skill CX Codex

chrome-webstore-release-blueprint — Claude Code skill: auto-publish

Q: How do I install chrome-webstore-release-blueprint in Claude?

Run `npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a claude-code`. The skill lands at `~/.claude/skills/chrome-webstore-release-blueprint/SKILL.md`.

Q: What do I need before starting?

Five values: `CWS_CLIENT_ID`, `CWS_CLIENT_SECRET`, `CWS_REFRESH_TOKEN`, `CWS_PUBLISHER_ID` and `CWS_EXTENSION_ID`. Without them the skill stops at the checklist.

Walks you through OAuth setup and version-triggered publishing of a Chrome extension to the Web Store.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a claude-code

Open on GitHub

What chrome-webstore-release-blueprint does

The skill covers the whole chain: enabling the Chrome Web Store API in Google Cloud, the OAuth consent screen, creating a client, and getting a refresh token through the OAuth Playground. The agent hands you one step at a time and waits for confirmation, since the dashboard work is yours, not its.

Once you have five values — CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN, CWS_PUBLISHER_ID, CWS_EXTENSION_ID — it helps write a local secret template and push those into CI. With gh installed it offers automated upload via gh secret set; otherwise you get a manual checklist. Values are masked in logs and kept out of git.

Then comes the CI workflow: read the version from the manifest, exchange the refresh token for an access token, call fetchStatus, compare the local version against the published one. Publishing only fires when the version changed. PENDING_REVIEW, PUBLISHED, PUBLISHED_TO_TESTERS and STAGED all count as a successful submission. A separate status script supports --json and exits non-zero on auth or API errors. The skill does not touch the Google console for you — skip those steps and nothing runs.

What it helps with

set up an OAuth client and refresh token for the Chrome Web Store API
build and upload an extension zip to the store from CI
publish a new version only when the manifest version changes
check what state the latest submission is in
upload secrets to GitHub Actions with gh

Example prompts for the agent

Help me set up automated publishing for my Chrome extension
Check the status of my latest store submission
Write a workflow that publishes only when the version changes

How to install chrome-webstore-release-blueprint

1Skills CLI (Vercel)

npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a claude-code

2Manually: put the files in place

~/.claude/skills/chrome-webstore-release-blueprint/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/chrome-webstore-release-blueprint/

1Skills CLI (Vercel)

npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a codex

2Manually: put the files in place

.agents/skills/chrome-webstore-release-blueprint/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a cursor

2Manually: put the files in place

.cursor/skills/chrome-webstore-release-blueprint/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install brianlovin/agent-config chrome-webstore-release-blueprint

2Manually: put the files in place

.github/skills/chrome-webstore-release-blueprint/SKILL.md

1Skills CLI (Vercel)

npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a gemini-cli

2Platform CLI

gemini skills install https://github.com/brianlovin/agent-config --path skills/chrome-webstore-release-blueprint

Manually: put the files in place

.devin/skills/chrome-webstore-release-blueprint/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about chrome-webstore-release-blueprint

How do I install chrome-webstore-release-blueprint in Claude?

Run npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a claude-code. The skill lands at ~/.claude/skills/chrome-webstore-release-blueprint/SKILL.md.

What does chrome-webstore-release-blueprint do?

It guides you through Chrome Web Store API access and helps build the scripts and CI flow that publish an extension by version.

What do I need before starting?

Five values: CWS_CLIENT_ID, CWS_CLIENT_SECRET, CWS_REFRESH_TOKEN, CWS_PUBLISHER_ID and CWS_EXTENSION_ID. Without them the skill stops at the checklist.

chrome-extensions GoogleChrome Guides building and publishing Chrome Extensions using Manifest V3 standards. It sets concrete rules for service workers, side panels, and store reviews. CX Codex +1 10,900installs clerk-chrome-extension-patterns clerk Guides integration of @clerk/chrome-extension into Chrome extensions. Helps configure popup sign-in, service worker session tokens, and OAuth delegation via syncHost. CX Codex +1 14,400installs chrome-extension samber Guides agents through Chrome extension work with Manifest V3. Use it for manifests, content scripts, background logic, browser APIs, and Chrome Web Store releases. CX Codex +1 4,500installs chrome-extension-development Mindrally Walks your agent through Manifest V3 extension work: manifest, service worker, content scripts, popup UI, and Chrome Web Store publishing. CX Codex +1 2,800installs chrome-extension-ui pproenca A rule set for Chrome extension interfaces: when to use a popup versus a side panel, how to keep navigation keyboard-accessible, how to handle loading and errors. CX Codex +1 719installs javascript-chrome-apis-cursorrules-prompt-file PatrickJS A Cursor rule that points the AI agent at Chrome extension work: manifest, architecture, Chrome API usage. ★ 41,011repo stars

From the same set12

simplify Rewrites code you just wrote so it reads better: less nesting, fewer duplicates, clearer names. Behaviour stays exactly as it was. CX Codex +1 20,100installs deslop A skill that diffs your branch against main and removes the comments, defensive checks and any-casts an AI left behind. CX Codex +1 5,500installs rams Reviews UI components for WCAG 2.1 compliance and visual styling bugs. Handy when auditing front-end code before shipping. CX Codex +1 3,000installs sentry Guides an agent through Sentry error capture and performance tracing in Next.js code. Use it while adding Sentry instrumentation to an application. CX Codex +1 2,800installs tdd Guides agents through a disciplined red-green-refactor loop. It builds features one vertical slice at a time and tests public behavior over implementation details. CX Codex +1 2,800installs react-doctor The skill scans a React codebase against 47+ rules and returns a 0-100 score with file paths and line numbers. Handy before a review or when the app drags. CX Codex +1 2,800installs reclaude Splits a bloated CLAUDE.md into a short root file plus a .claude/rules/ folder. Useful once your agent instructions grow past the point where you can keep them in your head. CX Codex +1 2,800installs bun Configures the assistant to use the Bun runtime instead of Node.js and npm. Replaces heavy npm packages with built-in APIs. CX Codex +1 2,800installs