agentleFS
rebelyticsrebelytics/one-skill-to-rule-them-all/skills/task-observer/SKILL.md

task-observer

Skill3.9k starsChanged 53 days agoCC-BY-4.0View on GitHub

Turns corrections, repeated workflows and judgement calls from work sessions into small, evidenced skill updates: logs each observation with its source, stages every change for your approval, and flags repeating work as new skills. Use during ANY multi-step task, agentic workflow, or work session. Also triggers in post-task feedback discussions and when the user mentions skill observations, the observation log, or skill taxonomy. 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. 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 session-start hook (references/environments.md). A subagent dispatched by a session already running it does not run it: it writes nothing and puts its findings in its report.

11 other projects use a version of this, 5 of them edited; 5 of 5 edited versions we compared changed its rules; 1 new project in the last 4 weeks, against 0 the 4 before.

How people change it

5 of 5 edited versions changed its rules, and some changes recur.

Of the 5 edited versions we compared: 5 made changes of their own.

Rules people drop

  1. A rule we can't quote: its licence doesn't allow itdropped by 5 of 5
  2. A rule we can't quote: its licence doesn't allow itdropped by 5 of 5
  3. A rule we can't quote: its licence doesn't allow itdropped by 4 of 5
  4. A rule we can't quote: its licence doesn't allow itdropped by 3 of 5
  5. A rule we can't quote: its licence doesn't allow itdropped by 3 of 5

Rules people add

  1. Scan. Read only the frontmatter of each file in observation-log/ — the header block between the first two --- lines, never the bodies — and build awareness from status, skill, proposes_skill and title; also read the active principles. …added by 5 of 5
  2. Review trigger. Read skill-observations/last-review-date.txt. The value carries the truth: a date = when the last review actually ran; never = no review has run yet. …added by 5 of 5
  3. Context preservation: if an observation depends on session-local data (uploads, API output), save that context into the workspace first and set reference: to its path — an observation whose evidence dies with the session is incomplete.added by 5 of 5
  4. Create skill-observations/last-review-date.txt containing the literal value never if it doesn't exist — never write a date into it at setup; a date means a review actually ran. …added by 4 of 5
  5. First run. If the log is empty and the project has history (handover or decision docs, commit history, test scripts, an existing CLAUDE.md — which is largely a record of corrections nobody logged), offer a one-off backfill pass over those artefacts. …added by 4 of 5
  6. Storage. If skill-observations/observation-log/ (with its archive/ subdirectory) or skill-observations/cross-cutting-principles.md don't exist, create them (principles template: references/skill-authoring.md). …added by 3 of 5
  7. If skill-updates/PENDING.md lists staged updates, say "N staged updates awaiting review" in one line.added by 3 of 5
  8. Batch writes: resolve each id at its own write time. When logging more than one observation in a session that may overlap a scheduled review or another writer, run the id snippet before EACH file — never pre-compute a range and hardcode sequential numbers …added by 3 of 5

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about rebelytics/one-skill-to-rule-them-all

The biggest 5 of 43 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 43

Talked about on GitHub and Hacker News (43 times).

On GitHub · 42

37 more on GitHub

On Hacker News · 1

Used with

Projects with it also use ui-ux-pro-max.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.