Chrome Plugin - Generate and Submit.

    1

    Builds Chrome Manifest V3 extensions and prepares complete Web Store submission kits including ZIPs, assets, and sites.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Chrome Plugin - Generate and Submit.

    Example session with this skill installed

    I have a small timer extension in the /src folder. Help me package it for the Chrome Web Store with 2 screenshots and a privacy policy site.

    • Read your context and instructions
    • Compiled the chrome plugin
    • Generated the document

    I have processed the timer extension. I separated the source from the release artifacts, generated the required branding, and prepared the documentation site.

    Chrome Extension Submission Kit

    The runtime ZIP has been frozen and verified. All marketing assets meet the Chrome Web Store dimensions and format requirements.

    Release Details

    • Product Name: FocusTimer
    • Version: 1.0.0 (Manifest V3)
    • ZIP Hash (SHA-256): e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
    • Build Directory: ./release/extension.zip

    Store Assets

    AssetPathStatus
    Store Description./store-assets/description.txt450/16,000 chars
    Runtime Icon./extension/icons/icon128.png128x128 PNG
    Small Promo Tile./store-assets/small-promo.png440x280 PNG
    Screenshot 01./store-assets/screen-01.png1280x800
    Screenshot 02./store-assets/screen-02.png1280x800

    Public Documentation

    • Homepage: https://focustimer.example.com/
    • Privacy Policy: https://focustimer.example.com/privacy
    • Support: https://focustimer.example.com/support

    Readiness Report
    The check_assets.py script confirmed all files are present. The manifest uses narrow permissions (storage, alarms). No remote code detected.

    Next steps

    1. Download the extension.zip from the /release folder.
    2. Log into the Chrome Developer Dashboard and upload the ZIP.
    3. Copy the text from description.txt into the Store Listing tab.

    extension.zip

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Stop shipping extensions with missing assets or rejected privacy policies. This skill takes a browser extension from a raw repository to a complete, store-ready submission kit including the optimized runtime ZIP and all required marketing collateral.

    What it does

    • Runtime Packaging generates a clean Manifest V3 ZIP excluding source maps, tests, and secrets.
    • Asset Generation creates required 128x128 icons and 440x280 promotional tiles.
    • Listing Copy drafts store descriptions, summaries, and permission justifications within character limits.
    • Documentation Sites builds and deploys required product, support, and privacy policy pages.
    • Readiness Audits runs pre-flight checks on file inventories, SHA-256 hashes, and image dimensions.

    How it works

    1. Initialize the project by separating extension code from store assets and site source.
    2. Package the extension using package_extension.py to freeze a clean production build.
    3. Generate the listing text and capture screenshots of the actual product interface.
    4. Publish the mandatory privacy and support pages to a public HTTPS endpoint.
    5. Verify the entire kit with check_assets.py before handoff to the Developer Dashboard.

    Frameworks & tools

    Built for Chrome Manifest V3. Supports Python-based packaging scripts and integrates with GPT Sites or custom hosting for documentation.

    Why this beats prompting it yourself

    Standard prompts often forget mandatory store assets like promotional tiles or fail to separate source code from the final ZIP. This skill enforces a strict directory structure and uses local scripts to verify file hashes and image constraints, ensuring you don't get rejected for technicalities.

    Use cases

    • Preparing a new extension for its first Chrome Web Store submission.
    • Updating an existing Manifest V2 extension to V3 with a fresh asset kit.
    • Generating compliant privacy policies based on actual extension data flows.
    • Auditing a repository to ensure no secrets or source maps leak into the production ZIP.

    Known limitations

    Does not authorize store uploads, pay developer fees, or bypass manual dashboard steps. JavaScript dynamic dependencies are not parsed during packaging.

    Does not handle store upload/payment. No dynamic JS dependency parsing. Requires manual verification of live URL content. Scripts require Python 3.10+.

    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 any payment.

    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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    The skill produces a production-ready Manifest V3 ZIP file, a full set of promotional icons and tiles, compliant listing descriptions, and hosted privacy/support pages required for store approval.

    Yes, the skill is designed to audit your extension's data flows and generate a compliant privacy policy and support site, ensuring you meet the mandatory Google developer requirements.

    No, while this skill prepares every technical and marketing component for you, Google requires developers to manually upload the kit and pay the one-time registration fee through their official dashboard.

    The skill uses local verification scripts to perform 'pre-flight' checks on image dimensions, file hashes, and manifest structure to catch common rejection triggers before you submit.

    This skill is purpose-built for the Manifest V3 standard; while it can help migrate logic from older V2 extensions, the final output will always be formatted for the current V3 requirements.

    New in APIs & Backend