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:Dokhacgiakhoa/antigravity-ide --skill browser-extension-builderOverall
score
62%
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 uses third person voice, lists specific technical concepts, and includes an explicit 'Use when:' clause with natural trigger terms. The description is concise yet comprehensive, covering the full scope from architecture to publishing.
| 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 common variations and platform-specific terms users naturally use. | 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
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 table of contents rather than a skill document. It lacks any actionable content, executable examples, or workflow guidance in the main file. While it appropriately delegates to sub-skills, it provides no quick-start value or context for when/how to use the linked resources.
Suggestions
Add a 'Quick Start' section with a minimal working extension example (manifest.json + basic content script) that users can copy-paste and load immediately
Include a workflow section explaining the typical extension development process: 1) Define manifest 2) Create content/background scripts 3) Test locally 4) Package and publish
Remove or condense the 'Capabilities' list since it duplicates the sub-skill links below it
Add brief 1-line descriptions to each sub-skill link explaining when to use each module
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary fluff like 'You extend the browser to give users superpowers' and the capabilities list which largely duplicates the sub-skill links. The role description adds little actionable value. | 2 / 3 |
Actionability | The skill body contains zero executable code, no concrete commands, and no specific examples. It's entirely a table of contents pointing elsewhere with no actionable guidance in the main file itself. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. The content is just a list of links with no indication of how to approach building an extension, what order to follow, or any validation checkpoints. | 1 / 3 |
Progressive Disclosure | The skill does use sub-skills for detailed content (good), but the main file provides almost no overview content - it's essentially just a link dump. A quick start section or minimal working example should exist before pointing to 15 sub-files. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
91%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 | |
- 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.