browser-extension-builder
Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing.
69
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/browser-extension-builder/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and trigger term coverage for browser extension development. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The description also uses 'Expert in' framing which is slightly informal but not first/second person.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building, debugging, or publishing browser extensions, or mentions Chrome extensions, Firefox add-ons, manifest files, or content scripts.'
Rephrase the opening from 'Expert in building...' to a more action-oriented third-person form like 'Guides building browser extensions that solve real problems' to better match the expected voice.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. These are concrete, actionable areas rather than vague language. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain description, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'browser extensions', 'Chrome', 'Firefox', 'cross-browser', 'manifest v3', 'content scripts', 'popup UIs', 'Chrome Web Store'. These cover many natural variations of how users would describe extension development needs. | 3 / 3 |
Distinctiveness Conflict Risk | Browser extension development is a clear, distinct niche. Terms like 'manifest v3', 'content scripts', 'Chrome Web Store publishing' are highly specific to this domain and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides good, executable code examples for core extension development tasks (manifest v3, content scripts, storage, messaging), which is its primary strength. However, it suffers from significant verbosity with redundant sections (expertise/capabilities lists, role description), a monolithic structure with no progressive disclosure, and lacks a clear end-to-end build workflow with validation checkpoints. The monetization and collaboration sections add token cost without proportional value.
Suggestions
Remove redundant sections (Role, Expertise, Capabilities lists) that repeat the same information and explain concepts Claude already knows—consolidate into a lean overview.
Add an explicit build/test workflow with validation steps: e.g., load unpacked extension in chrome://extensions, check for manifest errors, test content script injection, verify permissions before publishing.
Split the monolithic content into separate files (e.g., CONTENT_SCRIPTS.md, STORAGE.md, MONETIZATION.md, PUBLISHING.md) and reference them from a concise SKILL.md overview.
Remove or drastically shorten the Collaboration/Delegation Triggers/When to Use/Limitations boilerplate sections that consume tokens without adding actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity: the 'Role' description, 'Expertise' list, and 'Capabilities' list are redundant with each other and with the description. Sections like 'Collaboration', 'Delegation Triggers', workflow descriptions, and 'When to Use' add substantial token overhead without teaching Claude anything new. The monetization section explains basic business concepts Claude already knows. | 1 / 3 |
Actionability | The skill provides fully executable code examples throughout: complete manifest.json, working content scripts, storage API usage with async/await wrappers, UI injection code, and payment integration patterns. These are copy-paste ready and cover the key extension development scenarios. | 3 / 3 |
Workflow Clarity | The collaboration workflows (Productivity Extension, AI Browser Assistant) list numbered steps but are vague ('Define extension functionality', 'Market and iterate'). There are no validation checkpoints for the extension building process itself—no mention of testing the extension locally, debugging with chrome://extensions, or validating the manifest before publishing. The 'Validation Checks' section lists common issues but doesn't integrate them into a build workflow. | 2 / 3 |
Progressive Disclosure | All content is in a single monolithic file with no bundle files or external references. The file is very long with inline content covering architecture, content scripts, storage, monetization, validation, and collaboration—much of which could be split into separate reference files. There's no clear navigation structure or signposting to help find specific topics. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
e40fdb8
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.