CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-build

Use when full Comet change 已完成 design 阶段,需要创建/恢复实施计划、选择执行方式或继续 build 阶段任务。

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 tightly sequenced, highly actionable orchestration workflow with strong validation checkpoints, feedback loops, and a clear exit checklist. Its main weakness is conciseness — repeated hard-constraint injunctions and restated guard language inflate the token budget without adding guidance.

Suggestions

Consolidate the repeated hard-constraint restatements (e.g. the '必须按 decision-point.md 协议暂停并等待用户明确选择' injunction and the per-field guard-failure paragraphs) into a single '硬约束' reference block near Step 3, then refer back to it instead of restating each time.

Replace the repeated '立即执行:使用 Skill 工具加载 Superpowers X 技能。禁止跳过此步骤。' boilerplate with a single defined convention (e.g. a '加载技能(X)' shorthand introduced once) to cut redundancy across Steps 1, 3, 3b, and the TDD/review gates.

Move the detailed branch-naming rules and the full review_mode/thorough segmentation logic into comet/reference/ files, keeping SKILL.md as a leaner orchestration overview that links out — this would also let progressive_disclosure reach the top anchor.

DimensionReasoningScore

Conciseness

Mostly efficient and much of the detail is genuinely Comet-specific state-machine knowledge Claude lacks, but hard-constraint restatements (e.g. '必须按...协议暂停并等待用户明确选择', '立即执行:使用 Skill 工具加载...') are repeated across steps and could be tightened, fitting 'mostly efficient with some unnecessary explanation'.

3 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout (e.g. `node "$COMET_STATE" set <name> plan ...`, `git rev-parse HEAD`, `grep -n '\- \[ \]' tasks.md | head -1`), plus concrete subagent instructions, YAML templates, and option tables covering the common cases.

5 / 5

Workflow Clarity

Clear Step 0–5 sequence with explicit validation checkpoints (entry check, comet-guard build --apply, review gate, debug-gate), feedback loops for error recovery, and an explicit exit-condition checklist — matching the top anchor.

5 / 5

Progressive Disclosure

References are one-level-deep and clearly signaled inline ('按 comet/reference/decision-point.md 的协议'), and detail is delegated to reference docs; however the SKILL.md body itself is dense (~316 lines) and the referenced comet/reference/*.md files are absent from the bundle, leaving minor organization/verification gaps.

4 / 5

Total

17

/

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.

The description is well-crafted: it opens with an explicit 'Use when' trigger tied to a specific workflow state and enumerates concrete build-phase actions, making it highly distinct and actionable. It is concise and free of fluff or over-claims.

DimensionReasoningScore

Specificity

Lists several concrete actions in the Comet domain — '创建/恢复实施计划', '选择执行方式', '继续 build 阶段任务' — with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers both what (create/recover plan, select execution mode, continue build tasks) and when ('Use when full Comet change 已完成 design 阶段') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Uses natural phrases a Comet user would say ('design 阶段', '实施计划', '执行方式', 'build 阶段任务') with good keyword coverage, though a few common synonyms are missing, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, clearly named niche (Comet build phase / 阶段 3) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.