build-chrome-extension

Scaffold, build, and validate MV3 Chrome extensions with manifest checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yigitkonur/skills-by-yigitkonur-secondary --skill build-chrome-extension
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-chrome-extension
Source: https://github.com/yigitkonur/skills-by-yigitkonur-secondary/tree/main/skills/build-chrome-extension
Command: npx skills add https://github.com/yigitkonur/skills-by-yigitkonur-secondary --skill build-chrome-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps teams scaffold, validate, and package Chrome MV3 extensions, reducing setup time and misconfigurations during development and deployment.

Core Features & Use Cases

  • Scaffold MV3 extension skeletons (service_worker, manifest integration) and framework guidance (default to WXT)
  • Run manifest validation and preflight checks to ensure MV3 compliance before packaging
  • Debug, package, and ship MV3 extensions across Chrome versions with cross-surface guidance

Quick Start

Run the install and build steps to generate production MV3 extension output for testing.

Frequently Asked Questions about build-chrome-extension

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

FAQPage Schema
How do I scaffold a new Chrome MV3 extension with a service worker?

You can scaffold a production-ready MV3 extension skeleton by automating project setup, which configures service_worker backgrounds, manifest integration, and side_panel integration. It defaults to WXT framework guidance to streamline initial development workflows.

What is the best way to migrate an MV2 Chrome extension to manifest version 3?

Migrating an MV2 extension to MV3 involves enforcing the manifest_version 3 standard and validating updated artifacts. The process applies check-mv3-manifest scripts to ensure service_worker backgrounds and content_scripts meet compliance before packaging.

How do I validate a Chrome extension manifest for Web Store submission readiness?

Validating an extension manifest for Web Store submission requires running preflight checks. The preflight-extension script enforces MV3 compliance, verifying service_worker backgrounds and manifest_version 3 configurations before packaging production-ready output.

Can I use WXT to build and package Chrome MV3 extensions?

WXT is the default framework guidance for scaffolding and building Chrome MV3 extensions. It integrates with manifest validation workflows to produce production-ready output suitable for Web Store submission and cross-version Chrome compatibility.

Why does my MV3 extension fail preflight checks before packaging?

MV3 extension preflight checks fail when manifest validation detects non-compliant configurations, such as missing service_worker backgrounds or incorrect manifest_version 3 settings. The check-mv3-manifest script identifies these misconfigurations to resolve before packaging.