skills.rest
brianlovin
brianlovinCOMMUNITY
Explore all skills by this author →
Website𝕏@brian_lovinGitHub

chrome-webstore-release-blueprint

Set up Chrome Web Store API release automation with credential and CI configuration.

357|29|Updated Jan 19, 2026
Search Tags:#automation#ci/cd#api#oauth#chrome web store#extension release
One-click install
npx skills add https://github.com/brianlovin/agent-config --skill chrome-webstore-release-blueprint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrome-webstore-release-blueprint
Source: https://github.com/brianlovin/agent-config/tree/main/skills/chrome-webstore-release-blueprint
Command: npx skills add https://github.com/brianlovin/agent-config --skill chrome-webstore-release-blueprint

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex and often manual process of setting up and managing releases for Chrome Web Store extensions, streamlining development workflows.

Core Features & Use Cases

  • End-to-End Automation: Guides users through API setup, credential management, and CI/CD integration for Chrome Web Store releases.
  • Credential Management: Securely handles OAuth and API keys for publishing.
  • Version Control: Automates publishing based on version changes in the manifest.
  • Status Checks: Provides clear visibility into the submission and publishing status.
  • Use Case: A developer can use this skill to set up a GitHub Actions workflow that automatically builds, uploads, and submits their Chrome extension to the Web Store whenever a new version is pushed to the main branch.

Quick Start

Use the chrome-webstore-release-blueprint skill to set up automated Chrome Web Store releases for your extension.

Frequently Asked Questions about chrome-webstore-release-blueprint

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

FAQPage Schema
How do I automate Chrome Web Store extension releases in CI/CD?▼

Automate Chrome Web Store extension releases by configuring OAuth credentials, setting local or CI secrets, and using scripts to trigger version-based publishing and submission status checks. This allows automatic uploads through API integration.

What do I need to set up Chrome Web Store API release automation?▼

To set up Chrome Web Store API release automation, you need to generate OAuth credentials via the Google Cloud dashboard, configure these secrets locally or in your CI environment, and establish repository-side workflow scripts.

How does version-based publishing work for Chrome extensions?▼

Version-based publishing for Chrome extensions works by detecting version changes in your manifest, which then triggers the automated workflow to build, upload, and submit the updated extension package to the Chrome Web Store API.

Can I use GitHub Actions to publish my Chrome extension to the Web Store?▼

Yes, you can use GitHub Actions to publish your Chrome extension by setting up a workflow that monitors your main branch, automatically building and submitting the extension to the Chrome Web Store using configured OAuth secrets.

How do I check my Chrome Web Store submission status after an automated release?▼

Check your Chrome Web Store submission status by running the provided status check scripts from your repository, which query the Chrome Web Store API to provide clear visibility into the publishing state after an automated release.

Related Skills

Explore More Software Engineering Skills→
Aliisa-ytAliisa-yt

google-cloud-api-auth

Standardize Google Cloud API authentication with environment variables and initialization checks.

Community
Advanced
ricablericable

expo-deployment

Deploy Expo applications for iOS, Android, and web releases.

Community
Intermediate
jwmossmozjwmossmoz
3

worker-image-build

Trigger and monitor Firefox CI Windows image builds via GitHub Actions workflows.

Community
Intermediate
KhoiwallKhoiwall

playwriter

Automate real Chrome browser sessions with Playwright code via MCP extension.

Community
Advanced