CtrlK
BlogDocsLog inGet started
Tessl Logo

browser-extension-developer

Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.

60

Quality

70%

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 ./browser/.claude/skills/browser-extension-developer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

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

The body is lean, well-organized, and mostly actionable with concrete commands and an i18n recipe, but it lacks an explicit build-to-test workflow with validation checkpoints, and the structure section describes the tree rather than guiding execution.

Suggestions

Replace the flat 'Run lint and tests before completion' note with a sequenced workflow (e.g., 1. `npm run lint` 2. `npm run test` 3. `npm run build-all` 4. verify `.output/` artifacts) so completion has explicit checkpoints.

Add a brief validation step after `npm run build-all` (e.g., confirm `.output/chrome-mv3` and `.output/firefox-mv2` exist and load in the target browser) to catch build failures before completion.

Add one concrete example of a `messages.json` entry for a new locale so the i18n recipe is fully copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding; it assumes Claude's competence and every section (Structure, Commands, i18n, Notes) earns its place without explaining what a content script or i18n is.

5 / 5

Actionability

Provides concrete executable commands (`npm run dev`, `npm run build-all`) and a concrete recipe (create `public/_locales/[code]/messages.json` with named keys), but the structure section is a descriptive tree rather than executable steps, leaving a minor gap.

4 / 5

Workflow Clarity

Commands are listed but there is no sequenced workflow with validation checkpoints for the build/test process; the only validation guidance is the flat note 'Run lint and tests before completion', which is implicit rather than a checkpoint, capping it at 3.

3 / 5

Progressive Disclosure

A short, well-organized overview with clear section headers and no nested references; for a sub-50-line skill with no need for external bundle files, this clean structure merits a 5.

5 / 5

Total

17

/

20

Passed

Description

63%Weight 40%Scale 1-5

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 well-structured with an explicit 'Use this skill when' trigger, concrete domain scoping to the `browser/` directory, and good natural keyword coverage. It is concise and avoids fluff, but the listed actions are somewhat generic and the 'when' trigger could be more specific about maintenance scenarios.

DimensionReasoningScore

Specificity

Names the domain (browser extension code in `browser/`) and several concrete actions ('Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates'), but each action is only listed generically without specifics, sitting between anchors 3 and 4 but closer to 3.

3 / 5

Completeness

Clearly answers 'what' (developing/maintaining browser extension code) and 'when' via an explicit 'Use this skill when...' clause with concrete trigger contexts; the 'when' could be slightly more specific about maintenance scenarios, so it sits at 4 rather than 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('browser extension', 'content scripts', 'background scripts', 'i18n', 'Chrome/Firefox/Edge') with good coverage; missing a few common synonyms like 'add-on' or file extensions, placing it slightly above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The `browser/` directory scoping plus the specific extension concepts (WXT, MV3, content/background scripts) make it a clear niche with minimal overlap risk, though it could still overlap slightly with a generic frontend skill.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
yamadashy/repomix
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.