Content
86%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 an exemplary lean, fully executable workflow: concrete commands, an explicit verification step before the irreversible clone, and precise guidance on passing the project path. Its only weaknesses are the redundant opening line and the absence of an explicit error-recovery branch when the preview verification fails.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence (exact shell commands, no concept explanations); the only trim candidate is the opening line, which restates the frontmatter description verbatim. Not 5 because that duplicated sentence costs tokens without adding information; not 3 because there is no over-explanation. | 4 / 5 |
Actionability | Every step is copy-paste ready: the exact `tail -1 ~/.claude/history.jsonl | jq -r ...` command, a version-sorted `find` for the script, preview/run invocations, and the exact `claude --resume <new-session-id>` command. The `<script-path>` placeholder is resolved by step 2, so the guidance is fully executable and covers the common cases. | 5 / 5 |
Workflow Clarity | Clear numbered sequence with an explicit validation checkpoint (step 3: preview and 'Check that the first and last messages match the current conversation'), plus a fallback path for resuming. Not 5 because there is no error-recovery branch for what to do when the preview does not match; not 3 because a concrete checkpoint is explicitly present. | 4 / 5 |
Progressive Disclosure | A single-task skill under 50 lines with no bundle files (no references/, scripts/, or assets/ directories) and no need for external references; the well-organized numbered steps and the dynamic script-lookup note with rationale satisfy the simple-skill exception. | 5 / 5 |
Total | 18 / 20 Passed |