Skills browser-extension-developer
📦

browser-extension-developer

Content revision r1 Safe ⚙️ External commands

Build Browser Extensions With WXT

Cross-browser extension work often breaks across Chrome, Firefox, Edge, and localization files. This skill guides WXT extension development, builds, compatibility checks, and i18n updates.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "browser-extension-developer" from https://skillstore.io/skills/yamadashy-browser-extension-developer.md and its manifest at https://skillstore.io/api/skills/yamadashy-browser-extension-developer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yamadashy-browser-extension-developer.md Signed manifest GET /api/skills/yamadashy-browser-extension-developer/manifest Signed lockfile GET /api/skills/yamadashy-browser-extension-developer/lockfile

Test it

Using "browser-extension-developer". Review a new content script change for cross-browser risk.

Expected outcome:

A concise review covering API compatibility, injected button behavior, Firefox polyfill needs, and recommended validation steps.

Using "browser-extension-developer". Add a new supported language for extension messages.

Expected outcome:

A localization checklist with required message names, existing language references, and validation steps for translated extension text.

Using "browser-extension-developer". Prepare the extension for a release build.

Expected outcome:

A release readiness summary covering development commands, build targets, lint checks, tests, and manual browser verification.

Security Audit

Safe
v8 • 7/8/2026 Open versioned report

The static findings are false positives caused by Markdown backticks and documented npm commands in SKILL.md. I found no executable shell invocation, prompt injection attempt, or malicious intent in the skill text.

1
Files scanned
37
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (8)
SKILL.md:3 SKILL.md:12-18 SKILL.md:18-22 SKILL.md:22-23 SKILL.md:23-24 SKILL.md:24-25 SKILL.md:25 SKILL.md:31-35
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/yamadashy-browser-extension-developer/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yamadashy-browser-extension-developer/security.svg)](https://skillstore.io/skills/yamadashy-browser-extension-developer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yamadashy-browser-extension-developer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yamadashy-browser-extension-developer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yamadashy-browser-extension-developer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

yamadashy. (2026). browser-extension-developer security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yamadashy-browser-extension-developer/audits/8

BibTeX citation

@techreport{yamadashy-yamadashy-browser-extension-developer-2026, author = {yamadashy}, title = {browser-extension-developer security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/yamadashy-browser-extension-developer/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "browser-extension-developer security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "yamadashy" date-released: "2026-07-08" url: "https://skillstore.io/skills/yamadashy-browser-extension-developer/audits/8" identifiers: - type: other value: "skillstore:yamadashy-browser-extension-developer:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
71
Community
83
Spec Compliance

What You Can Build

Add Extension Features

Plan and implement a browser extension change across content scripts and background scripts.

Verify Browser Compatibility

Check whether a change needs Chrome API handling, Firefox polyfills, or Edge-specific validation.

Expand Localization

Add or update locale messages for supported extension languages.

Try These Prompts

Inspect Extension Structure 
Review the browser extension structure and explain where content script, background script, config, and locale changes should go.
Implement a Small Change 
Add this browser extension behavior while keeping Chrome, Firefox, and Edge compatibility in mind: [describe behavior].
Add a Locale 
Add or update extension localization for [language code]. Include the required message keys and check existing language patterns.
Prepare a Cross-Browser Release 
Review the extension changes for WXT build readiness, browser compatibility risks, lint coverage, tests, and localization completeness.

Best Practices

  • Run lint and tests before marking extension work complete.
  • Test changes in each target browser before release.
  • Keep locale message keys aligned across all supported languages.

Avoid

  • Assuming Chrome APIs work unchanged in Firefox.
  • Changing content scripts without validating GitHub page behavior.
  • Adding locale files with missing required message keys.

Frequently Asked Questions

Which browsers does this skill target?
It targets Chrome, Firefox, and Edge browser extension development.
Which framework does it assume?
It assumes the extension uses the WXT framework.
Can it help with content scripts?
Yes. It includes guidance for content script and background script work.
Can it help with localization?
Yes. It describes supported languages and required message keys.
Does it publish extensions to browser stores?
No. It helps with development and validation, not store submission.
Does it run npm commands automatically?
No. It documents commands for the developer to run when appropriate.

Developer Details

Author

yamadashy

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/yamadashy/repomix/tree/main/.claude/skills/browser-extension-developer

Ref

64ca8af0f54a325752f08bd54e52151061ea659a

Maintenance freshness

7/21/2026

Usage

18 downloads · 250 views

File structure

📄 SKILL.md

More from yamadashy

View all

Related Skills

View all