CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-design

Comet Classic 阶段 2 —— 为 change 产出深度技术 Design Doc。

62

Quality

73%

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 ./assets/skills-zh/comet-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 content is a well-structured, highly actionable phase orchestration guide with strong sequencing, explicit validation gates, and clean progressive disclosure via reference files; its only weakness is minor verbosity from duplicated frontmatter and detailed handoff-internal descriptions.

DimensionReasoningScore

Conciseness

The body is dense and operational, assuming Claude's competence without explaining known concepts; minor over-explanation remains (the frontmatter template is restated in Step 1b and Step 2, and the handoff-package internals in 1a could be trimmed), keeping it just below fully lean.

4 / 5

Actionability

It provides copy-paste-ready commands throughout (comet state select/check/set, comet handoff ... --write, comet guard ... --apply, comet state next) with concrete file paths and explicit frontmatter templates covering the common cases.

5 / 5

Workflow Clarity

The process is clearly sequenced (Step 0 entry check through 3a) with explicit validation checkpoints (entry check, blocking user confirmation at 1c, guard --apply PASS gate at exit), error-feedback guidance, and an exit-condition checklist for this batch/state-mutating workflow.

5 / 5

Progressive Disclosure

The SKILL.md acts as a clear orchestration overview with well-signaled one-level-deep references to comet-classic/reference/*.md (classic-layout, scripts, context-recovery, decision-point, auto-transition), deferring detailed mechanics to those files rather than inlining or nesting them.

5 / 5

Total

19

/

20

Passed

Description

53%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 states a clear domain and a single concrete action but lacks an explicit 'Use when' trigger and relies on internal phase jargon, leaving it at a competent-but-not-exceptional level across specificity, triggers, and completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when a Comet change has completed the open phase and needs a deep technical design before build.'

Expand concrete actions beyond '产出 Design Doc' to include the key sub-outputs (technical implementation design, risk analysis, test strategy, Spec Patch write-back).

Soften internal jargon by adding natural user-facing trigger phrases alongside 'Comet Classic 阶段 2'.

DimensionReasoningScore

Specificity

It names the domain ('Comet Classic 阶段 2') and one concrete action ('为 change 产出深度技术 Design Doc'), but coverage is not comprehensive, matching the '1-2 concrete actions' anchor rather than the more action-rich 4/5 anchors.

3 / 5

Completeness

The 'what' is clear (produce a deep technical Design Doc for a change) but there is no explicit 'Use when...' trigger clause; 'when' is only weakly implied by the phase-2 framing, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'Comet Classic 阶段 2', 'change', and 'Design Doc' are relevant but lean toward internal project jargon with phase numbering, missing natural variations or synonyms a user would commonly say.

3 / 5

Distinctiveness Conflict Risk

The 'Comet Classic 阶段 2' / design-phase framing carves a clear niche with mostly distinct triggers, with only minor overlap risk against sibling Comet phase skills (open/build).

4 / 5

Total

13

/

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.

Validation16 / 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.