Skip to content
SkillScript-led9,245 tokens in use

Task Observer

A meta-skill that logs corrections and repeated workflows during agent sessions, then stages evidenced updates to your skills for your approval.

3,986 stars on the repository CC-BY-4.0rebelytics/one-skill-to-rule-them-all · skills/task-observer
npx skills@1.8.1 add rebelytics/one-skill-to-rule-them-all --skill task-observer
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Task Observer costs

197tokens idle
9,245tokens in use
145,052tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/bin-check.sh, scripts/diff-staged.sh, scripts/extend-observation.sh, scripts/migrate-log.py, scripts/new-observation.sh, scripts/session-start-scan.sh, scripts/set-fields.sh, scripts/skill-load.sh, scripts/stage-patch.sh, scripts/validate-skill-bundle.py.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter15/15
  • Structure17/25
  • Examples15/15
  • Output15/15
  • Size9/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 169
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 371

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community52
  • Maturity32
  • Momentum40

Task Observer runs alongside your work and watches for friction: a correction you make, a preference you state, a rule the agent breaks, or a workflow you repeat. Each finding is written to a file in an observation log with its source, then surfaced as a grouped summary at the end of the session.

A periodic review turns open observations into staged edits of your skills and flags repeating work as candidates for new skills. Nothing is installed without you: changes are made on a staged copy and handed over for approval.

What You Get

  • A skill-observations folder in a stable workspace with one Markdown file per observation, plus archive, checkpoint and session-start logs
  • A session-start scan that reports open observations, a due review and staged updates
  • A review procedure that turns observations into staged skill edits and new skill candidates
  • Reference files for activation setup, signals worth logging, skill families, authoring and migration
  • Ten helper scripts that create, edit, scan and validate observation files

Common Use Cases

  • Capture the corrections you give an agent so they reach the skill that should have prevented them
  • Spot repeated workflows that deserve their own skill
  • Keep a team’s skills improving from real sessions with a reviewable history
  • Fix a rule the agent keeps breaking with a hook or check on the second violation

What Makes It Unique

It treats improvement as a pipeline with evidence at each step: observe, log, review, stage, install. Edits are never made to live skills, only to staged copies, and a second violation of the same rule requires a hook or check as the fix. The README reports more than 2,500 observations logged across 87 skills by its author and credits over 100 contributors.

Under The Hood

The skill is a core SKILL.md plus reference files loaded on demand and ten helper scripts, mostly bash with two Python tools. They create the workspace folders, scan observation frontmatter at session start, assign observation ids, write and edit observation files, stage patches, diff staged updates against installed skills and validate skill bundles. It reads and writes files in a persistent workspace folder you pin, and expects the agent to run these scripts through the shell. Normal operation fetches nothing from the network; a few opt-in features, such as a version check of a foreign skill or a feedback pre-flight, are enabled by one line in your instruction file. Activation is best set up with a session-start hook and an instruction block in CLAUDE.md, since description matching alone tends to under-trigger.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers