Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-sequenced skill body with concrete commands, strong validation gates, and a clear checklist. It is held back by verbatim-duplicated rules and by a References section that points to bundle files which are not actually present.
Suggestions
Remove the verbatim duplication of the 'Output Schema must be attached to a concrete Workflow Node' rule and the enforcement-tag list — state each once in Hard Rules and reference it from Core Model / Step 4 to tighten conciseness.
Create the five referenced files under comet-any/reference/ (authoring-protocol.json, authored-zone-example.md, bundle-authoring.md, authoring-subagents.md, eval-provider.md) or remove the References entries, so progressive disclosure resolves to real content.
Render reference paths as markdown links (e.g. [bundle-authoring.md](comet-any/reference/bundle-authoring.md)) instead of code-spans to make navigation explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, assumes Claude's competence, and contains no concept filler, but several rules are duplicated verbatim (the 'Output Schema must be attached to a concrete Workflow Node...' rule appears in both Core Model and Hard Rules, and the enforcement tag list 'guarded, handoff-guarded, evidence-only, advisory' appears in both Step 4 and Hard Rules), so it could be tightened to reach a 3. | 2 / 3 |
Actionability | It provides concrete, copy-paste-ready CLI commands with flags throughout (comet creator guide --project . --json, comet creator authoring-record <name> --lane <id> --file <out.json> --json, comet publish review <name> --platform <reference-platform> --json) plus a complete JSON plan example. | 3 / 3 |
Workflow Clarity | The 10-step Steps section is a clearly sequenced process with explicit validation/confirmation gates (pause for missing/ambiguous Skills, schema-validated authoring-record that rejects BLOCKED/NEEDS_CONTEXT, eval that cannot become ready on failure/stale hash, publish only after human approval) and a Hard Rules checklist, satisfying the feedback-loop requirement for a destructive/batch workflow. | 3 / 3 |
Progressive Disclosure | It has clear sections and a one-level-deep References list, but the five referenced files (comet-any/reference/*.json, *.md) do not exist anywhere in the bundle and are rendered as code-spans rather than navigable links, so the disclosure does not actually resolve; some inline detail (full Plan Example JSON, Protected Boundary rules) could also be externalized. | 2 / 3 |
Total | 10 / 12 Passed |