Content
11%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 landing page rather than skill instructions: it repeatedly promotes a complete source package that is explicitly not included, contains no code, commands, or sequenced workflow, and pads its token budget with FAQ restatements and promotional links. As shipped, the skill gives Claude nothing actionable to execute.
Suggestions
Include the actual extension source (manifest.json, content.js, detectors, UI assets) in assets/ or references/ so the 'complete, shipped source code' claim is real, and point to those files from clearly signaled sections in SKILL.md.
Replace the FAQ and promotional sections with a concise step-by-step workflow: copy the extension folder, enable Developer Mode, 'Load unpacked' in chrome://extensions, edit, and reload — with a verification checkpoint (e.g., confirm the extension is listed and test on a page with a cookie banner).
Trim the duplicated capability descriptions ('What it does', 'Supported Features', and the FAQ all restate the same three points) down to one compact overview, and mention concrete clutter targets (cookie banners, chat widgets, sticky headers, popups) so the skill's scope is actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is noticeably padded: the FAQ section restates 'What it does' and 'Supported Features' nearly verbatim (no-build vanilla JS, categorized detection engine, reversibility each appear three times), and promotional boilerplate ('Built by Nex AI. More skills and info at nex-ai.be and slopsome.com', a 'What exactly is included in the purchase?' answer) earns no tokens, matching anchor 2's 'several unnecessary explanations or padded sections'. | 2 / 5 |
Actionability | There is no executable guidance anywhere — no manifest snippet, no content-script code, no commands. The body only describes ('It uses a sophisticated detection engine that classifies elements into categories') and even concedes the deliverable is absent: 'Scripts, extension source, and templates from the original package are not in this folder.' This is an exact anchor-1 match ('only describes rather than instructs'). | 1 / 5 |
Workflow Clarity | The dev workflow the skill promotes (load unpacked in chrome://extensions, edit, reload, verify) is never sequenced; only fragments exist ('Requires manual reload in chrome://extensions after edits'), and the Example section fabricates a result ('I've generated the full source code... in assets/extension/') pointing at a directory that does not exist. Steps are effectively missing, matching anchor 1. | 1 / 5 |
Progressive Disclosure | Section headers exist, but the only substantive pointer is to a nonexistent assets/extension/ path (no references/, scripts/, or assets/ directories are present in the bundle), so navigation to the actual material is broken. Combined with FAQ/marketing content inlined into SKILL.md that belongs elsewhere, this fits anchor 2 ('minimal structure... references are buried' / misplaced content) rather than anchor 3's 'references present but not clearly signaled'. | 2 / 5 |
Total | 6 / 20 Passed |