browser-extension-builder

You extend the browser to give users superpowers. You understand the unique constraints of extension development - permissions, security, store policies. You build extensions that people install and actually use daily. You know the difference between a toy and a tool.

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/browser-extension-builder/SKILL.md

Quality

Discovery

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 description relies heavily on marketing-style language ('superpowers', 'toy vs tool') rather than concrete technical capabilities. It fails to specify what actions the skill performs, lacks natural trigger terms users would use, and provides no guidance on when Claude should select it. The second-person voice ('You extend', 'You understand') also violates the third-person requirement.

Suggestions

Replace vague language with specific actions: 'Create Chrome/Firefox extensions, configure manifest.json, implement content scripts, handle background processes, manage permissions'

Add explicit trigger guidance: 'Use when the user mentions browser extensions, Chrome extensions, Firefox addons, manifest files, or content scripts'

Rewrite in third person voice: 'Builds browser extensions for Chrome and Firefox' instead of 'You extend the browser'

Dimension	Reasoning	Score
Specificity	Uses vague, abstract language like 'superpowers' and 'toy vs tool' without listing any concrete actions. No specific capabilities like 'inject scripts', 'modify DOM', 'handle background processes' are mentioned.	1 / 3
Completeness	Fails to answer 'what does this do' with concrete actions and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Missing natural keywords users would say like 'Chrome extension', 'Firefox addon', 'browser plugin', 'manifest.json', or 'content script'. The term 'browser' alone is too generic.	1 / 3
Distinctiveness Conflict Risk	Mentions 'extension development', 'permissions', and 'store policies' which provides some domain specificity, but 'browser' is vague and could overlap with general web development skills.	2 / 3
	Total	5 / 12 Passed

Implementation

64%

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 a clear development workflow with validation checkpoints, and several capabilities mentioned (monetization, publishing, cross-browser support) have no corresponding guidance. The anti-patterns section is valuable but the overall structure could better guide Claude through the extension development process.

Suggestions

Add a step-by-step workflow section covering: create manifest → load unpacked → test → debug → package → publish, with explicit validation checkpoints

Either remove capabilities not covered (monetization, publishing, cross-browser) or add concrete guidance for them in separate referenced files

Add a debugging/testing section with chrome://extensions loading instructions and common error resolution patterns

Remove the redundant role description and 'When to Use' section to improve conciseness

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy - the role description is repeated from the description, and some sections like 'When to Use' add little value. The capability list could be trimmed as Claude knows what browser extensions involve.	2 / 3
Actionability	Provides fully executable code examples throughout - complete manifest.json template, working content scripts, storage API patterns with async/await wrappers. All code is copy-paste ready and includes practical patterns like injecting UI and message passing.	3 / 3
Workflow Clarity	The project structure and communication pattern diagram are helpful, but there's no clear step-by-step workflow for building an extension from start to finish. Missing validation steps for testing, loading unpacked extensions, or debugging. No explicit sequence for the development process.	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 documentation for advanced topics like cross-browser support, monetization, or store publishing that are mentioned in capabilities.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: 9c177eb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.