External/one-skill-to-rule-them-all
1
0
Fork 0
mirror of https://github.com/rebelytics/one-skill-to-rule-them-all.git synced 2026-06-10 17:17:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revise README for improved clarity on meta-skill

Browse Source 
Updated the README to enhance clarity and detail about the meta-skill's functionality and usage.
This commit is contained in:
Eoghan Henn
2026-05-20 15:24:20 +02:00
committed by GitHub
parent 20beaf208b
commit 4042203116
1 changed files with 25 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
README.md
View File

@@ -1,8 +1,12 @@
# One Skill to Rule Them All
_UPDATE AFTER THREE MONTHS OF USING THIS: The meta-skill has **logged and applied over 600 improvements across my 40 skills**, all of which were themselves created based on observations by the meta-skill._
## The meta-skill that builds and improves all your skills, including itself.
**The meta-skill that builds and improves all your skills, including itself.**
In the first three months of using this meta-skill, it **logged and applied over 600 improvements across my 40 skills**, all of which were themselves created based on observations by the meta-skill.
This meta-skill, called "task-observer", is a practical application of the [Augmented Expertise](https://www.rebelytics.com/augmented-expertise/) methodology, an AI framework for knowledge workers.
## Why you should use this meta-skill
Creating skills is powerful but time-consuming. And the skills that do get built stay frozen: they never learn from how you actually use them.
@@ -13,6 +17,12 @@ Task Observer fixes both problems. It's a skill that runs alongside your work, w
You work normally. It watches. Your skill library grows and gets better over time.
## The self-improving part
This is the detail that makes the task observer truly beautiful in my opinion. Because it runs during every session and observes all active skills — including itself — it captures improvements to its own methodology over time.
If it misses something, or if its observation format could be clearer, or if it's triggering in contexts where it shouldn't — it notices, and it logs that too. The skill that improves all your skills also improves itself.
## What it does
Task Observer monitors your work sessions and looks for three things:
@@ -25,6 +35,8 @@ At the end of each session, it produces a structured observation log: what it no
Some observations reveal patterns that aren't specific to one skill. These get captured as **cross-cutting principles** in a separate file — and new skills are automatically checked against them whenever they're created or updated. The more you use the system, the higher the quality floor across your whole skill library.
The observer doesn't modify your skills directly. It produces recommendations that you review. You stay in control of what changes and when.
## Who it's for
You don't need to be a developer. If you use skills in any capacity (for writing, research, client work, analysis, content creation, anything) and you want those skills to get better over time instead of staying frozen, this is for you.
@@ -33,9 +45,9 @@ It's particularly valuable if you've built multiple skills and want a systematic
## How it works
**The best way to get started with this work setup in any environment is probably to grab the skill, readme and user guide, feed them to your AI and let it guide you towards the best setup for your particular environment** - No matter which AI system you use. As long as skills are supported, you should be able to use this approach with some adjustments.
**The best way to get started with this work setup in any environment is probably to grab the skill, readme and user guide, feed them to your AI and let it guide you towards the best setup for your particular environment** - No matter which AI system you use. As long as skills are supported, you should be able to use this approach with some adjustments. And even without skills, the methodology should work with any other type of knowledge base that your AI has access to.
The observer doesn't modify your skills directly. It produces recommendations that you review. You stay in control of what changes and when.
## Claude environment notes
**In Claude Cowork (including Dispatch) or Claude Code in the desktop app:** Full experience. The observer writes observation logs to your filesystem, so improvements persist between sessions and can be actioned easily. Observations land in `[your shared folder]/skill-observations/`; proposed skill updates land in `[your shared folder]/skill-updates/`. You don't normally need to look at these directly — Claude handles them — but they're there if you want to inspect what's been captured.
@@ -57,24 +69,18 @@ The observer doesn't modify your skills directly. It produces recommendations th
- Codex version by AllstarGER: [https://github.com/AllstarGER/one-skill-to-rule-them-all](https://github.com/AllstarGER/one-skill-to-rule-them-all)
**Potentially compatible with caveats:**
- Other Agent Skills-compatible platforms (ChatGPT, Gemini CLI, Cursor, etc.) — the skill uses Claude-centric concepts like `<available_skills>` and skill-creator references that other systems would need to interpret or adapt. The SKILL.md format is cross-platform, but the content assumes Claude's architecture.
- Other skills-compatible platforms (ChatGPT, Gemini CLI, Cursor, etc.) — the skill uses Claude-centric concepts like `<available_skills>` and skill-creator references that other systems would need to interpret or adapt. The SKILL.md format is cross-platform, but the content assumes Claude's architecture.
If you try it on another platform, please let me know how it goes. Issues and pull requests welcome.
## Quick start
1. I recommend that you give the content of this repo (skill, readme and user guide) to the AI system of your choice and let it guide you towards the ideal configuration for your individual setup.
2. Read the user guide at [https://github.com/rebelytics/one-skill-to-rule-them-all/blob/main/USER-GUIDE.md](https://github.com/rebelytics/one-skill-to-rule-them-all/blob/main/USER-GUIDE.md)
1. Read the user guide at [https://github.com/rebelytics/one-skill-to-rule-them-all/blob/main/USER-GUIDE.md](https://github.com/rebelytics/one-skill-to-rule-them-all/blob/main/USER-GUIDE.md)
2. Give the content of this repo (skill, readme and user guide) to the AI system of your choice and let it guide you towards the ideal configuration for your individual setup.
3. Make sure that the skill loads in all sessions where it's needed (I solved this via an instruction in my CLAUDE.md file)
4. Try to remember to ask "Any observations logged" when you finish a session (I do this every time I archive a session). Often, the skill then finds additional improvement potential that it didn't log before.
4. Try to remember to ask "Any observations logged?" when you finish a session (I do this every time I archive a session). Often, the skill then finds additional improvement potential that it didn't log before.
5. Schedule a recurring review session that applies all open observations. Mine runs Monday, Wednesday and Friday morning, but you should adapt this to your needs.
## The self-improving part
This is the detail that makes the task observer truly beautiful in my opinion. Because it runs during every session and observes all active skills — including itself — it captures improvements to its own methodology over time.
If it misses something, or if its observation format could be clearer, or if it's triggering in contexts where it shouldn't — it notices, and it logs that too. The skill that improves all your skills also improves itself.
## Contributing
This is an early release. If you use it, I want to hear from you:
@@ -87,7 +93,11 @@ This is an early release. If you use it, I want to hear from you:
This work is licensed under [Creative Commons Attribution 4.0 International (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/).
You're free to use, adapt, and redistribute — even commercially — as long as you give appropriate credit.
You're free to use, adapt, and redistribute — even commercially — as long as you give appropriate credit: Link to the original repo (https://github.com/rebelytics/one-skill-to-rule-them-all/) and name the author (Eoghan Henn).
## Further reading
If you want to learn more about the methodology behind this skill, please read the [Augmented Expertise manifesto](https://www.rebelytics.com/augmented-expertise/).
## Security audit