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.
57
48%
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 lack 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 abstractions. | 3 / 3 |
Completeness | The 'what' is well-covered with specific capabilities, but there is no explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the domain description. Per rubric guidelines, missing 'Use when...' 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 common terms a user would naturally use when asking about extension development. | 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
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill covers a broad range of browser extension topics but suffers from poor organization, redundant sections, and lack of clear workflows. The code examples are a strength but are undermined by verbose meta-sections (role descriptions, capability lists, delegation triggers) that consume tokens without adding actionable value. The skill would benefit significantly from trimming boilerplate, adding a clear build-test-publish workflow with validation steps, and splitting detailed content into referenced files.
Suggestions
Remove redundant sections (Role, Expertise, Capabilities lists) and the Collaboration/Delegation/When to Use meta-sections to reclaim token budget for actionable content.
Add a clear end-to-end workflow with validation checkpoints: create project → write manifest → implement features → load unpacked extension → test → fix errors → package → submit to store.
Split detailed content (content scripts, storage patterns, monetization) into separate referenced files and keep SKILL.md as a concise overview with quick-start examples.
Fix the duplicate heading structure (e.g., 'Extension Architecture' and 'Content Scripts' each appear twice at different heading levels) to improve navigation clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity: the 'Role' description, 'Expertise' list, and 'Capabilities' list are redundant with each other and with the skill description. Sections like 'Collaboration', 'Delegation Triggers', 'Related Skills', and 'When to Use' add meta-information that doesn't help Claude execute tasks. The 'Validation Checks' section explains obvious best practices Claude already knows. Overall, many tokens are spent on organizational boilerplate rather than actionable content. | 1 / 3 |
Actionability | The skill provides concrete, mostly executable code examples (manifest.json template, content scripts, storage API usage, payment integration pattern). However, several sections are descriptive rather than instructive (e.g., revenue models table, validation checks as prose). There's no complete end-to-end example of building and loading an extension for testing, and the monetization code references undefined helper functions (getStorage) without full context. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for building an extension from start to finish. The 'Productivity Extension' and 'AI Browser Assistant' workflows are vague numbered lists without validation checkpoints. Critical steps like loading an unpacked extension for testing, debugging, and store submission are absent. No feedback loops or verification steps exist for any multi-step process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files for detailed topics. Everything from architecture to monetization to validation is inlined. The heading structure is confusing with duplicate section headers (e.g., 'Extension Architecture' appears twice, 'Content Scripts' appears twice). No external references are provided for deeper topics like store publishing guidelines or cross-browser compatibility. | 1 / 3 |
Total | 5 / 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
43280f9
- 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.