Build and Publish Chrome Extensions
Create or fix Manifest V3 Chrome extensions without common API bugs, and generate CHROMEWEBSTORE.md with store copy, permission justifications, privacy disclosures, and launch checks.
Install the skill or give me an instruction how to install it - chrome-extensions from https://github.com/GoogleChrome/modern-web-guidance Free Open source Works in Claude, Cursor, Codex & more
What it does
Describe a browser tool, point it at an existing extension, or paste a Chrome Web Store rejection, and get back working Manifest V3 extension code plus a submission-ready CHROMEWEBSTORE.md file. It writes popups, side panels, content scripts, service workers, and matching PNG or SVG icons, while tracking listing copy, permission justifications, privacy answers, and version history at your project root.
To prevent silent failures with Chrome APIs, it enforces 20 mandatory Manifest V3 rules backed by 19 API reference guides. It keeps service-worker state in chrome.storage instead of globals, wires explicit triggers for side panels, replaces activeTab with host permissions in panels, locks exclusive capture streams, puts chrome.permissions.request ahead of awaits, and batches content-script DOM edits with requestAnimationFrame.
For release prep, four store guides turn manifest.json and a codebase scan into plain-English permission justifications, privacy policy templates, and user-focused listing copy stripped of API jargon. Before delivery, it checks a 29-item output list and supplies a ZIP packaging script that excludes dev files like node_modules and CHROMEWEBSTORE.md.
When to use it
- You're building a Chrome extension from scratch
Generate a Manifest V3 codebase with a popup or side panel, external scripts, persistent service-worker storage, and matching PNG icons or clean omissions.
- Your side panel, service worker, or permissions keep failing
Catch silent Manifest V3 bugs like missing side-panel triggers, activeTab calls from panels, global worker state, or lost user-gesture permission prompts.
- You're preparing an extension for Chrome Web Store review
Create CHROMEWEBSTORE.md with jargon-free store copy, specific permission justifications, a matching privacy disclosure table, and a clean ZIP packaging script.
- The Chrome Web Store review team rejected your submission
Diagnose common rejection triggers like unused permissions, broad host access, mismatched privacy disclosures, or vague single-purpose statements and update CHROMEWEBSTORE.md with the fix.
FAQ
What files and outputs do I get back?
You get Manifest V3 extension code, such as manifest.json, background service workers, popups, side panels, content scripts, and optional PNG or SVG icons, plus CHROMEWEBSTORE.md in your project root holding your store copy, permission justifications, privacy table, and version history.
How is this different from asking an agent without the skill?
Built around 20 Manifest V3 rules, 23 reference guides, and a 29-item output checklist, chrome-extensions stops common mistakes agents make on their own, such as generating deprecated Manifest V2 code, storing worker state in global variables, leaving side panels unopenable, or calling chrome.windows.query().
Does it need API keys, paid accounts, or special tools?
No. The skill is a set of Markdown rules and reference guides with no external API keys or services required. Creating 16x16, 48x48, and 128x128 PNG icons uses Python Pillow or Node.js canvas if installed, or the skill omits icons cleanly, and publishing later requires a Chrome Web Store developer account.
Can it help with Chrome Web Store rejections and privacy policies?
Yes. It includes four store-publishing guides covering common rejection causes, a privacy policy template for both zero-collection and data-collecting extensions, and rules that strip API names from user-facing descriptions while updating CHROMEWEBSTORE.md with each fix.