Skip to content

rebelytics/one-skill-to-rule-them-all / skills/task-observer

task-observer

Verified

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.

FileKindSize
LICENSEother18.2 KB
SKILL.mdskill md39.1 KB
references/acting-on-observations.mdmarkdown4.9 KB
references/ceilings.txtmarkdown9.9 KB
references/environments.mdmarkdown134.0 KB
references/migration.mdmarkdown13.2 KB
references/observation-families.mdmarkdown12.1 KB
references/observation-log.mdmarkdown68.7 KB
references/observation-scan.mdmarkdown34.4 KB
references/review-slice.mdmarkdown3.1 KB
references/signals.mdmarkdown13.1 KB
references/skill-authoring.mdmarkdown92.2 KB
references/starter-principles.mdmarkdown31.0 KB
references/weekly-review.mdmarkdown165.2 KB
scripts/bin-check.shexecutablescript5.9 KB
scripts/diff-staged.shexecutablescript5.5 KB
scripts/extend-observation.shexecutablescript11.1 KB
scripts/migrate-log.pyscript25.1 KB
scripts/new-observation.shexecutablescript23.6 KB
scripts/session-start-scan.shexecutablescript56.6 KB
scripts/set-fields.shexecutablescript21.6 KB
scripts/skill-load.shexecutablescript11.0 KB
scripts/stage-patch.shexecutablescript4.4 KB
scripts/validate-skill-bundle.pyscript227.5 KB

references/review-slice.md

View on GitHub
# Bounded slice — the entry path

Load triggers: a bounded slice runs (the offer in Session Start step 3, or a request to review the N oldest open entries)

A slice bounds the work, so its entry cost is bounded too. This file is
loaded instead of the whole of `weekly-review.md`, and that file's sections
are read one at a time, when the slice reaches them. Read a section from
its heading to the next step's heading (`grep -n` the heading, then read
that range). A section that sends you to another section, or a case this
file does not name, loads that section as well. Every rule in a section
read still binds: this file orders the reads, it replaces none of them.

**What a slice is.** A review of the N oldest OPEN entries, and it runs
as a review, not a glance. **Selection:** the N oldest by `date:`, then
id, leaving out parked entries and those asked and unanswered
(`weekly-review.md`, Approval policy, "An escalation is recorded on the
entry"), which the record lists once under "Waiting for the user" — and
re-asks, as a yes-or-no with the recommendation, each such entry whose
last ask was in the previous review, appending the re-ask to its
`escalated:` field; one re-asked and still unanswered is parked (Approval
policy). **Run for the slice:** Steps 3, 5 and 6 over its entries, and the
gate for the skills it stages. For each skill the slice stages, also list
the open entries naming it (`bash scripts/skill-load.sh "[ABSOLUTE PATH]"
<skill-name> --query-only`) and read the titles of those outside the
slice: the staged text stays consistent with them, or the record names
the conflict. They are checked for contradiction only, never reported as
reviewed. **Run for the whole log whatever the slice:** Step 1's integrity
checks (duplicate id, contiguity, header conformance, the inbox drain) and
Step 6's re-scan against the Step 1 list — a slice that skips them leaves
the log unchecked for as long as slices are all that run. **Record:**
`reviews/<date>-slice/REVIEW.md`, the Step 7 template with a first line
"Bounded slice: N of M open — ids …", and the steps not run named (Step 4,
the promotion pass); entries outside the slice are never reported as
reviewed. **Timestamp:** Step 8 with `rec` set to the slice's record,
bound to an outcome like a full review.

**The order, and the section of `weekly-review.md` each step reads:**

1. **Queue and integrity, whole log.** Step 1 from "Drain the observation
   inbox" up to "Staged-work reconciliation gate": the drain and harvest,
   the queue built from the files, the list kept on disk, the duplicate-id,
   contiguity and header checks. Then select the slice as above.
2. **Bodies and routing, slice only.** Step 3, for the slice's entries.
   An entry that needs the user's decision also reads Approval policy.
3. **Apply, only where the slice stages something.** "Staged-work
   reconciliation gate" for each skill it stages, then Step 5 and, at
   delivery, "Delivering updated skills". A slice that stages nothing
   reads none of them.
4. **Re-scan and mark, whole log.** Step 6.
5. **Record.** The Step 7 template ("Weekly Skill Review Complete").
6. **Timestamp.** Step 8, with `rec="reviews/$d-slice"`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall