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 product landing page rather than a skill: it markets a shipped extension, answers FAQ questions about it, and links to a paid catalog, but provides no instructions, code, commands, or workflow for Claude to act on. Critically, it references source files in assets/extension/ that are absent from the bundle, as the body itself concedes, leaving the skill functionally empty.
Suggestions
Replace the marketing and FAQ sections with actual build instructions: a step-by-step sequence for creating the manifest.json, background service worker, content script, and popup files, with executable code for each.
Ship the referenced source in the bundle (e.g., assets/extension/ or reference templates the skill can copy), or remove the claim that generated output lives there — currently the only pointer in the document is to files that do not exist.
Add a verification checkpoint to the workflow, such as loading the unpacked extension in chrome://extensions and confirming the popup renders and the RDAP lookup returns a trust score, so failures can be caught and fixed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is padded marketing copy rather than instructions: "Why this beats prompting it yourself" and a six-question FAQ section repeat the same points ("no build step" appears in at least four sections) without adding guidance, which is noticeably verbose for a skill body. | 2 / 5 |
Actionability | The body only describes capabilities ("Calculates a 0 to 100 trust score based on SSL status, domain age via RDAP...") and never instructs Claude how to produce anything; the sole concrete action — loading the extension from assets/extension/ in chrome://extensions — points at files the body itself admits are not in this folder, so there is nothing executable at all. | 1 / 5 |
Workflow Clarity | No sequence of steps exists for generating the extension, and there are no validation checkpoints (e.g., manifest validation or verifying the unpacked extension loads); the "Example" section shows a fictional result rather than a process. | 1 / 5 |
Progressive Disclosure | Although sections are labeled, the only substantive reference ("the complete source in assets/extension/") is a dangling pointer to a directory that does not exist in the bundle, and the FAQ/marketing content is inlined material that belongs in separate files or nowhere at all. | 2 / 5 |
Total | 6 / 20 Passed |