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 is a marketing README rather than operating instructions: it promotes a codebase it explicitly does not include, and every reference to extension source files is broken because no bundle files exist. A Claude invoking this skill would have nothing concrete to execute, only descriptive copy and a generic Chrome loading walkthrough.
Suggestions
Include the actual Manifest V3 extension source in assets/ (or scripts/) so the referenced paths (assets/extension/, fontmatch.js, content.js) resolve, and replace the fictional 'Result' dialog with real instructions for using those files.
Replace the FAQ and promotional sections ('Why use this skill', 'Questions', footer links) with actionable guidance: manifest structure, how to modify the font-mapping JSON, and concrete export-format examples (CSS, shorthand, Tailwind).
Add a real workflow with validation checkpoints, e.g. load unpacked -> verify the overlay activates on a test page -> confirm font match output, so failures have a recovery path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The FAQ section ('What exactly is included...', 'How does this skill differ...') restates the 'What you get' section, and promotional links to nex-ai.be, slopsome.com, and a paid catalog are pure padding. Several sections add no instructional value, matching anchor 2 rather than 1 since it doesn't explain concepts Claude already knows. | 2 / 5 |
Actionability | No code or commands beyond generic chrome://extensions loading steps, and the core deliverable is explicitly absent ('Scripts, extension source, and templates from the original package are not in this folder'). References to assets/extension/, fontmatch.js, and content.js point to files that do not exist in the bundle, so there is nothing executable to act on. | 2 / 5 |
Workflow Clarity | Only a loose implied sequence (generate source, then load unpacked) inside a fictional Example dialog, with no validation steps; the first step depends on files missing from the bundle. This matches anchor 2 (rough sequence, many gaps, validation absent) and is not a destructive/batch skill so the cap-3 rule is not binding. | 2 / 5 |
Progressive Disclosure | Scored against the actual bundle structure: no references/, scripts/, or assets/ directories exist, so the body's references to assets/extension/, fontmatch.js, and content.js are all dangling. Structure is minimal with broken references, fitting anchor 2 rather than 3 (references are not merely unclear, they resolve to nothing). | 2 / 5 |
Total | 8 / 20 Passed |