CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-archive

仅在用户明确调用 /comet-archive,或由 Comet 根 Skill/runtime 路由到 archive 阶段时使用;确认归档、合并 delta spec 并完成分支收尾。

75

Quality

92%

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

85%

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

A well-sequenced, highly actionable archive workflow with strong validation checkpoints and appropriate deferral to reference files; the main weakness is minor redundancy that could be tightened. Actionability and workflow clarity are strong; conciseness is the lowest dimension due to restated steps.

Suggestions

Remove the restated '脚本会调用 OpenSpec 归档能力...合并主 spec...校验主 spec 中没有残留 delta-only section 标题' sentence in Step 2 — it duplicates numbered items 4–5; fold the ADDED/MODIFIED/REMOVED/RENAMED detail into item 4 instead.

Drop the duplicate '归档脚本会把 openspec/changes/<name>/ 移动到 .../archive/YYYY-MM-DD-<name>/' line in 退出条件 (Step 4 already states the move) and keep exit conditions focused on success criteria.

Consolidate the comet/reference/* pointers into a short '## 参考资料' section so the deferred-detail navigation is discoverable in one place rather than scattered inline across steps.

DimensionReasoningScore

Conciseness

Mostly lean and command-driven with no concept-explanation fluff, but it restates the spec-merge/校验 steps in prose after the Step 2 numbered list and repeats the directory-move in 退出条件, so not every token earns its place; not a 3 because it could be tightened.

2 / 3

Actionability

Provides fully executable commands (node "$COMET_STATE" check <name> archive, node "$COMET_ARCHIVE" "<change-name>", git add -A / git commit) and concrete single-choice options that are copy-paste ready.

3 / 3

Workflow Clarity

Clear 0→0b→1→2→3→4 sequence with explicit validation (entry check, exit conditions, non-zero-exit stop) and a feedback loop (archive-reopen back to verify) around an irreversible operation.

3 / 3

Progressive Disclosure

Keeps the body an overview and defers detail to one-level-deep, clearly signaled references (comet/reference/scripts.md, decision-point.md, context-recovery.md) rather than inlining it.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise, well-targeted description with an explicit Use-when trigger, concrete named actions, and a clear niche that minimizes conflict risk. It is not a 2 on any dimension because every anchor (explicit trigger, multiple concrete actions, natural keywords, distinct niche) is satisfied.

DimensionReasoningScore

Specificity

Names multiple concrete actions — '确认归档', '合并 delta spec', '恢复 archive 阶段' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Opens with an explicit 'Use when ...' trigger and names the operations the skill performs, so both 'when' and 'what' are answered; the explicit trigger clears the completeness-2 cap.

3 / 3

Trigger Term Quality

Natural trigger terms for the niche ('验证已通过', '归档', '恢复 archive 阶段') give good coverage of the conditions a Comet user would actually express; not level 2 because no common trigger phrasing is missing.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to the Comet change archive phase with distinct triggers, making it 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
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.