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 promotional landing page rather than a skill: it markets a shipped extension, but contains no instructions, no code, no workflow, and no bundle files — the advertised extension source is missing from the package entirely. Invoking this skill would leave Claude with nothing actionable to execute. The description is well written, which makes the hollow content especially misleading.
Suggestions
Include the actual extension source (manifest.json, content.js, platforms.js, popup.html, etc.) in the bundle so the promised `assets/extension/` reference resolves, and list the files with one-line descriptions so Claude knows what each contains.
Replace the marketing and FAQ sections with actionable guidance: how to scaffold the extension, how to load it in Chrome Developer Mode, how to add a new platform pattern, and the concrete steps for Web Store publishing.
Add a sequenced workflow with validation checkpoints (e.g., detect links -> inject button -> verify host-page layout is unbroken -> test on a dynamic app like Gmail), and trim the restated 'Why use this skill' / 'What you get' / FAQ padding to respect the token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is padded marketing copy: 'battle-tested, production-ready', a 'Why use this skill?' section, a 'What you get' section, and a six-question FAQ whose answers restate earlier sections. This matches the 'noticeably verbose; several unnecessary explanations or padded sections' anchor; not 1 because it does not explain concepts Claude already knows, it just self-promotes. | 2 / 5 |
Actionability | There is no executable guidance anywhere: no code, no commands, and no steps — the body only describes behavior ('Scans pages for meeting links... using a robust MutationObserver') rather than instructing. The Example even claims output 'in `assets/extension/`', a path that does not exist in the bundle, which is a perfect match for the 'entirely vague; only describes rather than instructs' anchor. | 1 / 5 |
Workflow Clarity | No sequence of operations is present; the body never tells Claude what to do when the skill is invoked, and there are no validation checkpoints of any kind. This matches the bottom anchor ('steps missing or incoherent; no sequence'). | 1 / 5 |
Progressive Disclosure | Although the body has section headers, the skill's entire payload is supposed to live in bundle files that are absent: 'A complete `/extension` directory' and '`assets/extension/`' are dangling references, and the body admits 'Scripts, extension source, and templates from the original package are not in this folder.' This matches the 'minimal structure' anchor; not 3 because the promised separate files do not exist at all, leaving the disclosure structure broken rather than merely improvable. | 2 / 5 |
Total | 6 / 20 Passed |