CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/browser-extension-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with strong executable code examples, but it suffers from duplication, motivational padding, monolithic structure, and workflows that lack integrated validation checkpoints. Splitting reference material into bundle files and tightening prose would improve it.

Suggestions

Remove the duplicated description paragraph and merge the redundant Expertise/Capabilities lists into a single concise list to improve conciseness.

Move the manifest template, monetization, and validation-checks material into references/ files linked from a short overview to improve progressive disclosure.

Turn the build workflow into an explicit sequenced checklist with validation checkpoints (e.g., run validation checks after manifest creation and before store packaging) to raise workflow clarity.

DimensionReasoningScore

Conciseness

The body repeats the frontmatter description verbatim, duplicates near-identical Expertise and Capabilities lists, and includes motivational fluff ("give users superpowers", "the difference between a toy and a tool"), so it is mostly efficient but could be tightened.

2 / 3

Actionability

Provides copy-paste-ready, executable examples — a complete manifest v3 template, content script listeners, chrome.storage usage, and payment/feature-gating code — meeting the fully-executable anchor.

3 / 3

Workflow Clarity

The Collaboration workflows are high-level numbered lists without validation checkpoints, and while a Validation Checks section exists with severities and fix actions, it is not integrated as a validate→fix→retry loop in the build sequence.

2 / 3

Progressive Disclosure

No bundle files exist and the skill is a single ~385-line monolithic document with reference-style content (manifest templates, monetization tables, validation checks) inline that could be split into separate files, so it is organized but not appropriately decomposed.

2 / 3

Total

9

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-targeted with strong natural trigger terms and a clear niche, but it omits an explicit "Use when..." clause that would tell Claude when to invoke it. Adding trigger guidance would raise completeness from 2 to 3.

Suggestions

Append an explicit "Use when..." clause naming user cues (e.g., "Use when the user wants to build, debug, or publish a Chrome/F Firefox browser extension, addon, or manifest v3 project").

Drop the mild fluff phrase "that solve real problems" to tighten the opening without losing specificity.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing" — rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly answers "what" but lacks an explicit "Use when..." trigger clause, so per the guidelines completeness is capped at 2 (when is only implied by the topic list).

2 / 3

Trigger Term Quality

Covers natural terms users would say — "Chrome", "Firefox", "cross-browser extensions", "manifest v3", "content scripts", "Chrome Web Store" — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

The browser-extension niche with distinct triggers (manifest v3, Chrome Web Store publishing, content scripts) is unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.