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. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill browser-extension-builderOverall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates both capabilities and usage triggers. It lists specific technical concepts (manifest v3, content scripts, popup UIs) while including natural user language in the trigger terms. The explicit 'Use when:' clause with relevant keywords makes it easy for Claude to select this skill appropriately.
| 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 | Excellent coverage of natural terms users would say: 'browser extension, chrome extension, firefox addon, extension, manifest v3' - these match how users naturally describe extension development needs. | 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 coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable code examples for browser extension development with good coverage of MV3 patterns, content scripts, and storage. However, it lacks workflow guidance for the development lifecycle (testing, debugging, publishing) and includes some unnecessary introductory framing. The anti-patterns section is valuable but the skill would benefit from explicit step-by-step workflows for common tasks.
Suggestions
Add a workflow section with explicit steps for testing extensions locally (chrome://extensions, load unpacked, debugging) with validation checkpoints
Remove or condense the 'Role' paragraph and 'Capabilities' list - they add little value over the pattern demonstrations
Add a publishing workflow with Chrome Web Store submission steps and common rejection reasons to avoid
Consider splitting detailed API reference (storage limits, permission options) into a separate REFERENCE.md file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary framing ('You extend the browser to give users superpowers') and the capabilities list duplicates what's shown in the patterns. However, the code examples themselves are reasonably efficient without excessive explanation. | 2 / 3 |
Actionability | Provides fully executable code examples including complete manifest.json, content scripts, storage patterns with async/await wrappers, and UI injection code. All examples are copy-paste ready with real Chrome APIs. | 3 / 3 |
Workflow Clarity | Shows project structure and communication patterns but lacks explicit workflow steps for building/testing/publishing an extension. No validation checkpoints for common failure points like manifest errors or permission issues during development. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections with clear headers, but everything is inline in one file. References to 'Related Skills' exist but no links to separate detailed docs for topics like Chrome Web Store publishing or cross-browser support mentioned in capabilities. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.