Content
25%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 a marketing README rather than an actionable skill: it promotes a codebase that is not present, references an assets/extension/ path that does not exist, and spends most of its tokens on a promotional FAQ and repeated branding. Claude reading it learns what the extension is but has no instructions, code, or files to accomplish anything.
Suggestions
Ship the actual extension source (manifest.json, Shadow-DOM content script, service worker) in assets/ or references/ and make the SKILL.md reference match the real paths — currently 'assets/extension/' does not exist and the body admits the source is missing.
Replace the FAQ and 'Why use this skill?' marketing sections with actionable content: the file layout of the extension, how to customize the hotkey/panel/metrics, and concrete Chrome Web Store packaging steps (zip structure, icons, listing requirements).
Add a sequenced workflow with validation checkpoints, e.g.: 1) copy the extension folder, 2) load unpacked at chrome://extensions, 3) verify the inspector panel renders via Shadow-DOM on a test page, 4) zip the folder for Web Store upload.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is padded with promotional sections that earn no tokens: 'battle-hardened codebase', 'Why use this skill?', a six-question marketing FAQ, and branding repeated twice ('Built by Nex AI. More skills...'). It does not explain known concepts (so not a 1), but several entire sections are unnecessary filler. | 2 / 5 |
Actionability | The only concrete guidance is the install hint ('navigate to chrome://extensions... enable Developer mode... Load unpacked') and the Alt+Shift+I hotkey mention. No code, no manifest example, no file layout, and the extension source itself is absent, so Claude cannot actually execute the skill's stated purpose — minimal guidance with the specific steps missing. | 2 / 5 |
Workflow Clarity | There is only a rough install sequence buried in FAQ prose ('download the source files, navigate to chrome://extensions, enable Developer mode, click Load unpacked'); no build, customize, verify, or package workflow is sequenced, and validation steps are absent. Not 1 because that install sequence and the 'When to use' list give a rough, if gappy, order. | 2 / 5 |
Progressive Disclosure | Section headers exist, but the skill ships no bundle files at all (no references/, scripts/, or assets/ directories) and its one path reference — 'I've generated the extension in assets/extension/' — points to a non-existent location, while the body itself concedes the source 'is not in this folder'. For a skill whose entire value is a code bundle, this is minimal structure with a broken, unfulfilled reference. | 2 / 5 |
Total | 8 / 20 Passed |