comet

Comet — OpenSpec + Superpowers dual-star development workflow. Start with /comet for automatic phase detection and dispatch to subcommands. Five phases: open → design → build → verify → archive.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./eval/local/skills/benchmarks/039-release/comet-classic-039/SKILL.md

Quality

Content

77%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 highly actionable with a clearly sequenced, well-validated multi-phase workflow and concrete commands throughout. Its weak spots are repeated emphasis on the blocking-decision-point rule and references to comet/reference/*.md files that are not present in the bundle.

Suggestions

Include the referenced comet/reference/*.md files (comet-yaml-fields, file-structure, auto-transition, context-recovery, decision-point, debug-gate, dirty-worktree) in the bundle so signaled references resolve.

Consolidate the repeated blocking-decision-point guidance into one canonical statement plus the Red Flags table, removing the restatements across the Phase Transitions section.

Tighten the env-loading boilerplate block or move the full version into a reference file, keeping only the minimal load snippet inline.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational rather than padded with concepts Claude already knows, but the blocking-decision-point rule is restated across multiple IMPORTANT blocks and a Red Flags table, which could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands (the comet-env.sh loader, `openspec list --json`, `"$COMET_BASH" "$COMET_STATE" set/transition/next`, `"$COMET_BASH" "$COMET_ARCHIVE"`) with clearly indicated parameter slots covering the common cases.	5 / 5
Workflow Clarity	Sequences Steps 0–2 with an ordered first-match-wins phase determination, explicit validation guards, a verify-fail feedback loop, and an archive confirmation gate; destructive/batch operations have validation, so no cap applies.	5 / 5
Progressive Disclosure	Structure and reference signaling are good (clear Reference Appendix pointing to comet/reference/*.md at one level deep), but the referenced .md files are absent from the actual bundle, leaving dangling navigation that goes beyond a minor gap.	3 / 5
	Total	16 / 20 Passed

Description

70%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 specific, distinctive, and names concrete workflow actions with an explicit invocation trigger. Its main weakness is the lack of an explicit "Use when…" trigger clause, leaving the activation conditions weakly implied.

Suggestions

Add an explicit "Use when…" clause stating the situations that warrant this workflow (e.g., making spec-driven changes spanning OpenSpec proposals and Superpowers execution).

Briefly characterize what each of the five phases produces so the capability coverage reads as comprehensive rather than structural.

Dimension	Reasoning	Score
Specificity	Names the domain ("OpenSpec + Superpowers dual-star development workflow") and several concrete actions ("automatic phase detection and dispatch to subcommands", "Five phases: open → design → build → verify → archive"), with only minor coverage gaps on what each phase does.	4 / 5
Completeness	Clearly states what the skill does, but the "when" is only weakly implied via "Start with /comet for automatic phase detection" with no "Use when…" clause, so completeness is capped at 3 per the guideline.	3 / 5
Trigger Term Quality	Provides an explicit "/comet" invocation trigger and the five phase names as keywords; good coverage, though a few natural-language synonyms a user might voice are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (the OpenSpec + Superpowers dual-tool workflow with a distinct five-phase chain) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: eval/local/skills/benchmarks/039-release/comet-classic-039/SKILL.md
Commit: 899d1fb

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.