Content
88%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 content is highly actionable with executable recipes and a rigorous validation gate, clear sequenced workflows with explicit checkpoints, and tight mostly-padding-free prose. Its main limitation is progressive disclosure: as a single large file with no reference split, some lengthy material is inlined rather than externalized.
Suggestions
Split the lengthy block-level-lock raw-set digression and the full contract/SOW recipe into reference files (e.g. references/block-lock.md, references/sow-recipe.md) referenced one level deep from SKILL.md to improve progressive disclosure.
Consolidate the protection=forms mechanics, which are restated across 'Shell & Execution Discipline', 'Document protection & lock', and the Delivery Gate, into a single authoritative section to tighten conciseness.
Resolve the few illustrative placeholders (e.g. '/body/sdt[N]' in readback commands and the manual 'copy signatory_name path, then: set …' step in sow-c) so the core recipes are fully copy-paste runnable without an intermediate manual action.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and mostly free of padding — it defers flag enumeration to 'help' and avoids explaining basic concepts — but the protection=forms mechanics are restated across several sections and the block-level-lock raw-set digression (long inline Python/XML) is verbose, keeping it just below the every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Provides fully executable, copy-paste bash recipes (Quick Start, Path A/B/C, MERGEFIELD patterns, FormField, batch heredoc) and a six-gate Delivery Gate script, with concrete examples covering the common form cases (dropdown w/ items, date format, checkbox, mail-merge, conditional IF). | 5 / 5 |
Workflow Clarity | Gives an explicit build-order sequence, marks 'protection=forms is the LAST structural command', enforces 'one command at a time, read output before the next', and ships an executable Delivery Gate with per-gate OK/REJECT feedback and exit-on-failure, providing clear validation checkpoints and error-recovery loops for a mutation/batch skill. | 5 / 5 |
Progressive Disclosure | Internal section structure is strong and well-organized (decision tables, recipes, Known Issues, Delivery Gate), but with no bundle reference files the ~670-line monolith inlines material (block-level-lock digression, full contract/SOW recipe) that a more progressive layout would externalize, landing just below the clear-overview-with-one-level-deep-references anchor. | 4 / 5 |
Total | 18 / 20 Passed |