Content
65%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.
The body is well-structured and largely executable, but it references bundle files (scripts, schema, template) that are not present, and the batch HTML-regeneration workflow lacks an explicit validation checkpoint. Fixing the missing bundle and adding a validate step would lift the two lowest dimensions.
Suggestions
Ship the referenced bundle (scripts/progress-snapshot.sh, scripts/render-html.sh, scripts/plan-brief-open.sh, scripts/writing-rule-list.sh, scripts/writing-rule-approve.sh, schemas/progress-snapshot.v1.schema.json, and the progress.html.template) so the signaled references resolve to real files.
Add an explicit validation checkpoint before opening the browser — e.g. after render-html.sh, verify $OUT_PATH is non-empty / valid HTML and surface render-html.sh's exit code before proceeding to Step 3.
Collapse the bilingual Mission quote and the やる/やらない lists, since Quick Reference and the Schema section already convey the same intent, to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with compact schema YAML, numbered steps, and a tight failure-mode table, but the bilingual Mission quote and the 'やる/やらない' lists restate intent already conveyed by Quick Reference, so minor trimming is possible. | 4 / 5 |
Actionability | Step 0–3 give concrete copy-paste bash with real flags and variable assignments, but the referenced scripts (progress-snapshot.sh, render-html.sh, plan-brief-open.sh) are not present in any bundle directory and schema fields are placeholders like '<basename of git repo>', leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clear Step 0→3 sequence with an explicit --no-open conditional and a failure-mode table is present, but there is no validate-before-open checkpoint or feedback loop for this batch HTML-regeneration operation, so workflow clarity is capped at 3 per the batch/destructive guidance. | 3 / 5 |
Progressive Disclosure | Sections are well organized and the schema detail is linked one level deep to ${CLAUDE_SKILL_DIR}/schemas/progress-snapshot.v1.schema.json, but no references/, scripts/, or assets/ bundle directories exist, so the referenced scripts, template, and schema file are not real — structure is good but the signaled references are broken. | 3 / 5 |
Total | 14 / 20 Passed |