CtrlK
BlogDocsLog inGet started
Tessl Logo

epic-review

Authoritative protocol for pre-work review of epics. Six-stage gating chain — roadmap fit, approach elegance, source discussion mapping, sub-structure coherence, prescription layer, avoided-traps completeness — posted as a structured comment on the epic ticket. Per-agent-per-epic one-shot; subsequent sub pickups cite the prior review. Triggers: Use this skill when an agent is about to pick up its first sub from an unreviewed epic (per model-identity OTHER than the epic's author — you never review your own epic). Also use when a user explicitly requests an epic review, or when an epic is freshly filed and a reviewer pre-validates before any sub pickup begins. Participated in the source Discussion? The participant path narrows the chain; it never exempts it.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

A tight dispatch skill that defers detail to two real reference files, gives concrete tool/path/ordering guidance, and routes three cases unambiguously. Nothing is padded or redundant.

DimensionReasoningScore

Conciseness

The body is three lean paragraphs with no concept explanations Claude already knows; it assumes competence and every token earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete, specific guidance — the exact tool ('view_file'), the exact reference path to read, and a hard ordering constraint ('before running ticket-intake or any sub-work steps'). For an instruction-only dispatch skill this is copy-paste-ready direction; absence of code is not penalized.

3 / 3

Workflow Clarity

The three dispatch cases (first sub from an unreviewed epic / subsequent pickups / participant path) are clearly sequenced and unambiguous, and the ordering constraint ('before running ticket-intake') acts as a checkpoint for the simplest single-action skill.

3 / 3

Progressive Disclosure

The body is a concise overview pointing one level deep to real, well-signaled references ('references/epic-review-workflow.md' and 'references/participant-path.md', both present in the bundle), with content appropriately split out.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, specific description that enumerates concrete actions, includes explicit trigger guidance, and carves out a distinct niche. Voice is appropriately third person with no over-claims.

DimensionReasoningScore

Specificity

The description names multiple concrete actions — a 'six-stage gating chain' with all six stages enumerated (roadmap fit, approach elegance, etc.), 'posted as a structured comment on the epic ticket', and 'cite the prior review' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers both 'what' (pre-work review protocol, six-stage gating chain posted as a structured comment) and 'when' (the explicit 'Use this skill when...' triggers), satisfying the 'both what AND when' anchor.

3 / 3

Trigger Term Quality

An explicit 'Triggers:' clause lists natural user/agent scenarios ('about to pick up its first sub from an unreviewed epic', 'user explicitly requests an epic review', 'epic is freshly filed'), giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche — per-agent-per-epic one-shot epic pre-review, 'you never review your own epic' — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
neomjs/neo
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.