Content
68%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.
An efficiently written, well-organized instruction skill hampered by missing referenced files and a stub install script pointing at a nonexistent .pyw, which leaves the core flow non-executable from the body.
Suggestions
Add the missing references/workflow.md (or inline the staged install protocol) so the quarantine → validate → install → rollback sequence is visible with explicit checkpoints.
Provide the missing install-plugin-from-github.pyw the CLI stub runs, or inline executable install code, so the central action is copy-paste ready.
Either create the other referenced files (contract.yaml, evals.yaml, task-profile.json) or remove them from the References list to keep navigation intact.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean, terse bullet structure that assumes Claude's competence and never pads with explanations of what plugins or provenance are; every section earns its place. | 5 / 5 |
Actionability | Concrete validation command, allowlist URLs, and explicit input/output field lists are present, but the core install flow is delegated to a missing references/workflow.md and the install script stub targets a nonexistent .pyw, so the central action is not executable from the body. | 3 / 5 |
Workflow Clarity | Validation and fail-fast checkpoints exist, but the staged install sequence (quarantine → validate → install → rollback) is delegated to a missing workflow.md rather than shown in-body; the destructive/batch cap of 3 applies. | 3 / 5 |
Progressive Disclosure | Clear section structure with well-signaled 'Read when:' navigation and one-level-deep references, but several referenced files (references/workflow.md, contract.yaml, evals.yaml, task-profile.json) do not exist in the bundle, so navigation is partly broken. | 4 / 5 |
Total | 15 / 20 Passed |