chrome-extension

Guide MV3 Chrome extension development from scaffolding to Web Store publishing.

9|4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/marduk191/qwen3_mcp --skill chrome-extension-marduk191
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-extension
Source: https://github.com/marduk191/qwen3_mcp/tree/main/skills/chrome-extension
Command: npx skills add https://github.com/marduk191/qwen3_mcp --skill chrome-extension-marduk191

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building and debugging Chrome extensions (MV3) can be complex, error-prone, and hard to publish; developers need a structured, end-to-end guide from project bootstrap to Web Store submission.

Core Features & Use Cases

  • Comprehensive MV3 Chrome extension development guide including project structure, APIs (content scripts, service workers), messaging, storage, side panels, and publishing steps.
  • Migration assistance from MV2, debugging workflows, and best practices for packaging and submission to the Chrome Web Store.
  • Practical scenarios: creating a new extension, implementing a content script, adding a service worker, configuring a side panel, and preparing store assets.

Quick Start

Create a new MV3 extension project skeleton and run the setup to scaffold, test, and publish.

Frequently Asked Questions about chrome-extension

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

FAQPage Schema
How do I migrate a Chrome extension from MV2 to Manifest V3?

To build a Manifest V3 Chrome extension, you configure the manifest file, implement content scripts and service workers, and establish messaging and storage APIs. This structured approach scaffolds the project, tests workflows, and prepares the extension for Web Store publishing.

How do service workers work in Manifest V3 Chrome extensions?

Service workers in Manifest V3 Chrome extensions operate as ephemeral background scripts replacing persistent background pages, managing events and messaging. They handle background tasks, API calls, and state coordination without maintaining long-term memory, requiring specific lifecycle handling.

What is the best way to debug content scripts and service workers in MV3?

The best way to debug content scripts and service workers in MV3 involves utilizing Chrome DevTools for inspecting extension contexts and verifying messaging pipelines. A structured workflow identifies errors in manifest configuration, storage, and API interactions.

How do I package and publish a Chrome extension to the Web Store?

To package and publish a Chrome extension to the Web Store, prepare store assets, configure packaging best practices, and submit the MV3 project. This deployment phase finalizes the manifest, tests workflows, and uploads the built extension package.

Why does my MV3 service worker keep unloading during extension messaging?

MV3 service workers unload during extension messaging due to their ephemeral lifecycle design, terminating after inactivity. Managing this requires implementing state persistence via storage APIs and ensuring message handlers wake the service worker efficiently.

Can I use side panels with content scripts in a Manifest V3 extension?

Yes, you can use side panels with content scripts in a Manifest V3 extension by configuring the side panel API alongside your content scripts. This builds persistent side UIs interacting with service workers and manipulating web page content.