Chrome Plugin - Generate and Submit.

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.