skills.rest
GoogleChrome
GoogleChromeOFFICIAL
Explore all skills by this author →
GitHub

chrome-extensions

Generate Manifest V3 Chrome extensions with compliant APIs and store metadata.

926|71|Updated Jan 27, 2026
Search Tags:#service worker#extension development#manifest v3#chrome web store#content scripts#browser extensions#chrome extensions
One-click install
npx skills add https://github.com/GoogleChrome/modern-web-guidance-src --skill chrome-extensions-googlechrome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrome-extensions
Source: https://github.com/GoogleChrome/modern-web-guidance-src/tree/main/skills-src/chrome-extensions
Command: npx skills add https://github.com/GoogleChrome/modern-web-guidance-src --skill chrome-extensions-googlechrome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coding agents frequently generate broken Chrome extension code that relies on deprecated Manifest V2 APIs, leading to non-functional extensions, Chrome Web Store rejections, and poor user experience. This skill eliminates that risk by embedding up-to-date Manifest V3 best practices, API usage guardrails, and end-to-end publishing guidance directly into the agent's context.

Core Features & Use Cases

  • Manifest V3 Compliance Enforcement: Ensures all generated extension code uses current MV3 APIs (service workers, chrome.action, separate host_permissions) instead of deprecated V2 patterns like background.scripts or chrome.browserAction.
  • Chrome Web Store Publishing Support: Provides templates, checklists, and guidance for store listings, permission justifications, privacy policies, and pre-submission reviews to avoid common rejection reasons.
  • API Best Practice Guidance: Covers critical pitfalls for side panels, content scripts, service worker state management, media capture, user scripts, and other Chrome extension APIs to prevent broken functionality and edge case failures.
  • Use Case: When a user requests to build a Chrome extension that saves and organizes browser tabs, this skill ensures the generated code follows MV3 rules, handles service worker state correctly, and includes all required metadata for successful store submission.

Quick Start

Use the chrome-extensions skill to build a Manifest V3 Chrome extension that lets users save open tabs to categorized lists, then generate a complete CHROMEWEBSTORE.md file with all required metadata and permission justifications for publishing to the Chrome Web Store.

Frequently Asked Questions about chrome-extensions

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

FAQPage Schema
How do I migrate my Chrome extension to Manifest V3?▼

Migrating to Manifest V3 requires replacing deprecated background scripts with service workers, updating chrome.browserAction to chrome.action, and separating host permissions. This skill enforces current MV3 best practices to generate compliant browser extension code and prevent API usage errors.

Why does my Chrome extension get rejected from the Chrome Web Store?▼

Chrome Web Store rejections often stem from missing privacy policies, insufficient permission justifications, or deprecated Manifest V2 code. This skill provides publishing templates and pre-submission checklists to generate complete store listing metadata and ensure compliant extension code.

How do I manage state in a Manifest V3 service worker?▼

Managing state in a Manifest V3 service worker requires handling the ephemeral lifecycle of service workers correctly to prevent broken functionality. This skill provides API best practice guidance to handle service worker state management and avoid edge case failures in browser extensions.

What is the best way to build a production-ready Chrome extension?▼

Building a production-ready Chrome extension involves following Manifest V3 rules, correctly implementing content scripts, and preparing store submission metadata. This skill embeds up-to-date API usage guardrails and publishing guidance to generate functional, compliant extension code.

Does this skill help with Chrome extension side panel and user scripts API?▼

Yes, this skill covers critical API best practices and pitfalls for side panels, user scripts, content scripts, and media capture. It ensures correct API implementation to prevent broken functionality and edge case failures during Chrome extension development.

Can I use this skill to debug existing Manifest V2 browser extensions?▼

Yes, you can use this skill to debug existing browser extensions by identifying deprecated Manifest V2 patterns and updating them to current MV3 APIs. It applies to modifying functionality and fixing broken Chrome extension code to meet Chrome Web Store compliance.

Related Skills

Explore More Software Engineering Skills→
yukieijiyukieiji

chrome-extensions

Develop and publish Chrome extensions following Manifest V3 guidelines.

Community
Advanced
jinwoonghongjinwoonghong

moai-platform-chrome-extension

Develop Chrome extensions using Manifest V3 service workers and content scripts.

Community
Advanced
RepairYourTechRepairYourTech
6

browser-extension-patterns

Develop Manifest V3 browser extensions across Chrome, Firefox, and Safari.

Community
Advanced
thimsluggathimslugga

browser-extension-builder

Build cross-browser Chrome and Firefox extensions with MV3 manifests, content scripts, and popup UI.

Community
Intermediate