CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chrome-extension-development

Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices. Use when building browser extensions, creating popup UIs, implementing content scripts, working with Chrome APIs, managing extension permissions, or publishing to Chrome Web Store.

Quality

69%

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 ./chrome-extension-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 pairs a clear 8-step workflow with two solid, executable examples (manifest and service worker), but roughly half of it is generic best-practice filler Claude already knows, with no concrete guidance for content scripts, popup, storage, or testing, and no progressive disclosure into reference files.

Suggestions

Cut the generic filler sections (Code Style, UI/UX, Accessibility, Internationalization, Publishing, Testing, Output Expectations) or replace them with Chrome-specific non-obvious guidance — e.g. MV3 service-worker lifetime limits, chrome.storage session vs local vs sync, host_permissions vs activeTab, web_accessible_resources MV3 gating.

Add a complete content-script + popup + storage example (mirroring the quality of the service-worker example) so all core workflow steps have executable code instead of abstract bullets.

Add explicit validation checkpoints to the workflow (e.g. verify the manifest loads cleanly at chrome://extensions, check for service-worker console errors before wiring messaging) and move detailed topic content (publishing, i18n) into one-level-deep reference files.

DimensionReasoningScore

Conciseness

The two code examples are efficient, but roughly half the body (~10 bullet sections from 'Code Style and Structure' onward) restates generic software knowledge Claude already has — "Implement proper error handling and logging", "Follow Material Design guidelines", "Implement ARIA labels", "Handle user feedback", "Maintain documentation" — none of it Chrome-specific. This matches anchor 2 (noticeably verbose, several padded sections) rather than anchor 3, where padding would be occasional rather than extensive.

2 / 5

Actionability

The manifest JSON and the TypeScript service worker are complete and copy-paste ready, but they concretely cover only 2 of the 8 workflow steps; content scripts, popup UI, storage, i18n, and testing get zero executable guidance, and most sections are abstract direction ("Implement proper caching mechanisms", "Use secure messaging between components", "Implement secure data encryption"). Key details are missing, fitting anchor 3 rather than anchor 4 (which requires only minor gaps).

3 / 5

Workflow Clarity

The 8-step build workflow is clearly sequenced (init → manifest → background → content scripts → popup → storage → test → publish), but validation is only implicit: step 7 says "run unit tests" with no commands or criteria, and there is no manifest-validation checkpoint or error-recovery loop. This matches anchor 3 (sequence present but checkpoints missing or implicit); no destructive or batch operations apply, so the workflow-cap rule is not triggered.

3 / 5

Progressive Disclosure

Sections are clearly headed, but the ~185-line file is monolithic with no bundle files or external references, and content that clearly belongs in separate reference files (i18n, accessibility, publishing, testing) is inlined. The under-50-line simple-skill exception does not apply; anchor 3 (some structure, content that should be separate is inline) is the best fit.

3 / 5

Total

11

/

20

Passed

Description

82%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.

A strong description with an explicit third-person 'what' and a concrete 'Use when...' trigger clause covering natural terms and Chrome-specific vocabulary. Its main weakness is an abstract 'what' portion that relies on 'best practices' filler instead of concrete capability statements.

DimensionReasoningScore

Specificity

Names the domain (Chrome extension development, Manifest V3) and lists several concrete actions in the trigger clause ("creating popup UIs, implementing content scripts, working with Chrome APIs, managing extension permissions, or publishing to Chrome Web Store"), but the 'what' portion leans on generic filler ("covering security, performance, and best practices") rather than a comprehensive list of concrete capabilities, so it fits the anchor-4 pattern (several specific actions, minor gaps) rather than anchor 5.

4 / 5

Completeness

Both parts are explicitly present: a 'what' ("Expert guidelines for Chrome extension development with Manifest V3, covering security, performance, and best practices") and a 'when' ("Use when building browser extensions, creating popup UIs, ..." with concrete trigger phrases). The 'what' is somewhat abstract ('guidelines', 'best practices') compared to the anchor-5 pattern of concrete capability verbs, so anchor 4 is the best fit.

4 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered: "building browser extensions", "popup UIs", "content scripts", "Chrome APIs", "extension permissions", "Chrome Web Store", "Manifest V3", including the synonym pairing of "browser extensions" with "Chrome extension" — a user needing this skill would naturally say these terms.

5 / 5

Distinctiveness Conflict Risk

Triggers are strongly Chrome-specific ("Manifest V3", "Chrome APIs", "Chrome Web Store", "content scripts"), but the generic phrase "building browser extensions" creates minor overlap risk with non-Chrome (e.g. Firefox/Safari) extension development skills, matching anchor 4 (mostly distinct, minor overlap risk) rather than anchor 5.

4 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

Mindrally/skills

Path

chrome-extension-development/SKILL.md

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.