Task Observer — One Skill to Rule Them All

What it does

• Runs as a background observer across any multi-step task or agentic workflow, capturing user corrections, recurring task types, and "I always do it this way" methodology that no existing skill encodes.
• Stores each finding as one Markdown file with YAML frontmatter under skill-observations/observation-log/, anchored on a single stable absolute workspace path that outlives individual sessions (with an archive/ for resolved entries).
• Ships a strict Session Start Protocol: probe the storage mount inside the first batched tool call, scan frontmatter only (cheap at hundreds of entries), decide whether a weekly review is due, verify the activation config, and reconcile staged skill updates.
• Enforcement is the point: mandatory disk writes after every 3rd completed todo, a flush at every deliverable hand-off, an immediate flush when an external write is denied, plus retry-once-and-try-another-tool rules so observations are never silently lost.
• Includes de-duplication and escalation rules — extend an existing open entry instead of restating it, and when a rule is violated a second time, propose a structural barrier (hook, lint rule, unavailable default) rather than clearer wording.

Who it's for

• Builders who maintain their own set of Claude Code skills and want them to get measurably better over time.
• Anyone running long agent sessions who hates losing hard-won lessons at session end.
• Tech leads documenting and standardising a team's working methodology.
• Probably overkill if you just want a small, self-contained skill: the core file is large and demands careful path setup.

Examples

1. You correct the agent three times to "run the tests first" — an observation is logged that the target skill lacks that rule, and it surfaces in the next review.
2. The agent breaks the same documented rule twice — the proposal must now be a hook that refuses the call, not a bolder warning.
3. First run with an empty log but a repo full of handover docs and commit history — the skill offers a one-off backfill pass to seed initial observations.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/rebelytics/one-skill-to-rule-them-all/HEAD/SKILL.md

What I want: (describe your task here)

Install the skill I found on Claude Skill Mart.
Copy the SKILL.m folder from the GitHub repo rebelytics/one-skill-to-rule-them-all into my ~/.claude/skills/task-observer/.
When it's done, tell me in one line what this skill can do.