Content
100%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 exemplary lean operational skill: executable commands, an explicit validation gate with an error-recovery loop, and dense project-specific constraints with no filler. Nothing material is missing from the body; the only weakness of the skill lives in its frontmatter description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is operational project-specific knowledge ('Never hand-edit a .patch', the resolutions workaround, the dev-shell cache-key behavior) with zero padding and no explanation of concepts Claude already knows. | 5 / 5 |
Actionability | Fully executable copy-paste blocks: the cp/node/npx patch-package sequence, the mktemp/unzip/git fallback diff, and the git apply --check verification. Placeholders like <pkg> and <version> are standard parameterization, not pseudocode, and the common cases are covered. | 5 / 5 |
Workflow Clarity | Clear sequence (edit node_modules -> generate -> fallback -> verify) with an explicitly required verification section and a feedback loop ('must be 0 (else rm -rf node_modules/<pkg>/android/build, regenerate)'), so the destructive-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | A sub-50-line single-file skill with well-organized headed sections and no external reference files needed; per the simple-skill guidance this structure merits full marks, and all internal references (patches/ paths, lint script, dev-shell command) are real and clearly signaled. | 5 / 5 |
Total | 20 / 20 Passed |