CtrlK
BlogDocsLog inGet started
Tessl Logo

comet-open

Use when Comet 需要创建新的 OpenSpec change,或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。

63

Quality

74%

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 ./eval/local/skills/benchmarks/040-beta/comet-open/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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, well-sequenced workflow with strong validation checkpoints and concrete commands. Its main weakness is repetition that hurts conciseness, and a long inlined PRD-split subsection that could be externalized.

Suggestions

Deduplicate the repeated prohibition about not creating proposal.md/design.md/tasks.md before user confirmation — state the rule once and reference it from each blocking point.

Extract the large Step 1a PRD-split precheck (candidate list format, split conditions, batch-mode rules) into a dedicated reference file and link to it, keeping SKILL.md as an overview.

Inline a one-line note on how $COMET_STATE and $COMET_GUARD are resolved (or confirm the scripts.md reference covers it) so the bash commands are fully self-contained.

DimensionReasoningScore

Conciseness

Mostly efficient procedural prose, but several prohibitions are repeated verbatim across blocking points (e.g. '不得在用户确认...前创建 proposal.md/design.md/tasks.md') and Step 1a restates the same constraints multiple times, so it could be tightened.

3 / 5

Actionability

Provides concrete, copy-paste-ready bash commands (openspec status/instructions, node "$COMET_STATE" init/check/next, node "$COMET_GUARD" ... --apply) and explicit Skill-tool invocations, with a minor gap that $COMET_STATE/$COMET_GUARD resolution is delegated to an external reference.

4 / 5

Workflow Clarity

Clear numbered sequence (Steps 0-5) with explicit blocking checkpoints, validation steps (status --json, check, file-existence checks), feedback loops (failure handling, idempotent resume, '需要调整' retry), and an exit-conditions checklist.

5 / 5

Progressive Disclosure

Well-sectioned with clearly signaled one-level-deep external references (comet/reference/decision-point.md, scripts.md, auto-transition.md); minor gap because the lengthy PRD-split logic in Step 1a is inlined rather than split into its own reference.

4 / 5

Total

16

/

20

Passed

Description

75%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 clear, third-person, trigger-led description that names concrete actions and specific artifacts within a well-defined niche. It is strong but not maximal because actions are limited to two scenarios and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

Names concrete actions ('创建新的 OpenSpec change') and specific artifacts (proposal/design/tasks/.comet.yaml), listing two distinct trigger scenarios with minor coverage gaps.

4 / 5

Completeness

Has an explicit 'Use when' trigger and a clear what (create changes / initialize missing artifacts); both what and when are present with the when quite explicit.

4 / 5

Trigger Term Quality

Includes natural phrases a Comet user would say ('创建新的 OpenSpec change', 'active change 缺少 proposal/design/tasks/.comet.yaml') with good keyword coverage, though a few synonymous variants are missing.

4 / 5

Distinctiveness Conflict Risk

The Comet/OpenSpec niche and specific .comet.yaml artifact references make it mostly distinct, with minor overlap risk against sibling Comet phase skills that also handle active changes.

4 / 5

Total

16

/

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.