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 brochure rather than a skill: it markets a shipped extension but contains none of the actual source, scripts, or templates it references, and offers no executable guidance for building or deploying anything. Its few redeeming parts are the features list, known limitations, and install instructions. Structurally the sections are well-labeled, but every referenced bundle path is dangling.
Suggestions
Ship the actual bundle: create assets/extension/ with the extension source (manifest.json, service worker, popup) and the heavysites.json heuristic database the body references, or remove the references and the 'not in this folder' disclaimer.
Replace the marketing copy ('Why use this skill', footer promos, and the FAQ that restates the description) with a concrete build workflow: file layout, the domain-weight/memory heuristic formula with a code snippet, and the Chrome Web Store packaging steps.
Add validation checkpoints to any workflow involving tab auto-closing (e.g., verifying tab age and excluding pinned/playing-media tabs before closing), since closing tabs is a semi-destructive batch operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is padded with promotional material repeated three times ('Built by Nex AI' in the header note, the features section, and the footer) and a FAQ 'Questions' section that largely restates the description, plus paid-catalog marketing links. | 2 / 5 |
Actionability | No code, commands, or build instructions appear anywhere; the only concrete items (chrome://extensions install steps, 'Green <2GB, Red >4GB' thresholds, 60-minute idle cutoff) are product specs rather than executable guidance, and the referenced 'assets/extension/' and 'heavysites.json' do not exist in the bundle. | 2 / 5 |
Workflow Clarity | There is no workflow for the skill's core purpose: no file layout, no steps for implementing the heuristic engine, and no Chrome Web Store packaging sequence despite it being claimed as a feature; only a rough install sequence exists with no validation checkpoints. | 2 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/ directories), yet the body points to 'assets/extension/' and 'heavysites.json' and admits 'Scripts, extension source, and templates from the original package are not in this folder' — navigation signals content that is not delivered. | 2 / 5 |
Total | 8 / 20 Passed |