skills.rest
TrebuchetDynamics
TrebuchetDynamicsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

chrome-extensions

Diagnose Manifest V3 Chrome extension build and runtime configuration issues.

5|Updated May 21, 2026
Search Tags:#permissions#service worker#side panel#manifest v3#chrome web store#chrome extensions#csp sandboxing
One-click install
npx skills add https://github.com/TrebuchetDynamics/pi-package-goal --skill chrome-extensions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrome-extensions
Source: https://github.com/TrebuchetDynamics/pi-package-goal/tree/main/skills/chrome-extensions
Command: npx skills add https://github.com/TrebuchetDynamics/pi-package-goal --skill chrome-extensions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Chrome extension projects often fail late due to Manifest V3 constraints, CSP restrictions, missing permissions, incorrect UI triggers, or publishing requirements—this Skill guides you to build reliable extensions and avoid common production-breaking mistakes.

Core Features & Use Cases

  • Manifest V3 correctness: Enforces rules for icons, side panel triggers, required manifest keys (like action), and safe API usage.
  • Robust extension architecture: Covers async/await patterns, service worker lifetime constraints, ephemeral state handling, and correct tab/window API usage.
  • Safe code execution: Provides compliant CSP sandboxing patterns for user-generated or dynamic UI.
  • Publishing readiness: Establishes a repeatable Chrome Web Store workflow via CHROMEWEBSTORE.md, including permissions justifications and pre-publish checks.
  • Implementation references: Points you to focused reference docs for common subsystems (content scripts, CSP, messaging, media capture, devtools, storage, etc.).

Quick Start

Ask for a complete Manifest V3 build and debug plan for your extension so it can be packaged and prepared for Chrome Web Store submission.

Frequently Asked Questions about chrome-extensions

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

FAQPage Schema
How do I fix Manifest V3 service worker lifetime and state management issues in Chrome extensions?▼

Manifest V3 service worker lifetime constraints require careful async/await patterns and ephemeral state handling to prevent runtime interruptions. This Skill diagnoses build-breaking configuration and provides correct architecture rules for service workers and tab/window API usage.

What's the best way to configure Content Security Policy sandboxing for dynamic UI in Chrome extensions?▼

CSP sandboxing for dynamic UI in Chrome extensions requires compliant code execution patterns to avoid security violations. This Skill provides safe CSP sandboxing patterns for user-generated content and dynamic UI components within Manifest V3 constraints.

Why does my Chrome extension side panel or popup fail to trigger correctly?▼

Chrome extension side panel and popup failures often stem from missing required manifest keys like action or incorrect UI trigger configuration. This Skill enforces correct manifest key usage and API behavior for icons, side panels, and popup UI interactions.

Do I need specific permissions justifications to publish a Manifest V3 extension to the Chrome Web Store?▼

Publishing a Manifest V3 extension to the Chrome Web Store requires explicit permissions justifications and passing pre-publish checks. This Skill establishes a repeatable CHROMEWEBSTORE.md publishing checklist satisfying store requirements for packaging and submission.

Can I use async/await patterns with Chrome extension content scripts and messaging APIs?▼

Using async/await patterns with Chrome extension content scripts and messaging APIs requires correct state management to handle service worker ephemeral lifetime constraints. This Skill guides robust extension architecture covering async patterns and messaging subsystems.

What are common Manifest V3 limitations that break Chrome extension builds before publishing?▼

Common Manifest V3 limitations breaking Chrome extension builds include CSP restrictions, missing permissions, incorrect UI triggers, and invalid manifest key configurations. This Skill diagnoses these production-breaking mistakes and enforces correct API usage before Chrome Web Store submission.

Related Skills

Explore More Software Engineering Skills→
pingqLINpingqLIN

start-chrome-extension-project

Scaffold a Chrome extension project from a bundled template with Manifest V3 and build scripts.

Community
Intermediate
auto-medica-labsauto-medica-labs
6

chrome-extensions

Build, debug, and publish Chrome Extensions using Manifest V3 best practices.

Official
Advanced
richardadonnellrichardadonnell
45

wxt-browser-extensions

Review WXT browser extension code against performance optimization rules.

Community
Advanced
Claude-Code-Community-IrelandClaude-Code-Community-Ireland
10

Browser Extension Builder

Build Chrome and Firefox browser extensions with Manifest V3.

Official
Intermediate