Content
85%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 dense, security-conscious instruction skill with fully sequenced steps, pervasive fail-closed validation checkpoints, and an appropriately delegated single reference. Its weaknesses are redundancy across sections, run-on sentences that hurt readability, and unspecified command inputs ($QUERY, $TITLE).
Suggestions
Deduplicate the duplicate-search and label rules that appear in both Hard Rules and Execution Steps, keeping one authoritative statement and one pointer.
Split the long compound sentences in steps 1 and 5 into discrete rules, and add a one-line example of how to build the duplicate-search $QUERY.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body contains no explanations of concepts Claude already knows; every line is non-obvious domain policy with concrete commands. However, duplicate-search and label rules are restated across Hard Rules and steps 4/6/7, and steps 1 and 5 contain very long compound sentences that could be tightened, keeping it at the efficient-with-minor-trimming level. | 4 / 5 |
Actionability | Concrete, executable gh commands are given for label enumeration, duplicate search, candidate capture, create/comment, and read-back, backed by a label expansion contract. Minor gaps remain, such as how to construct $QUERY for the duplicate search and what $TITLE should look like, so it is not fully copy-paste ready. | 4 / 5 |
Workflow Clarity | Nine clearly sequenced steps with explicit validation checkpoints: identity verification against the exact target host, read-back comparison with normalization rules, fail-closed stop conditions, cleanup on every terminal path, and a confirmed | no_write | unknown classification with no blind retries. Validation is thoroughly present for this write-capable workflow, so no cap applies. | 5 / 5 |
Progressive Disclosure | The single bundle reference, references/delegated-workflow-actions.md, exists, is clearly signaled as normative ("read ... completely ... It is normative, not optional background"), and is one level deep with no nested references. The core workflow is inline while delegated post-publication mutation rules live in the reference — content is appropriately split and easy to navigate. | 5 / 5 |
Total | 18 / 20 Passed |