rebelytics/task-observer

Monitors task execution for skill improvement opportunities. Use during ANY multi-step task, agentic workflow, or work session where the agent uses tools and produces deliverables. Captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers in post-task feedback discussions and when the user mentions skill observations, improvements, the observation log, skill taxonomy, or asks the agent to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: invoke this skill before the FIRST tool call of any session and before writing or proposing a plan — any turn that will involve a tool call counts, however simple the opener looks. This sentence is the session-start trigger and the only activation layer that survives an unreachable config file; pair it with a CLAUDE.md instruction or a harness session-start hook (references/environments.md) — description matching alone is not enforceable.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

task-observer - One Skill to Rule Them All

Name: rebelytics/task-observer
Rating: 68 (1 reviews)
Author: rebelytics

The meta-skill that builds and improves all your skills, including itself.

In the first seven months of using this meta-skill, it logged over 1200 observations across my 70 skills, most of which were turned into skill improvements. The majority of my 70 skills were themselves created based on observations by the meta-skill.

The current version of task-observer also includes improvements suggested by 36 different users, across 60 issues and 12 pull requests. Without these contributions, the project wouldn't be half as good as it is today.

This meta-skill is a practical application of the Augmented Expertise methodology, an AI framework for knowledge workers. However, users have reported successful integrations into their Hermes and Openclaw setups, so it works equally well with autonomous agents.

Why you should use task-observer

Creating skills is powerful but time-consuming. The skills that do get built stay frozen: they never learn from how you actually use them.

Task Observer fixes those problems. It's a meta-skill that runs alongside your work, watches what you do, and does two things:

Identifies new skills for you — it spots repeating patterns in your work and flags them as skill candidates, then helps you build them, so you get skills without staring at a blank page.
Improves your existing skills — it notices corrections you make, preferences you express, and gaps in your current skills, then suggests specific updates.

You work normally. It watches. Your skill library grows and gets better over time.

The self-improving part

This is the detail that makes 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:

Corrections and adjustments — if you adjust the AI's output or steer it in a different direction, that's a signal that a skill could be clearer or more complete
Gaps no skill covers yet — if you're doing something manually or repeatedly that could be systematised, the observer flags it as a candidate for a new skill
Its own blind spots — the observer watches itself too, capturing improvements to its own methodology as you use it

During each session, it produces a structured observation log: what it noticed, which skills are affected, and specific suggested improvements. You review, approve, and your skills evolve.

Some observations reveal patterns that aren't specific to one skill. These get captured as cross-cutting principles in a separate log — 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 and you want those skills to get better over time instead of staying frozen, this is for you.

If you're a builder, you can easily integrate this skill, or even just the methodology, into your existing setup. Just point your agent at the repo and let it guide you towards the ideal implementation for your specific setup.

The task observer is particularly valuable if you've built multiple skills and want a systematic way to maintain and improve them without manually auditing each one. It's also useful if you don't have any skills yet: the observer will start identifying skill candidates for you and help you build them.

One honest boundary: the formal observation log and review cycle pay off most as your skill library and usage grow — many skills, parallel sessions, scheduled reviews. If you run a small setup with a handful of skills, your AI system's built-in memory features may cover much of the same ground with less overhead, and editing a skill directly is quick. The observer's value compounds with scale: adopt it early if you expect your library to grow, or come back to it when direct editing stops feeling manageable.

How it works

The best way to get started with this work setup in any environment is 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.

Installation

The skill is a small bundle: SKILL.md, the files in references/ that are loaded on demand (this keeps the always-loaded part lean), and two helper scripts in scripts/. Installing only SKILL.md works, but runs degraded and isn't recommended — the skill will tell you which files are missing.

Get the files: download the .skill bundle attached to the latest release, or download the repo as a ZIP (Code → Download ZIP) / clone it and keep SKILL.md, references/ and scripts/ together.

Claude (web interface, desktop app, mobile app, Cowork): upload the .skill bundle via Settings → Customize (or put SKILL.md, references/ and scripts/ into one folder and zip that folder). The skill is then available in all chats and in Cowork tasks.

Claude Code: place the folder at .claude/skills/task-observer/ (project-level) or in your user-level skills directory, preserving the references/ and scripts/ subfolders.

Other systems: keep the folder structure intact wherever your platform expects skills, and let your AI guide you (see "How it works" above).

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/observation-log/, one small file each; proposed skill updates land in [your shared folder]/skill-updates/. Upgrading from a version before 3.0? The first session converts your old single-file log automatically (see the user guide). 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.

In Claude.ai web or Claude Chat in the desktop app / mobile app: Handoff doc mode. Since there's no filesystem access, the observer produces a structured handoff document at the end of your session that you can use to update your skills in a dedicated session.

Compatibility

Tested and designed for:

Claude Cowork (full experience with filesystem access)
Claude Dispatch
Claude.ai web interface (handoff doc mode)
Claude mobile app (handoff doc mode)
Claude Code in the desktop app

Confirmed to work by users:

Claude Code without desktop app — the methodology and format translate directly - plenty of users have reported seamless experiences with this.

Versions for other environments created by users:

Codex version by AllstarGER: https://github.com/AllstarGER/one-skill-to-rule-them-all (based on an older version of task-observer)
Please get in touch if you've open-sourced an adaptation of the meta-skill for another system or environment. I'm happy to include it here.

Potentially compatible with caveats:

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.
Users have reported successful integrations into Openclaw and Hermes setups.

If you try it in another environment, please let me know how it goes. Issues and pull requests welcome.

Quick start

Read the user guide at https://github.com/rebelytics/one-skill-to-rule-them-all/blob/main/USER-GUIDE.md
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.
Make sure that the skill loads in all sessions where it's needed (I solved this via an instruction in my CLAUDE.md file).
Try to remember to ask "Any observations logged?" when you finish a session (I do this every time I archive a session). Sometimes, the skill then finds additional improvement potential that it didn't log before.
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.

Contributing

This is an open-source project for the community. If you use it, I would love to hear from you:

Bug reports and feature requests: Open an issue or a pull request, whichever you prefer — you are credited either way. See CONTRIBUTING.md for how reports become changes and how credit works.
Platform compatibility reports: Tried it somewhere other than Claude? Tell me what happened.
Interesting use cases: Have you come up with a creative way of using or improving Task Observer?
Integrations with other systems: One user told me that they connected task observer to Obsidian. Do you have a similar story?

License

This work is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0).

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 / rebelytics.com).

Recommended by

I would like to thank the following creators, platforms, publications, companies and kind people who have recommended task-observer to their audiences: