Content
75%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 a strong, highly actionable instruction skill: exact commands, a naming scheme with worked examples, explicit validation, and failure handling. Its main weaknesses are redundancy — the naming template repeated three times and a leftover Output section that contradicts the customization by describing the disabled numeric/timestamp prefixes — and the absence of a recovery loop after validation failure.
Suggestions
Delete or rewrite the trailing Output section: it documents BRANCH_NAME examples like "003-user-auth" or "20260319-143022-user-auth" that contradict the rule disabling sequential/timestamp numbering, leaving only the note that FEATURE_NUM equals the full branch name.
State the branch-name template once (in the Mandatory Branch Naming section) and have the Execution section reference it, replacing the duplicated composition block; parameterize the shell examples with <VERSION>/<TYPE>/... placeholders instead of repeating the same hard-coded STAFF-0003 example in both blocks.
Add a short recovery step after the validation regex mismatch (e.g. re-resolve the misparsed component, rebuild the name, re-run) to complete the validate → fix → retry loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly rule-dense and efficient, but the naming template is stated three times (Mandatory Branch Naming, Execution step 2, and the hard-coded example inside both shell blocks), and the trailing Output section re-describes the legacy "003-user-auth" / "20260319-143022-user-auth" output that the body explicitly disables — noticeable redundancy that could be tightened. Not a 4 because these padded/contradictory sections are more than minor trimmings; not a 2 because most sections carry real, non-redundant guidance. | 3 / 5 |
Actionability | The guidance is fully executable: exact branch-name composition rules, copy-paste-ready bash and PowerShell invocations with GIT_BRANCH_NAME and the JSON flag, an exact validation regex, and the exact warning string for degradation. Specific examples cover the common cases (feat example, Trello defaults, both shells). | 5 / 5 |
Workflow Clarity | There is a clear sequence (resolve inputs → compose name → invoke script → validate against regex) with an explicit validation checkpoint that aborts on mismatch, plus graceful degradation when Git is absent. Not a 5 because there is no fix-and-retry loop after a validation failure (only abort), and the contradictory Output section muddies what the expected result actually is; well above a 3 given the explicit regex checkpoint and error path. | 4 / 5 |
Progressive Disclosure | No bundle files exist, and the single-file body is well-sectioned with clear headers, no nested references, and nothing that clearly belongs in a separate file — matching the anchor for good structure with minor organization gaps. Not a 5 because the stale, duplicated Output section is an organization gap that should be trimmed, and the file runs past the under-50-lines simple-skill range. | 4 / 5 |
Total | 16 / 20 Passed |