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 reads as a product landing page rather than an operational skill: marketing prose, a sales FAQ, and claims of "complete high-fidelity source code" that is explicitly not included in the folder, with dangling references to assets/extension/, analyzer.js, and sites.js. There is no executable code, no sequenced workflow with validation, and no actual developer loop or submission checklist despite both being promised. Almost all instructional value is absent from the shipped bundle.
Suggestions
Ship the actual extension source in assets/extension/ (manifest.json, analyzer.js, sites.js, background worker, side-panel UI) or remove all references to files that are not in the bundle — the current dangling references make the skill's core promise unexecutable.
Replace the marketing sections ("Why use this skill", "What you get") and the purchase-oriented FAQ with a numbered workflow: load unpacked via chrome://extensions, test on a sample review page, verify the side-panel trust score output, then follow a concrete Chrome Web Store submission checklist.
Cut the duplicated promotional footers and restated "When to use" triggers; the ~85-line body can be reduced to a lean overview plus the install/customize/publish steps, cutting token cost by more than half.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Multiple padded, non-instructional sections: "Why use this skill" ("bypasses the 'blank page' problem"), a five-question FAQ that restates earlier sections (Q1 repeats "What it does"), purchase-oriented filler ("Buyers receive the current stable version", "after purchase"), and promo links repeated in "What you get" and the footer. This is noticeably verbose with several sections that earn no tokens; it avoids a 1 only because it does not extensively teach concepts Claude already knows. | 2 / 5 |
Actionability | The body's central promise — "I've generated the complete Manifest V3 source in `assets/extension/`" — points at files that do not exist in this bundle (the body itself admits "Scripts, extension source, and templates from the original package are not in this folder"), so the primary task cannot be executed. The only concrete procedure is the prose FAQ instruction to "navigate to chrome://extensions... enable 'Developer mode,' and click 'Load unpacked'"; the rest is descriptive marketing. That is minimal concrete guidance with missing execution steps, not the incomplete-but-present guidance of a 3. | 2 / 5 |
Workflow Clarity | A rough sequence (download source → load unpacked → customize → submit to Web Store) exists but is scattered across marketing prose and FAQ answers rather than presented as steps. There are no validation checkpoints, and the promised "developer loop for rapid iteration and a checklist for Chrome Web Store submission" are mentioned but never actually provided. This matches a rough sequence with many gaps and absent validation. | 2 / 5 |
Progressive Disclosure | The bundle contains no references/, scripts/, or assets/ directories, yet the body directs the reader to `assets/extension/`, `analyzer.js`, and `sites.js` — dangling references to files that are not shipped. Section headers give the document minimal structure (so it is not a monolithic wall), but the core content that clearly belongs in bundle files is simply missing, making the file layout ineffective. | 2 / 5 |
Total | 8 / 20 Passed |