{{persona::BRAND}}-platform-chrome-extension

Develop Chrome Extensions with Manifest V3 service workers and content scripts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yejune/godo --skill persona-brand-platform-chrome-extension
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: {{persona::BRAND}}-platform-chrome-extension
Source: https://github.com/yejune/godo/tree/main/core/skills/platform-chrome-extension
Command: npx skills add https://github.com/yejune/godo --skill persona-brand-platform-chrome-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance and tools for developing robust, secure, and performant Chrome Extensions using Manifest V3, streamlining the entire development lifecycle from setup to publishing.

Core Features & Use Cases

  • Manifest V3 Development: Covers service workers, content scripts, message passing, and Chrome APIs.
  • API Reference & Patterns: Detailed guides on core Chrome APIs like chrome.runtime, chrome.tabs, chrome.storage, and chrome.scripting.
  • Security & Best Practices: Ensures extensions are secure, privacy-preserving, and adhere to Chrome's latest standards.
  • Publishing Workflow: Guides through packaging, submission, and management on the Chrome Web Store.
  • Use Case: A developer needs to build a new Chrome extension to enhance a web application by adding custom UI elements and background data synchronization. This Skill provides all the necessary documentation, API references, and best practices to accomplish this efficiently and securely.

Quick Start

Use the {{persona::BRAND}}-platform-chrome-extension skill to generate a basic Manifest V3 Chrome extension structure.

Frequently Asked Questions about {{persona::BRAND}}-platform-chrome-extension

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

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

To build a Chrome extension using Manifest V3, you need to configure a service worker for background tasks, implement content scripts for web page manipulation, and define your extension's structure and permissions in the manifest file.

What is the difference between service workers and content scripts in browser extensions?

Service workers handle background events and extension lifecycle in Manifest V3, while content scripts directly interact with and modify the DOM of specific web pages the user visits.

How do I implement message passing between a content script and a service worker?

Message passing between a content script and a service worker is implemented using Chrome Extension APIs like `chrome.runtime.sendMessage` and `chrome.runtime.onMessage` to enable asynchronous communication across different extension contexts.

What do I need to publish a Chrome extension to the Web Store?

Publishing a Chrome extension to the Web Store requires packaging your Manifest V3 project directory into a zip file, configuring privacy practices, and submitting it through the Chrome Developer Dashboard for review.

Do I need to know JavaScript to develop Chrome extensions with Manifest V3?

Yes, you need a solid understanding of JavaScript, HTML, and CSS to develop Chrome extensions with Manifest V3, as these technologies are required to structure the UI, implement logic, and utilize Chrome Extension APIs efficiently.

Why is my Manifest V3 service worker becoming inactive?

Manifest V3 service workers are event-driven and automatically become inactive when idle to conserve system resources, requiring you to persist state using `chrome.storage` instead of global variables for reliable background data synchronization.