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.

Quality

82%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

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 includes some unnecessary introductory fluff, lacks explicit development/testing workflows, and doesn't deliver on promised topics like monetization and Chrome Web Store publishing despite listing them in capabilities.

Suggestions

Remove the roleplay framing paragraph and capabilities list - let the patterns speak for themselves

Add a workflow section with explicit steps: create manifest → test locally → debug → package → publish, with validation checkpoints

Either add content for Chrome Web Store publishing and monetization (mentioned in capabilities) or remove those claims

Consider splitting detailed API references into separate files and keeping SKILL.md as a quick-start overview

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 clearly, 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. The 'Related Skills' section hints at connections but doesn't provide navigation to detailed references for topics like Chrome Web Store publishing or cross-browser support mentioned in capabilities.	2 / 3
	Total	9 / 12 Passed

Description

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

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: duclm1x1/Dive-Ai
Commit: 20ba150

Reviewed: 4 months 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.