CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exceptionally strong on workflow discipline — sequenced checklists, explicit validation guards, and named error-recovery paths — and its guidance is concrete and largely executable, backed by a complete, trigger-labeled reference bundle. Its weakness is token efficiency: dense multi-clause prose, heavy restatement across sections, and duplication of reference content inline make a 756-line core that could be substantially tightened without losing any rule.

Suggestions

Cut the Quick Reference table or reduce it to non-duplicative pointers: its rows restate the restatement check, the id-derivation rule, the sibling check, and the two-guard rule almost verbatim from the body, doubling the token cost of the same policies.

Move the 20-line id-derivation bash snippet and the full frontmatter field spec into references/observation-log.md (which already documents them), keeping in the core only the new-observation.sh invocation and the one-line fallback pointer — the snippet is the single largest inline block duplicating reference content.

Split multi-clause sentences and drop the inline 'why' asides (e.g., the parenthetical justifications after each guard in the Session Start Protocol); each rationale already lives in the referenced section it names, so the core can state the rule and the pointer alone.

DimensionReasoningScore

Conciseness

The 756-line body is noticeably verbose for a companion/logging skill: rules are restated across sections (the restatement check, checkpoint rules, and archival policy each appear in prose, in the snippet comments, and again in the Quick Reference table), and single sentences routinely run 60+ words with nested parentheticals and 'why' asides (e.g., the workspace-anchoring paragraph). It is not 1 because the text never explains concepts Claude already knows — every sentence carries skill-specific policy — but it far exceeds 'some unnecessary explanation that could be tightened'.

2 / 5

Actionability

Guidance is mostly executable: a complete copy-paste id-derivation bash snippet with guards (noclobber create, collision check, listing guard), exact script invocations ("bash scripts/new-observation.sh --body <file> <slug> \"[ABSOLUTE PATH]\"", "scripts/set-fields.sh \"[ABSOLUTE PATH]\" <plan>", "scripts/diff-staged.sh <staged> <live>"), and a full frontmatter template enumerating every field. It falls short of 5 because some procedures give only the outcome vocabulary ("ERROR is not reconciled... DIFFERS is classified") or defer entirely to a reference section without the inline command, leaving minor gaps.

4 / 5

Workflow Clarity

The Session Start Protocol is a seven-item tick-box checklist with explicit ordering, and validation is pervasive with named feedback loops: the storage probe is 'split before any branch is chosen', 'an empty scan in a log known to be non-empty is a broken command until proven otherwise', failed writes get bounded retry rules, and the write snippet guards every failure mode it names. This matches the top anchor — clear sequence, explicit validation steps, error-recovery loops, and a checklist for a complex process.

5 / 5

Progressive Disclosure

Scored against the actual bundle: all nine referenced files (weekly-review, skill-authoring, observation-log, observation-scan, observation-families, signals, environments, migration, starter-principles) and all named scripts exist beside SKILL.md, and each pointer carries an explicit load trigger ('Load when a review triggers', 'Load only when the Session Start Protocol detects a legacy log'), one level deep. It is not 5 because substantial detail that has a reference home is also inlined in the core — the 20-line id snippet and the full frontmatter spec duplicate observation-log.md material, and the Quick Reference table re-states body content.

4 / 5

Total

15

/

20

Passed

Description

76%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description does an excellent job on completeness, pairing a concrete what-pipeline with explicit and varied when-triggers, and its niche vocabulary is distinctive. Its main defect is deliberate over-triggering: the mandatory-before-any-tool-call instruction maximizes conflict with every other skill, and a large share of the text is activation policy rather than capability description.

Suggestions

Remove or soften the blanket 'invoke before the FIRST tool call of any session' mandate from the description; keep activation guidance in CLAUDE.md or the referenced environments.md so the description triggers on the skill's actual niche (skill observations, observation log, skill taxonomy, feedback discussions).

Trim the meta-commentary about activation layers and subagent behavior from the description and spend that space naming more concrete capabilities (e.g., staged skill updates, observation archival, weekly review scheduling).

Add a few natural user-side synonyms such as 'skill review' or 'lessons learned' to broaden the natural-phrases coverage that is currently dominated by the skill's own internal vocabulary.

DimensionReasoningScore

Specificity

"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" lists several concrete, distinct actions (monitor, log, review-and-update, propose new skills), matching the 'several specific actions; minor gaps in coverage' anchor. It is not 5 because the latter half of the description shifts from capabilities to activation mechanics, and finer capabilities (staging, archival, sibling checks) are left unnamed.

4 / 5

Completeness

Both halves are explicit: the 'what' is the concrete pipeline ("logs patterns, user corrections and methodology... turns them into skill updates in a weekly review, and flags repeating work as new skills") and the 'when' is stated repeatedly with concrete trigger phrases ("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"). This clearly matches the top anchor and is not the 'when could be more explicit' level 4, since trigger guidance is if anything over-specified.

5 / 5

Trigger Term Quality

Natural trigger phrases are explicitly present — "when the user mentions skill observations, the observation log, or skill taxonomy", "post-task feedback discussions", "One Skill to Rule Them All" — giving good keyword coverage a user of this skill would actually say. It falls short of the comprehensive anchor because common variations like "skill review", "retro", or "lessons learned" are absent while much of the keyword budget is spent on self-referential activation instructions.

4 / 5

Distinctiveness Conflict Risk

Although the niche terms ("skill observations", "the observation log", "skill taxonomy") are distinct, the activation sentence — "invoke this skill before the FIRST tool call of any session... any turn that will involve a tool call counts" — makes the skill trigger alongside virtually every other skill in every session, which is the 'very broad; high overlap risk' anchor. It is not 1 because the description does name a clear, non-generic niche rather than being entirely generic.

2 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (757 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

rebelytics/one-skill-to-rule-them-all

Path

SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.