chrome-extension

Create and modify Chrome extensions with Manifest V3 scaffolding and messaging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers rapidly create and modify Chrome extensions using Manifest V3, reducing boilerplate and setup time.

Core Features & Use Cases

  • MV3 scaffolding: generate a compliant manifest.json and project structure.
  • Messaging and components: setup content_scripts, background service worker, and popup communication.
  • Use Case: when you need a robust, permission-safe extension ready for testing and packaging.

Quick Start

Use the chrome-extension skill to scaffold a MV3 extension, load it in chrome://extensions for testing, and verify messaging between content script and background.

Frequently Asked Questions about chrome-extension

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

FAQPage Schema
How do I scaffold a Chrome extension using Manifest V3?

To scaffold a Manifest V3 Chrome extension, generate a compliant manifest.json and project structure with the required background service worker, content scripts, and popup components, ensuring MV3 compliance and secure permission handling.

How does messaging work between content scripts and the background service worker in MV3?

Messaging between content scripts and the background service worker in MV3 involves setting up communication channels that allow the extension components to exchange data and trigger actions across the browser environment securely.

What is the best way to set up secure permissions for Chrome extension development?

Secure permissions for Chrome extension development are enforced by declaring required permissions in the manifest.json, ensuring the background service worker and content scripts only request access necessary for their specific extension scenarios.

Do I need a background service worker for every Manifest V3 extension?

Manifest V3 extensions require a background service worker to handle browser events and background logic, replacing the persistent background pages used in previous versions to ensure compliant extension architecture.

Can I use this to package and debug my Chrome extension?

You can debug and package your Chrome extension by loading the generated project structure in chrome://extensions for testing, verifying messaging between components, and following the enforced MV3 compliance workflows.