Content
17%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 landing page for the skill rather than the skill itself: it markets capabilities, includes an FAQ and promotional links, and explicitly states the extension source is not in the folder. It provides no executable guidance, no workflow, and references bundle paths that do not exist.
Suggestions
Replace the FAQ, promotional links, and marketing sections with the actual extension source layout (manifest.json, background.js, offscreen document, pdf-gen.js) or at minimum concrete build/usage steps.
Provide an explicit workflow: scaffold the extension files, implement the scroll-and-capture loop, stitch via the offscreen document, export PDF locally, then verify by loading unpacked in chrome://extensions.
Fix progressive disclosure by actually shipping the referenced /assets/extension/ files or removing the dangling references and inlining concise, working code in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is promotional copy: a five-question marketing FAQ, a "Why use this skill?" pitch, and repeated plugs ("Built by Nex AI. More skills and info at nex-ai.be and slopsome.com", a paid-catalog link). Several sections are pure padding; not 1 only because it does not explain concepts Claude already knows — it explains nothing technical at all — but nearly the whole document is unnecessary. | 2 / 5 |
Actionability | There is no code, command, file layout, or concrete instruction for the skill's core task; the document "only describes rather than instructs". The stated deliverable itself is absent: "Scripts, extension source, and templates from the original package are not in this folder", so Claude cannot execute anything. | 1 / 5 |
Workflow Clarity | Only a rough install sequence exists (enable Developer mode, click Load unpacked); the actual workflow — generating the extension, viewport stitching, PDF export — is entirely absent with no validation checkpoints. Not 1 because a rough, usable load-and-test sequence is written out in the FAQ. | 2 / 5 |
Progressive Disclosure | The body points to "/assets/extension/" and "pdf-gen.js", but no assets/, scripts/, or references/ directories exist, so the primary reference is broken and the content that belongs in separate files is simply missing. Not 1 because section headers are present and there is no nested reference chain. | 2 / 5 |
Total | 7 / 20 Passed |