Content
73%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, highly actionable execution skill: the 8-step workflow is clearly gated with validation checkpoints (manifest-hash binding, verify-current rules, red-line check, receipt-before-status), and the bundle reference is real and well-signaled. The main cost is token efficiency — registry mechanics are stated three times and the channel-matrix's wave/red-line content is restated in the body — and a sample output artifact would make the guidance fully concrete.
Suggestions
State the registry proposal mechanics (authorized `operation: propose` to `registry-events.py`, never write the dossier directly) once — in the Skill Contract's Writes bullet — and have steps 8 and Save Results reference it instead of restating it.
Move the wave-tier timings and the red-line list out of steps 6–7 and into references/channel-matrix.md, keeping only a one-line pointer plus the single most safety-critical red line (no vote solicitation) inline.
Add one worked example of a T-0 submission-status line (the exact ndjson event shape) so the most frequent output is copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and prescriptive with no padding about concepts Claude already knows, but it repeats itself: the registry-proposal mechanics ('an authorized `operation: propose` request to `registry-events.py`' with 'never write the dossier directly') appear in three places (Skill Contract Writes, step 8, Save Results), the RAMP non-computation rule twice, and steps 6–7 restate the wave tiers and red lines that already live in references/channel-matrix.md. Mostly efficient, but it could be meaningfully tightened by deduplicating. | 3 / 5 |
Actionability | Guidance is concrete and executable throughout — the exact title template 'Show HN: <what it is, stated plainly>', named per-sub table columns (subreddit, self-promotion rule as written, required flair/format, account-history expectations), wave timings, and the exact save path 'memory/launch/community-launch-runner/YYYY-MM-DD-<launch-slug>-submissions.md'. It falls short of fully copy-paste-ready because no worked output example (a sample maker-comment skeleton or a sample T-0 status line) demonstrates the common cases. | 4 / 5 |
Workflow Clarity | Eight clearly sequenced steps with explicit validation checkpoints: step 1 hard-gates on the manifest hash and SHIP verdict ('Missing accepted state or a mismatch is Unknown/NEEDS_INPUT; do not submit against it'), step 2 verifies each community's current rules and drops barred channels, step 7 runs the red-line check before execution, and step 8 enforces receipt gating ('Only after receipt evidence exists may the corresponding dated status fact be proposed') with explicit handling of partial/failed/missing receipts — a full feedback loop for a batch-submission workflow. | 5 / 5 |
Progressive Disclosure | The body is a well-sectioned overview (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with a clearly annotated Reference Materials list, and its one bundle reference, references/channel-matrix.md, is real, one level deep, and accurately described. It misses the top anchor because the wave-tier table and red-line list from that reference are duplicated inline in steps 6–7 rather than kept solely in the file. | 4 / 5 |
Total | 16 / 20 Passed |