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 reads as a product brochure rather than agent guidance: it is repetitive, promotional, contains no executable instructions, and its key reference (assets/extension/) is missing from the bundle. Claude reading this SKILL.md would learn almost nothing about how to actually build or customize the extension.
Suggestions
Remove the redundant FAQ section and the duplicated 'When to use' list — each restates facts already covered elsewhere in the file — and drop the promotional links (nex-ai.be, slopsome.com, paid catalog) that consume tokens without aiding execution.
Add an actionable build workflow: a minimal manifest.json example, the background-alarms and offscreen-diff wiring skeleton in executable code, and concrete steps for testing via chrome://extensions 'Load unpacked', so the agent has something it can actually run and extend.
Resolve the broken core reference: either include the promised assets/extension/ source files in the bundle or replace the 'You receive the complete assets/extension/ source directory' claim with self-contained instructions for generating the extension from scratch.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The same facts are repeated three times — the no-build vanilla stack appears in 'Supported architecture', 'When to use', and FAQ #2; offscreen-API performance appears in 'What it does', the features list, and FAQ #5; 'When to use' restates the frontmatter verbatim — plus promotional padding ('Built by Nex AI. More skills... at nex-ai.be and slopsome.com'). This is noticeably verbose with several padded sections (anchor 2); it is not anchor 1 because it does not explain concepts Claude already knows. | 2 / 5 |
Actionability | The body contains no code and no commands for the agent — it names files ('manifest.json', 'background.js', 'diff.js') and one end-user install step ('Open chrome://extensions, enable Developer Mode, and Load unpacked') but otherwise describes what the skill delivers rather than instructing how to do it. Minimal concrete guidance with missing execution steps matches anchor 2; not anchor 1 because a few concrete details (file names, install sequence) are present. | 2 / 5 |
Workflow Clarity | There is no development workflow at all — the only sequence is a rough three-beat install instruction buried in the 'Example' section, with many gaps (nothing on creating the manifest, writing the diff engine, wiring alarms, or testing) and no validation checkpoints. This fits anchor 2's 'rough sequence present but many gaps'; it falls short of anchor 3 because no real step list for the actual task exists. | 2 / 5 |
Progressive Disclosure | The body's central promise — 'You receive the complete assets/extension/ source directory' — references a directory that does not exist, and the body itself concedes 'Scripts, extension source, and templates from the original package are not in this folder'. With the core reference broken/absent and ~20 lines of redundant FAQ inlined, this matches anchor 2; it is not anchor 3 because the references are not merely unclear — they point to nothing. | 2 / 5 |
Total | 8 / 20 Passed |