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 functions as a promotional landing page rather than skill instructions: it markets a paid package, explains Chrome basics Claude already knows, and contains no actionable guidance, code, or workflow. Critically, it admits the advertised source code is not included in the bundle, so the skill cannot accomplish its stated purpose.
Suggestions
Replace the marketing and FAQ sections with concrete instructions: loading the unpacked extension in chrome://extensions, where the manifest and frame-drawing code live, and how to add a new device frame.
Actually bundle the extension source (or at minimum a working manifest.json and one frame-drawing module) so referenced paths like assets/extension/ and frames/macbook.js exist and the Example section is achievable.
Provide a real dev-to-store workflow with sequenced steps and verification checkpoints (e.g., reload extension, test capture, validate zip structure) instead of only claiming a 'proven dev-to-store workflow' exists.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is noticeably padded with marketing copy ('Unlike generic AI prompts that generate non-functional code snippets...'), repeated promotional links, and a five-question FAQ explaining concepts Claude already knows (Chrome Developer Mode loading, NPM/Webpack, Manifest V3 standards). | 2 / 5 |
Actionability | There is no code, command, or executable instruction anywhere in the body; it only describes ('Includes a proven dev-to-store workflow and packaging guide') and the stated source is absent — 'Scripts, extension source, and templates from the original package are not in this folder'. | 1 / 5 |
Workflow Clarity | No steps or sequence are provided; the 'Example' section is a fabricated dialogue claiming deployment to 'assets/extension/' and 'frames/macbook.js', paths that do not exist in the bundle. | 1 / 5 |
Progressive Disclosure | Sections are clearly headed, but the only file references (assets/extension/, frames/macbook.js) point to nonexistent paths and the actual material is deferred to an external paid package rather than bundled reference files, leaving navigation broken. | 2 / 5 |
Total | 6 / 20 Passed |