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. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3.
68
61%
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 ./.agent/skills/browser-extension-builder/SKILL.mdQuality
Discovery
100%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 skill description that clearly defines its scope (browser extension development), lists specific capabilities (architecture, manifest v3, content scripts, etc.), and includes an explicit 'Use when' clause with natural trigger terms. The description effectively differentiates itself from general web development skills through browser-extension-specific terminology.
| 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 capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('building browser extensions... Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing') AND when with explicit 'Use when:' clause listing trigger terms. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'browser extension, chrome extension, firefox addon, extension, manifest v3' - covers major variations users would naturally use when seeking help with browser extensions. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on browser extensions with distinct triggers like 'manifest v3', 'firefox addon', 'Chrome Web Store' - unlikely to conflict with general web development or other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill body functions as a pure index/table of contents with no actionable content in the main file. While it attempts progressive disclosure through sub-skill links, it fails to provide any executable guidance, quick-start examples, or workflow clarity. The role description and capabilities list add little value that Claude doesn't already know.
Suggestions
Add a Quick Start section with a minimal working extension example (manifest.json + basic content script) that can be copy-pasted
Include a numbered workflow for building an extension from scratch: 1. Create manifest 2. Add content script 3. Test locally 4. Package for store
Remove the 'Capabilities' list which duplicates the sub-skill links and replace with concrete guidance
Add a brief code example showing the core communication pattern between content script and background worker
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary framing ('You extend the browser to give users superpowers') and a capabilities list that largely duplicates the sub-skill links. The role description adds little actionable value. | 2 / 3 |
Actionability | The skill body contains zero executable code, commands, or concrete guidance. It's entirely a table of contents pointing to sub-skills with no actionable content in the main file itself. | 1 / 3 |
Workflow Clarity | No workflow is presented. The numbered list suggests sequence but provides no actual steps, validation checkpoints, or process guidance. It's just a link index without any procedural content. | 1 / 3 |
Progressive Disclosure | The structure attempts progressive disclosure with sub-skill links, but the main file lacks any quick-start content or overview of how to actually build an extension. It's all references with no substantive overview content to orient the reader. | 2 / 3 |
Total | 6 / 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 | |
332e58b
Table of Contents
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.