CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-verify

Use when Comet change 已完成 build 阶段,需要验证实现、处理验证失败决策或完成分支收尾。

68

Quality

83%

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

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

A thorough, highly actionable verification workflow with explicit checkpoints, feedback loops, and concrete state-management commands. Its main weakness is density: repeated safety caveats and inlined operational detail make SKILL.md heavier than an ideal overview.

Suggestions

Consolidate the repeated safety caveats ('仅在用户确认修复后执行', '禁止跳过此步骤', '必须暂停并等待用户') into a single stated convention referenced where needed, to trim conciseness.

Move the full light/full verification checklists and retry-cap rules into a comet/reference/ file, keeping SKILL.md as a leaner overview that links to them, to improve progressive disclosure.

Reduce duplicated verify-fail transition blocks by stating the command once and referencing it from each failure branch.

DimensionReasoningScore

Conciseness

Dense and mostly efficient with no padding about concepts Claude already knows, but safety caveats repeat across sections ('仅在用户确认修复后执行', '禁止跳过此步骤', '必须暂停并等待用户') and could be consolidated.

4 / 5

Actionability

Copy-paste-ready bash commands throughout (check/scale/transition/set/get subcommands, git diff --stat with base-ref), concrete 6-item and 7-item checklists, and explicit decision protocols cover the common cases fully.

5 / 5

Workflow Clarity

Clearly sequenced 0a→0b→1→1b→2a/2b→3→4 flow with explicit validation checkpoints, a verify-fail→build→retry feedback loop, a 3-retry cap, blocking user-decision points, idempotency notes, and a concrete exit-condition checklist.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references to comet/reference/* and named Superpowers skills make navigation easy, but SKILL.md itself is a long, dense inlined workflow rather than a lean overview pointing to detail files.

4 / 5

Total

18

/

20

Passed

Description

78%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 focused, trigger-led description that clearly states when (Comet build phase done) and what (verify, handle failure decisions, branch wrap-up) in the skill's domain language. It is distinct and well-scoped, with only minor room to sharpen the action granularity and separate the what/when phrasing.

DimensionReasoningScore

Specificity

Names the Comet domain plus three concrete actions — '验证实现', '处理验证失败决策', '完成分支收尾' — but they describe workflow phases at a fairly high level rather than granular operations, leaving minor coverage gaps.

4 / 5

Completeness

Both what (verify / handle failure / wrap up branch) and when (Comet change completed build phase) are present and the trigger is concrete, but the two are fused into one clause rather than cleanly delineated as in the top anchor.

4 / 5

Trigger Term Quality

Domain terms a Comet user would naturally say ('已完成 build 阶段', '验证实现', '验证失败决策', '分支收尾') with an explicit 'Use when' trigger, but coverage is process-jargon with no synonyms or variations.

4 / 5

Distinctiveness Conflict Risk

Tied to the named 'Comet change' system and its specific verify/build phase triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

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.