CB task-observer
Monitors task execution for skill improvement opportunities: logs patterns, user corrections and methodology worth preserving to the workspace, turns them into skill updates in a weekly review, 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.
Monitors task execution for skill improvement opportunities: logs patterns, user corrections and methodology worth preserving to the workspace, turns them…
As a process B 68/100 · Nearly there — weak spots: result and completion, consistency, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenREADME.md:220High-entropy token-like string (may be an id, hash or a credential)[platform's scheduler queried directly: `crontab -l` on Unix; `launchctl
quoted
Files scanned: 28. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 11022 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "core_max_lines" - note
edit-residuethe text marks something as outdated (lines 77): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 68/100
- 0Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (task-observer) differs from the folder (one-skill-to-rule-them-all)
- 40Execution cost. Instruction body is 11022 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 85Steps. 14 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 2 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 999: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -33 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (7 of 8)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.