CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-compound

Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work corrected a wrong belief about how something behaves, such as a failed approach, a real defect a review caught, or a wrong assumption or document, or when auditing stale, overlapping, or drifted learnings. Do not auto-invoke it for work that went as first planned.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ce-compound/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-architected orchestrator skill: the body stays a lean dispatch layer, names its required reads at each step, gates entry with an explicit counterfactual, and defines per-mode exits and terminal signals. Its weaknesses are prose density — Mode Detection and the Write boundary are run-on paragraphs that would scan better (and cost fewer tokens) as lists — and a validation loop that is only implied at body level.

Suggestions

Rewrite the Mode Detection and Write boundary sections as short bullet lists instead of multi-clause run-on paragraphs — the same rules in fewer tokens, and far easier to scan mid-run.

State the body-level validation loop explicitly (e.g. after writing, re-check the chosen form against the Done criteria and fix before reporting) rather than only implying it with the word 'validated'.

Surface the references/refresh/ subtree structure in the body or in refresh/overview.md's opening lines (a file index for the refresh job) so no content sits two reference levels deep from SKILL.md without navigation.

DimensionReasoningScore

Conciseness

The body spends no tokens on concepts Claude already knows — every sentence is operational — but several sections are multi-clause run-ons that need real tightening, e.g. the Mode Detection paragraph ('Enter non-interactive mode when either holds: the arguments... contain the mode:non-interactive token or its deprecated alias mode:headless, or the invocation makes non-interactive intent unmistakable...') and the Write boundary section, which is a single nine-line sentence enumerating every write permission. This goes beyond the 'minor instances' of anchor 4 and fits anchor 3's 'mostly efficient... could be tightened'.

3 / 5

Actionability

Guidance is concrete and specific throughout: exact tokens ('mode:non-interactive', 'depth:lightweight'), exact paths ('references/research.md', '<repo-root>/.compound-engineering/config.yaml', resolved via 'git rev-parse --show-toplevel'), and exact terminal signals ('Documentation complete', or 'Documentation skipped' with the reason). Minor gap: the body-level guidance is dispatch rules, with the executable detail of form choice and validation delegated to the reference files, so it is 'mostly executable' rather than fully copy-paste ready.

4 / 5

Workflow Clarity

The Full Mode flow is clearly sequenced ('Run these in order. Each reference is a required read at the step that names it') with six numbered steps, an entry gate (the counterfactual 'without a record of this lesson, would a future engineer... still be likely to repeat the mistake or redo substantial investigation?') and explicit exit criteria ('Done: the chosen form is written or updated and validated... when no lesson qualifies, nothing is written and the report says why'). Not anchor 5: the validate-and-fix loop for written artifacts is only implied by the word 'validated' in the Done line, and error-recovery detail lives one reference deep rather than in the body.

4 / 5

Progressive Disclosure

Every reference is signaled at its point of use ('Read references/modes.md... Read it before step 1', 'read references/form.md and write what it chooses'), and all ten body-referenced paths exist in the bundle (research.md, modes.md, session-history.md, form.md, assembly.md, refresh-and-discoverability.md, enhancement.md, report.md, lightweight.md, refresh/overview.md). Minor organization gap: the refresh job's content sits a second reference level deep (SKILL.md → references/refresh/overview.md → the ten files in references/refresh/), so the structure is not uniformly one-level-deep as anchor 5 requires — fits anchor 4's 'most content is appropriately placed... minor organization gaps'.

4 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description: it states both jobs (capture and refresh) concretely, gives explicit 'Use when' triggers with illustrative examples, and adds a negative trigger to prevent over-invocation. The only real gap is modest synonym coverage in its trigger terms.

DimensionReasoningScore

Specificity

Names several concrete output forms — 'a test or lint rule, a coding standard, or a repo learning' — plus the two actions 'Capture a solved problem's lesson' and 'refresh existing learnings against the codebase'. It falls short of anchor 5 because 'cheapest durable form' is somewhat abstract and only two verbs are enumerated, but it lists far more concrete forms than the 1-2 actions of anchor 3.

4 / 5

Completeness

Explicitly answers both questions: what ('Capture a solved problem's lesson in its cheapest durable form... or refresh existing learnings against the codebase') and when ('Use when verified work corrected a wrong belief about how something behaves, such as a failed approach... or when auditing stale, overlapping, or drifted learnings'), with concrete trigger phrases and an explicit negative trigger ('Do not auto-invoke it for work that went as first planned') — a clear match for anchor 5.

5 / 5

Trigger Term Quality

Includes natural trigger phrases such as 'a failed approach, a real defect a review caught, or a wrong assumption or document' and 'auditing stale, overlapping, or drifted learnings', with synonym variation across 'lesson'/'learning'. Missing some common user phrasings (e.g. 'postmortem', 'document this fix', 'clean up the docs'), so it matches anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche — persisting the lesson of a verified solved problem in a durable artifact, or auditing existing learnings — is distinct, and the exclusion clause 'Do not auto-invoke it for work that went as first planned' further reduces false triggers. Matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

EveryInc/compound-engineering-plugin

Path

skills/ce-compound/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.