Chrome Extension Automation Toolkit
chayestudos68-gif/chrome-extension-emissary
Automatiza publicação de extensões Chrome do código à Web Store
Ver no GitHubAutomação completa do ciclo de vida de extensões Chrome, desde geração de metadados até publicação na Web Store. Integra scaffolding, geração de copy otimizada para SEO, captura automatizada de screenshots, configuração OAuth e submissão orquestrada em um pipeline único.
Instalação
npx convez-ai chayestudos68-gif/chrome-extension-emissary1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Publicar extensões Chrome sem etapas manuais repetitivas
- Gerar descrições SEO-otimizadas multilíngues automaticamente
- Capturar screenshots responsivos em todas as dimensões exigidas
- Integrar publicação em pipelines CI/CD
Veredito

Ferramenta sólida para automatizar o workflow tedioso de publicação em Web Store, com suporte a multilíngues e CI/CD. Requer conhecimento técnico avançado em Chrome APIs e OAuth, mas elimina significativamente o atrito manual.
README
A tradução para o português deste README ainda está na fila.
Chrome Extension Automation Toolkit: Streamline Your Web Store Publishing Pipeline
Automate the entire Chrome extension lifecycle—from scaffolding and listing copy generation to screenshot capture, OAuth setup, and store submission. This companion toolkit transforms the chaotic, multi-step process of publishing a Chrome Web Store extension into a single, orchestrated workflow.
Overview
Publishing a Chrome extension is rarely a one-click affair. It involves six distinct, often tedious skills: scaffolding the project, writing compelling listing copy, capturing pixel-perfect screenshots, configuring OAuth for the Chrome Web Store API, and finally submitting the package. This repository provides the automation layer that bridges these gaps, pairing seamlessly with the cce-factory WXT template to eliminate manual friction.
Think of it as your personal publishing co-pilot—handling the repetitive, error-prone tasks so you can focus on building features that delight users instead of wrestling with store metadata.
🧭 Architecture & Workflow
The following diagram visualizes how the six automation modules interact to produce a complete Chrome extension submission:
graph TD
A[Scaffold Extension] --> B[Generate Listing Copy]
B --> C[Capture Screenshots]
C --> D[Configure Chrome Web Store OAuth]
D --> E[Set Up Submission Payload]
E --> F[Orchestrate & Submit]
B --> G[SEO-Optimized Description]
B --> H[Feature Bullet Points]
C --> I[Responsive Screenshot Sizes]
C --> J[Automated Border Styling]
D --> K[Token Refresh Logic]
D --> L[API Credential Storage]
F --> M[Chrome Web Store API]
F --> N[Publish Confirmation]
🚀 Key Features
- Six-Skill Orchestration – Scaffold, list, screenshot, OAuth, submit, and publish from a single command pipeline.
- AI-Powered Listing Copy – Generate SEO-optimized descriptions using OpenAI or Claude API integration.
- Automated Screenshot Capture – Responsive UI screenshots at all required Chrome Web Store dimensions with styled borders.
- OAuth Lifecycle Management – Automatically refresh tokens and handle credential rotation for the Chrome Web Store API.
- Multilingual Support – Generate listing copy in 10+ languages with automatic locale detection.
- 24/7 Background Automation – Designed to run in CI/CD pipelines with retry logic and error handling.
- Responsive UI Previews – Capture screenshots at 1280x800, 640x400, and mobile viewports without manual resizing.
- Configuration Templates – JSON and YAML file support for customizing every automation parameter.
- MIT Licensed – Free for personal and commercial use.
🖥️ OS Compatibility
This toolkit has been tested and verified across major operating systems. Emoji indicators reflect automation reliability:
| OS | Status | Notes |
|---|---|---|
| macOS Sonoma+ | ✅ Full Support | Native screenshot commands work out-of-the-box |
| Windows 11 | ✅ Full Support | PowerShell and WSL2 verified |
| Ubuntu 22.04+ | ✅ Full Support | Headless mode for CI/CD environments |
| ChromeOS | ⚠️ Partial | Requires Linux container for full automation |
| BSD Variants | 🧪 Experimental | Community contributions welcome |
📋 Example Profile Configuration
Customize the automation pipeline with a named profile. Here's a sample configuration file:
{
"profile": "my-first-extension",
"extension": {
"name": "Smart Tab Organizer",
"version": "1.2.0",
"developer_email": "dev@example.com",
"default_locale": "en"
},
"listing": {
"description_tone": "professional",
"target_audience": "productivity users",
"key_benefits": [
"auto-group tabs by domain",
"session restore after crash",
"lightweight (< 100KB)"
],
"screenshot_count": 5,
"language": ["en", "es", "de", "ja"]
},
"oauth": {
"client_id": "your-client-id-here",
"refresh_token_interval_hours": 48
},
"screenshots": {
"borders": true,
"background_color": "#ffffff",
"delay_seconds": 2
},
"submission": {
"publish_target": "trusted_testers",
"release_notes": "Initial release with tab grouping and crash recovery."
}
}
🖥️ Example Console Invocation
After configuring your profile, run the automation from your terminal:
# Scaffold a new extension using the cce-factory template
chrome-extension-toolkit scaffold --template cce-factory --name "Smart Tab Organizer"
# Generate listing copy with AI integration
chrome-extension-toolkit generate-listing --profile my-first-extension --api-key openai
# Capture responsive screenshots automatically
chrome-extension-toolkit capture-screenshots --profile my-first-extension --viewport all
# Configure Chrome Web Store OAuth and test connection
chrome-extension-toolkit setup-oauth --profile my-first-extension --test-connection
# Orchestrate full submission pipeline
chrome-extension-toolkit submit --profile my-first-extension --dry-run false
The tool provides real-time console output with progress bars, retry status, and error logs. Each command supports a --dry-run flag for validation before execution.
⚙️ How It Works
The automation engine operates in six distinct phases, each corresponding to a core skill:
-
Scaffolding Phase – Clones the
cce-factoryWXT template and applies your extension configuration, including manifest.json updates, icon placeholders, and directory structure. -
Listing Generation Phase – Uses AI APIs (OpenAI GPT-4 or Claude 3.5) to craft SEO-friendly descriptions, feature lists, and bullet points. The engine analyzes competitor extensions and suggests keywords naturally integrated into the copy.
-
Screenshot Capture Phase – Launches a headless browser instance, loads your extension's popup and options page, and captures screenshots at all Chrome Web Store dimensions. Each screenshot is automatically annotated with extension branding and a subtle border.
-
OAuth Configuration Phase – Sets up the Chrome Web Store API credentials, validates token expiration, and generates a refresh token workflow. Stores encrypted credentials in a local vault or CI/CD secrets.
-
Submission Preparation Phase – Packages the extension into a
.zipfile, validates the manifest against Chrome Web Store requirements, and constructs the submission payload with all metadata. -
Orchestration Phase – Submits the package via the Chrome Web Store API, handles rate limiting, and sends notifications (via email, Slack, or Discord webhook) upon success or failure.
🌐 AI API Integration
This toolkit supports two leading AI providers for generating listing copy and translations:
- OpenAI API – Use GPT-4o for nuanced, persuasive copy that converts. Configure with
--api-key openaiand set your organization ID in the environment. - Claude API – Leverage Claude 3.5 Sonnet for long-form, technically accurate descriptions. Ideal for developer tools and B2B extensions.
Both integrations respect your token budget and allow custom prompt templates. The engine automatically selects the most cost-effective model based on the requested language and description length.
🛡️ Disclaimer
This toolkit automates interactions with the Chrome Web Store API, which is subject to Google's terms of service. Users are responsible for:
- Ensuring their extension complies with Chrome Web Store policies
- Maintaining valid OAuth credentials and respecting API rate limits
- Not using automation to submit spam, malicious, or policy-violating extensions
- Reviewing generated listing copy for factual accuracy before publication
The developers of this repository are not affiliated with Google LLC or Anthropic. Use at your own risk. Automated submission may be subject to additional review by the Chrome Web Store team.
📝 License
This project is licensed under the MIT License. You are free to use, modify, and distribute this software for any purpose, personal or commercial. See the LICENSE file for the full text.
🙏 Acknowledgments
- Inspired by the
cce-factoryWXT template and the Chrome extension community - Built with Node.js, Puppeteer, and the Chrome Web Store API
- AI integration powered by OpenAI and Anthropic APIs
Version 1.0.0 — Released January 2026