Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Chrome Extension Builder: MV3, Tested & Store-Ready

    1

    Build and publish Manifest V3 browser extensions with TypeScript, Vite, and automated review readiness.

    Free

    Security scanned
    Chrome Extension Builder: MV3, Tested & Store-Ready

    Chrome Extension Builder: MV3, Tested & Store-Ready

    Example session with this skill installed

    I need a Chrome extension that highlights all 'price' elements on an ecommerce site and saves them to local storage when I click a button in the popup. Use TypeScript and Vite.

    • Read your context and instructions
    • Compiled the chrome extension builder

    I have scaffolded a Manifest V3 extension using TypeScript and Vite. It includes a content script targeted at ecommerce selectors, a popup UI for triggering the scan, and local storage integration.

    Extension Implementation

    // manifest.json
    {
      "manifest_version": 3,
      "name": "Price Tracker Lite",
      "version": "1.0.0",
      "description": "Highlights and saves price data from target ecommerce pages.",
      "permissions": ["storage", "activeTab", "scripting"],
      "action": {
        "default_popup": "src/popup/index.html"
      },
      "content_scripts": [
        {
          "matches": ["https://*.example-store.com/*"],
          "js": ["src/content.ts"]
        }
      ],
      "icons": {
        "128": "icons/128.png"
      }
    }
    
    // src/content.ts
    chrome.runtime.onMessage.addListener((request, sender, sendResponse) => {
      if (request.action === "scan_prices") {
        const prices = Array.from(document.querySelectorAll('.price-tag'))
          .map(el => el.textContent?.trim());
        
        // Highlight UI
        document.querySelectorAll('.price-tag').forEach(el => {
          (el as HTMLElement).style.border = '2px solid #ff0000';
        });
    
        chrome.storage.local.set({ lastScanned: prices }, () => {
          sendResponse({ status: "success", count: prices.length });
        });
        return true; 
      }
    });
    

    Next steps

    1. Run npm install followed by npm run build to generate the dist/ folder.
    2. Open chrome://extensions, enable Developer mode, and click Load unpacked to select the dist/ directory.
    3. Update the matches array in manifest.json with the actual URL patterns of your target store.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Building browser extensions shouldn't lead to immediate store rejection. This skill scaffolds and debugs Chrome, Edge, and Firefox extensions using Manifest V3 standards with a focus on security and review readiness.

    What it does

    • Architects Manifest V3 extensions including popups, side panels, service workers, and content scripts.
    • Configures build pipelines using Vite and TypeScript for type-safe browser API interactions.
    • Optimizes permissions by selecting the narrowest scope required to pass Web Store reviews.
    • Handles cross-browser compatibility via polyfills for Firefox and Edge support.
    • Prepares store listings with mandatory privacy justifications and single-purpose statements.

    How it works

    1. Define the spec including match patterns, UI surfaces, and required data storage.
    2. Scaffold the project with a standard TypeScript and Vite directory structure.
    3. Implement core logic using messaging patterns, alarms for timers, and storage sync.
    4. Run E2E testing using Playwright to verify functionality on target websites.
    5. Generate a publishing kit with a zip-ready distribution and store listing copy.

    Frameworks & tools

    TypeScript, Vite, @crxjs/vite-plugin, Playwright for E2E testing, and the chrome-types definition library.

    Why this beats prompting it yourself

    Generic prompts often produce Manifest V2 code or broad permissions that trigger manual review flags. This skill enforces MV3 patterns like service workers over background pages and forbids remote code execution by design.

    Use cases

    • Build a content script that modifies specific DOM elements on a target site.
    • Create a productivity tool using the Side Panel API and local storage.
    • Migrate an existing V2 extension to the modern V3 architecture.
    • Scaffold a cross-browser extension that works on Chrome, Edge, and Firefox.

    Known limitations

    Does not support remote code injection or eval due to MV3 security constraints. Development requires manual loading of unpacked extensions in browser developer mode.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    Requires manual loading of unpacked extensions in Chrome/Firefox. No support for remote code execution or eval.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    • Free with an Agensi account

    Permissions

    Browser
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This skill generates a complete, production-ready codebase including TypeScript source files, Vite configuration, Manifest V3 definitions, and a zip-ready distribution folder for immediate store submission.

    Yes, while it defaults to Chrome's Manifest V3 standards, it includes the necessary polyfills and configuration adjustments to ensure your extension functions correctly on Firefox and Edge.

    It solves common rejection issues by enforcing the 'principle of least privilege,' ensuring your manifest only requests the narrowest permissions required for your specific features.

    The skill is designed to work with any modern LLM-based agent that supports file generation and terminal commands, as it utilizes standard tools like Vite and Playwright.

    Absolutely—the skill includes a dedicated workflow for migrating legacy Manifest V2 background pages into the modern Service Worker architecture required by the latest browser standards.

    New in APIs & Backend

    Free