CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-doc-review

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally well-engineered orchestration skill body: lean and token-efficient, fully actionable with exact paths and failure behaviors, a clearly phased workflow with genuine validation checkpoints, and textbook just-in-time progressive disclosure across a verified reference bundle. The internal "issue #925" aside is the only trivially removable token.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and contains zero explanation of concepts Claude already knows — every sentence carries project-specific rules ("A capacity rejection is backpressure, not reviewer failure: wait and retry"), matching the 'every token earns its place' anchor. It is not 4 because no section could be trimmed without losing a real rule.

5 / 5

Actionability

For an instruction-only orchestration skill, the guidance is fully executable: exact file reads with timing ("Read `references/modes.md` before anything else"), exact config resolution ("Read `docs_root` from `<repo-root>/.compound-engineering/config.yaml` only"), exact dispatch and failure-handling behavior. All referenced bundle files (modes.md, document-intake.md, persona-selection.md, dispatch.md, depth.md, cross-model-review.md, synthesis-and-presentation.md, walkthrough.md, bulk-preview.md, subagent-template.md, findings-schema.json, personas/) verified to exist, leaving no gaps that would drop it to 4.

5 / 5

Workflow Clarity

Phases 1-5 are explicitly sequenced with a "Done when" checklist and explicit validation checkpoints: "Verify before any dispatch. Every resolved path must be readable on disk", "Wait until every dispatched agent has returned", and corrections "made and checked". Error-recovery loops cover capacity rejection, reviewer failure, and cross-model timeouts, satisfying the batch-operation feedback-loop requirement that would otherwise cap this at 3.

5 / 5

Progressive Disclosure

Scored against the actual bundle: the body is a lean overview with clearly signaled, one-level-deep references, each with an explicit read-timing rule ("Load neither before review evidence is complete"; non-interactive runs never load them), plus @-includes for the template and schema. All 13 reference files and the personas/ subdirectory exist as cited, with no bulk detail inlined and no nested reference chains in the body.

5 / 5

Total

20

/

20

Passed

Description

70%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 concise, well-formed description that clearly states both capability and an explicit use-when trigger, with decent natural keywords and a distinct planning-document niche. Its main limitation is thin specificity — it names the review activity but not the concrete actions the skill performs (persona dispatch, finding verification, authorized fixes).

Suggestions

Enumerate 2-3 concrete actions in the description, e.g., "Dispatch role-specific reviewer personas, verify their findings, and apply authorized fixes" — this would raise specificity from naming the domain to listing capabilities.

Broaden trigger coverage with natural variations users actually say, such as "spec review", "PRD", "design doc", or "critique my plan", to improve trigger-term quality and further reduce conflict risk with generic review skills.

DimensionReasoningScore

Specificity

"Review requirements, plans, or specs with role-specific lenses" names the domain and a single action framing but never lists what the review concretely does (e.g., dispatching reviewer personas, verifying findings, applying fixes), matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor at 4.

3 / 5

Completeness

Both halves are explicit: what ("Review requirements, plans, or specs with role-specific lenses") and when ("Use when the user wants to improve an existing planning document"). The 'when' clause is present but single and could be more specific with additional trigger scenarios, exactly matching anchor 4 rather than the multiple concrete trigger phrases required for 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say — "requirements, plans, or specs", "review", "improve", "planning document" — giving good keyword coverage, though common variations like "design doc", "PRD", or "spec review" are missing, placing it just below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

"planning document" review with "role-specific lenses" carves a mostly distinct niche with a clear trigger, but the broad verb "review" leaves minor overlap risk with generic critique or code-review skills, keeping it below the minimal-conflict anchor at 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

EveryInc/compound-engineering-plugin

Path

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