CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-build

Comet Phase 3: Plan and Build. Invoke with /comet-build. Create plans and select execution method (subagent or direct) for implementation.

61

Quality

71%

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 ./eval/local/skills/benchmarks/039-release/comet-classic-039-build/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a well-sequenced, highly actionable workflow with strong validation checkpoints, though slightly redundant in its hard-constraint boilerplate. Its main weakness is reliance on a comet/reference tree that is not bundled here, leaving progressive disclosure partially dangling.

Suggestions

Ship the referenced comet/reference/*.md files (decision-point, subagent-dispatch, debug-gate, context-recovery, dirty-worktree, auto-transition) as actual bundle files so the references resolve.

Consolidate the repeated 'script-enforced hard constraint' explanations for isolation/subagent_dispatch/tdd_mode/build_mode into one table to reduce boilerplate.

Add a one-line note near the top listing the reference files this skill depends on, so the dependency surface is visible before the reader encounters each inline reference.

DimensionReasoningScore

Conciseness

The body is largely efficient instructional prose that assumes competence and delegates detail to reference files, with only minor repeated hard-constraint boilerplate that could be trimmed.

4 / 5

Actionability

It provides concrete, copy-paste-ready bash commands (comet-state, git checkout -b, git rev-parse HEAD) and explicit skill-load instructions throughout, fully executable.

5 / 5

Workflow Clarity

Steps 0–5 are clearly sequenced with explicit validation checkpoints (entry check, review gate, debug gate) and feedback loops (fix and re-validate) for fragile operations.

5 / 5

Progressive Disclosure

It signals one-level-deep references to comet/reference/*.md files, but none of those bundle files actually exist in the skill directory, so the references are present but unverifiable and key detail is left inline.

3 / 5

Total

17

/

20

Passed

Description

57%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 is distinctive and names concrete actions but lacks an explicit 'Use when...' trigger clause, leaving the 'when' only weakly implied. It is competent but not comprehensive in capability coverage.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when the user wants to move from a design doc into implementation planning and execution.'

Broaden natural trigger terms beyond the slash command to include phrases users actually say, such as 'implement the design', 'start the build phase', or 'create an implementation plan'.

List a couple more concrete actions (e.g. 'break the design into tasks', 'run entry-state verification') to lift capability specificity.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Create plans', 'select execution method (subagent or direct)') but the coverage is not comprehensive, matching the anchor for a clear 'what' with limited actions.

3 / 5

Completeness

It states a clear 'what' but the 'when' is only weakly implied via 'Phase 3: Plan and Build' with no explicit 'Use when...' trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

The slash command 'Invoke with /comet-build' and terms 'plans'/'execution method' provide some natural keywords but miss common synonyms and variations a user might say.

3 / 5

Distinctiveness Conflict Risk

The 'Comet Phase 3: Plan and Build' niche with a distinct '/comet-build' trigger is clearly distinguishable with minimal conflict risk against other skills.

5 / 5

Total

14

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rpamis/comet
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.