Content
53%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 well-structured and token-efficient with clear ownership boundaries, routing, and a fail-fast validation stance. However, it delegates its core execution protocol to reference files that are missing from the bundle, so the skill as shipped offers no executable install flow, and the bundled scripts go unmentioned.
Suggestions
Inline the staged install sequence (quarantine, validate, install, refresh, rollback) as numbered steps with explicit validation checkpoints in SKILL.md, since the delegated `references/workflow.md` is absent from the bundle and currently leaves the core procedure unactionable.
Create the missing `references/` files (workflow.md, contract.yaml, evals.yaml, task-profile.json) or remove the dead links so progressive disclosure actually resolves.
Reference the existing bundle scripts (e.g., `scripts/install-plugin-from-github.py`) from the body so the executable tooling is discoverable instead of orphaned.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence: terse Inputs/Outputs, no re-teaching of concepts Claude knows. Minor trimmable instances remain, e.g., the maintenance-oriented line "Apply the context-disposition policy: move important still-valid context to references..." and overlap across Anti-Patterns, Failure Mode, and Gotchas. | 4 / 5 |
Actionability | Concrete details exist (output fields, the validation command, allowlisted hosts), but the actual install procedure is entirely delegated via "Use the staged install protocol in `references/workflow.md"" — and that file is absent from the bundle, leaving no executable steps for the core task. Fits anchor 3 (some concrete guidance, incomplete) better than anchor 2 since inputs, outputs, and a fail-fast gate command are specified. | 3 / 5 |
Workflow Clarity | The staged flow is only implied ("separate preview/quarantine validation from install, projection refresh, rollback") with no sequenced steps in the body, and the fail-fast validation policy ("stop at first failed gate and report blocker text") plus stop conditions are explicit but their checkpoints live in the missing workflow file. This lands on anchor 3: sequence present but implicit, validation described but not woven into ordered steps. | 3 / 5 |
Progressive Disclosure | References are clearly signaled ("Read when" bullets with reasons), but all four cited files under `references/` (workflow.md, contract.yaml, evals.yaml, task-profile.json) do not exist in the bundle, so the primary detailed-content pointer is dead. Additionally, the bundled `scripts/` files (install-plugin-from-github.py, github_utils.py) are never referenced from the body, leaving navigation broken rather than merely imperfect — below anchor 3's "references present". | 2 / 5 |
Total | 12 / 20 Passed |