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. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3.

54

Quality

61%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/browser-extension-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

This SKILL.md is essentially an empty shell — a table of contents linking to 15 sub-skill files with no substantive content of its own. It lacks any executable code, concrete examples, workflow guidance, or quick-start material. Without the referenced sub-skill files available, the skill provides almost no actionable value on its own.

Suggestions

Add a concise quick-start section with a minimal working manifest.json and project structure so Claude can immediately begin building an extension without needing to read sub-files.

Include at least one complete, executable code example (e.g., a minimal MV3 extension with background worker + content script) directly in the SKILL.md body.

Add a workflow section that sequences the sub-skills into a clear build process (e.g., 1. Set up manifest → 2. Add content scripts → 3. Test locally → 4. Publish) with validation checkpoints.

Remove the redundant 'Capabilities' bullet list since it duplicates the sub-skill links, and replace the vague 'Role' description with concrete constraints or decision criteria.

DimensionReasoningScore

Conciseness

The capabilities list is somewhat redundant with the sub-skill links below it. The 'Role' description has some unnecessary flavor text ('superpowers', 'difference between a toy and a tool'), but overall it's not excessively verbose.

2 / 3

Actionability

The SKILL.md contains zero executable code, no concrete commands, no examples, and no specific guidance. It is entirely a table of contents pointing to sub-skill files, with no actionable content in the body itself.

1 / 3

Workflow Clarity

There is no workflow, sequence, or process described. The numbered list is just a flat index of sub-skills with no indication of order, dependencies, or validation steps for building an extension.

1 / 3

Progressive Disclosure

The skill does reference 15 sub-skill files with clear one-level-deep links, which is good structure. However, no bundle files were provided to verify these references exist, the 'Patterns' section header is empty, and there's no quick-start content in the SKILL.md itself — it's purely a table of contents with no overview or getting-started guidance.

2 / 3

Total

6

/

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 covers specific capabilities, includes explicit trigger terms, and clearly delineates both what the skill does and when to use it. The only minor weakness is the use of 'Expert in' which is slightly promotional/first-person-adjacent, though it's not technically first or second person. The trigger terms are well-chosen and cover natural user language variations.

DimensionReasoningScore

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 areas rather than vague language.

3 / 3

Completeness

Clearly answers both 'what' (building browser extensions covering architecture, manifest v3, content scripts, popup UIs, monetization, publishing) and 'when' with an explicit 'Use when:' clause listing trigger terms.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'browser extension', 'chrome extension', 'firefox addon', 'extension', 'manifest v3'. These cover the most common variations a user would naturally use when asking about this topic.

3 / 3

Distinctiveness Conflict Risk

Browser extensions are a clear niche with distinct triggers like 'chrome extension', 'firefox addon', 'manifest v3'. These are unlikely to conflict with general web development or other coding skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.