browser-extension-builder

Builds Chrome and Firefox extensions using Manifest V3, content scripts, and service workers.

1|Updated Dec 29, 2025

Search Tags:#service worker #chrome #Manifest V3 #firefox #browser extension #web store #content scripts

Ready to run

npx skills add https://github.com/ratnesh-maurya/tracker.ratnesh-maurya.com --skill browser-extension-builder-ratnesh-maurya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-extension-builder
Source: https://github.com/ratnesh-maurya/tracker.ratnesh-maurya.com/tree/main/.claude/skills/browser-extension-builder
Command: npx skills add https://github.com/ratnesh-maurya/tracker.ratnesh-maurya.com --skill browser-extension-builder-ratnesh-maurya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a browser extension requires navigating Manifest V3 constraints, permission models, message passing between contexts, and store publishing rules, which are easy to get wrong without a structured reference. ## Core Features & Use Cases - Extension Architecture: Provides a standard project structure covering popup UIs, content scripts, background service workers, options pages, and icons. - Manifest V3 Templates: Supplies ready-to-adapt manifest.json configurations with correct permissions, content script matching, and service worker registration. - Storage and Messaging Patterns: Includes Chrome Storage API usage (local vs sync limits), async/await wrappers, and popup-to-content-script communication patterns. - Use Case: You want to build a Chrome extension that highlights data on web pages and saves user preferences. Use this Skill to scaffold the manifest, write the content script, wire up message passing, and persist settings with chrome.storage. ## Quick Start Help me build a Manifest V3 Chrome extension with a popup UI, a content script that modifies page elements, and settings saved to chrome.storage.

Frequently Asked Questions about browser-extension-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build a Chrome extension with Manifest V3?▼

Create a manifest.json with manifest_version 3, declare permissions, and register your popup, content scripts, and background service worker. Organize the project into popup, content, background, options, and icons directories.

How do content scripts communicate with the popup in a Chrome extension?▼

Use chrome.runtime.onMessage in the content script to listen for messages sent from the popup or background worker. Return true from the listener to keep the channel open for asynchronous sendResponse calls.

What is the difference between chrome.storage.local and chrome.storage.sync?▼

chrome.storage.local stores up to 5MB on the local device, while chrome.storage.sync is limited to 100KB total with 8KB per item but syncs across the user's signed-in devices. Use sync only for small settings.

Why does my Manifest V3 background script stop running?▼

MV3 service workers are terminated when idle, so long-running background processing fails. Keep background logic minimal, use chrome.alarms for periodic tasks, and offload heavy work to content scripts.

Can a Chrome extension work on Firefox and other browsers?▼

Yes, cross-browser support is achievable since Firefox supports Manifest V3 and the WebExtensions API. Keep permissions minimal and avoid Chrome-only APIs, or add polyfills where behavior differs.