Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with concrete commands, a verbatim greeting, and explicit git/delegation rules, but it is padded with repeated command listings, time-sensitive YAML metadata, and a monolithic inline structure that could be split out. Workflows are sequenced but lack explicit feedback loops for merge operations.
Suggestions
De-duplicate the command listings: keep a single authoritative command table and have the Quick Commands and YAML 'commands' sections reference it instead of re-listing every command.
Add an explicit validate→fix→retry loop for local merges (e.g. run *story-checklist, and on merge conflicts: resolve, re-validate, retry) so the workflow_clarity checkpoint is not implicit.
Move the large embedded YAML agent definition and time-sensitive metadata (autoClaude version, migratedAt) into a referenced file under references/ so SKILL.md stays a lean overview with one-level-deep navigation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The command set is repeated three times (Star Commands table, the YAML 'commands' block, and Quick Commands) and the activation substeps are verbose; time-sensitive metadata like 'migratedAt' and 'autoClaude version: 3.0' in the YAML add tokens that do not aid execution, so it is mostly efficient but could be tightened. | 2 / 3 |
Actionability | Provides exact prefixed commands (*draft, *story-checklist), a verbatim greeting, an explicit git allow/block list (e.g. 'git checkout -b feature/X.Y-story-name' allowed, 'git push' blocked), and concrete delegation/handoff tables — fully actionable guidance for an instruction-only skill. | 3 / 3 |
Workflow Clarity | The 'Typical Workflow' is a clear numbered sequence with a *story-checklist validation checkpoint and an activation fallback, but there is no explicit validate→fix→retry feedback loop for the destructive local-merge operations, so checkpoints are partly implicit. | 2 / 3 |
Progressive Disclosure | It is a single ~330-line file with a large inline YAML agent definition and no bundle files to offload detail into; headers give it structure and the one command-authority-matrix reference is one level deep, but content that could be separate is inline, so it is organized but monolithic. | 2 / 3 |
Total | 9 / 12 Passed |