Agent skill

Chrome Webstore Release Blueprint

by brianlovin in brianlovin/agent-config

Guide a user end-to-end through setting up Chrome Web Store API release automation in any repository.

No licenceAuto-check: notesBackend & APIs

Install Chrome Webstore Release Blueprint

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brianlovin/agent-config chrome-webstore-release-blueprint --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brianlovin/agent-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/chrome-webstore-release-blueprint .claude/skills/chrome-webstore-release-blueprint && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chrome-webstore-release-blueprint
GitHub stars
377
Used in
1 other repo
Token cost
~2.2k tokens
SKILL.md length
1,015 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
None found

At a glance

Guide a user end-to-end through setting up Chrome Web Store API release automation in any repository.

  • Works in 6 steps: Project Discovery (Before Any Credential… → Detailed Credential Walkthrough (User +… → Local Secret File and CI Secret Setup → …
  • Asked to walk someone through OAuth/CWS credential setup
  • SKILL.md covers What This Skill Is For, Agent Behavior Rules, Step 1: Project Discovery… and Step 2: Detailed Credential…, plus 7 more sections
  • Calls gh; reaches console.cloud.google.com and developers.google.com; needs CWS_CLIENT_SECRET and CWS_REFRESH_TOKEN

What it does

Chrome Webstore Release Blueprint is an agent skill from brianlovin/agent-config. Guide a user end-to-end through setting up Chrome Web Store API release automation in any repository. Use when asked to walk someone through OAuth/CWS credential setup, refresh token creation, local/CI secret setup, version-based publish automation, and submission status checks.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering OAuth and OpenID Connect. The repository describes itself as: My coding agent config.

When your agent uses it

  • Asked to walk someone through OAuth/CWS credential setup
  • Refresh token creation
  • Local/CI secret setup
  • Version-based publish automation

Example prompts

  • “/chrome-webstore-release-blueprint”

Requirements

  • A credential in CWS_CLIENT_SECRET
  • A credential in CWS_REFRESH_TOKEN

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Project Discovery (Before Any Credential Work)
  2. Detailed Credential Walkthrough (User + Agent)
  3. Local Secret File and CI Secret Setup
  4. Release Workflow Blueprint (Version-Triggered)
  5. Submission Status Checker Blueprint
  6. Guided Verification Flow

What it can do on your machine

Read from SKILL.md and the folder at commit 1a9819e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • console.cloud.google.com
    • developers.google.com
    • chromewebstore.googleapis.com
    • developer.chrome.com
    • googleapis.com
    • oauth2.googleapis.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CWS_CLIENT_SECRET
    • CWS_REFRESH_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Chrome Webstore Release Blueprint loads about 2.2k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 1,015 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:34
    - local secret file convention (`.env`, `.env.local`, etc.)

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,015 words (~2,186 tokens).

“Use this skill as a hands-on setup guide. The agent should lead the user step-by-step, ask for confirmations, and only automate the parts that can be done locally/in CI.”

— opening of SKILL.md by brianlovin
name
chrome-webstore-release-blueprint

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/chrome-webstore-release-blueprint of brianlovin/agent-config.

Open the folder on GitHubat commit 1a9819e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in brianlovin/agent-config, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Chrome Webstore Release Blueprint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Chrome Webstore Release Blueprint compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chrome Webstore Release Blueprint this skillbrianlovin/agent-config3771 repos~2.2kAutomated safety check: NotesNone
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
OmniRoute Provider Managementdiegosouzapw/OmniRoute75k—~2.4kAutomated safety check: PassMIT
Antipattern Preventiondoorkeeper-gem/doorkeeper5.5k—~1.1kAutomated safety check: PassMIT
Cognitoitsmostafa/aws-agent-skills1.2k1 repos~2.3kAutomated safety check: PassMIT
Notion Worker Third-Party Auth Guidemakenotion/workers-template4391 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed
  • OmniRoute Provider Management

    diegosouzapw/OmniRoute

    Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.

    75k GitHub stars~2.4k tokensUpdated today
    Backend & APIsAuto-check passed
  • Antipattern Prevention

    doorkeeper-gem/doorkeeper

    Avoid common Ruby and Rails antipatterns that degrade maintainability and performance.

    5.5k GitHub stars~1.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Cognito

    itsmostafa/aws-agent-skills

    AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Backend & APIsAuto-check passed
  • Notion Worker Third-Party Auth Guide

    makenotion/workers-template

    Official

    Decides whether a Notion Worker should use a brokered credential, a plaintext environment secret, or OAuth to authenticate against a non-Notion service.

    439 GitHub starsUsed in 1 repo~3.5k tokens
    Backend & APIsAuto-check: notes
  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    173 GitHub starsUsed in 2 repos~925 tokens
    Backend & APIsAuto-check passed

More from brianlovin/agent-config

All 12 skills in this repo
  • Electron Wrapper

    brianlovin/agent-config

    Wrap a Bun web app into an Electron desktop app with native window management, auto-updates, code signing, and CI/CD distribution.

    377 GitHub stars~2.3k tokensUpdated 6 mo ago
    Auto-check passed
  • Favicon

    brianlovin/agent-config

    Generate a complete set of favicons from a source image and update HTML.

    377 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check: notes
  • Playwriter

    brianlovin/agent-config

    Control the user's currently open Chrome tab through the Playwriter CLI (no new browser launch).

    377 GitHub starsUsed in 1 repo~594 tokens
    Auto-check passed
  • Rams

    brianlovin/agent-config

    Run accessibility and visual design review on components. An agent skill from brianlovin/agent-config.

    377 GitHub starsUsed in 1 repo~801 tokens
    Auto-check passed
  • Reclaude

    brianlovin/agent-config

    Refactor CLAUDE.md files to follow progressive disclosure principles.

    377 GitHub starsUsed in 1 repo~981 tokens
    Auto-check passed
  • Bun

    brianlovin/agent-config

    Use Bun instead of Node.js, npm, pnpm, or vite. An agent skill from brianlovin/agent-config.

    377 GitHub starsUsed in 1 repo~484 tokens
    Auto-check: notes

Categories

Questions about Chrome Webstore Release Blueprint

What does Chrome Webstore Release Blueprint do?

Guide a user end-to-end through setting up Chrome Web Store API release automation in any repository. Chrome Webstore Release Blueprint is an agent skill from brianlovin/agent-config. Guide a user end-to-end through setting up Chrome Web Store API release automation in any repository.

When should I use Chrome Webstore Release Blueprint?

Chrome Webstore Release Blueprint fits situations like: asked to walk someone through OAuth/CWS credential setup; refresh token creation; local/CI secret setup; version-based publish automation.

How do I install Chrome Webstore Release Blueprint in Claude Code?

Run `npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a claude-code`. Or copy the skill folder (skills/chrome-webstore-release-blueprint in brianlovin/agent-config) into .claude/skills/chrome-webstore-release-blueprint in your project. Claude Code loads it when a task matches its description.

How do I install Chrome Webstore Release Blueprint in Codex?

Run `npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a codex`. Or copy the skill folder (skills/chrome-webstore-release-blueprint in brianlovin/agent-config) into .agents/skills/chrome-webstore-release-blueprint in your project. Codex loads it when a task matches its description.

Can I use Chrome Webstore Release Blueprint in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brianlovin/agent-config --skill chrome-webstore-release-blueprint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chrome-webstore-release-blueprint, .gemini/skills/chrome-webstore-release-blueprint, .github/skills/chrome-webstore-release-blueprint and .opencode/skills/chrome-webstore-release-blueprint in your project.

What does Chrome Webstore Release Blueprint need to run?

Going by SKILL.md and its folder, Chrome Webstore Release Blueprint needs the command-line tools its instructions call (gh) and credentials named CWS_CLIENT_SECRET and CWS_REFRESH_TOKEN. Our summary lists: A credential in CWS_CLIENT_SECRET; A credential in CWS_REFRESH_TOKEN.

Does Chrome Webstore Release Blueprint access the network?

SKILL.md names 6 domains. In commands or code: console.cloud.google.com, developers.google.com, chromewebstore.googleapis.com, developer.chrome.com, googleapis.com and oauth2.googleapis.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Chrome Webstore Release Blueprint safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Chrome Webstore Release Blueprint use?

No licence was found for Chrome Webstore Release Blueprint or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Chrome Webstore Release Blueprint use?

About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chrome Webstore Release Blueprint?

Skills that share tags, products or a category with Chrome Webstore Release Blueprint: Fortify Development (coollabsio/coolify, 63k stars), OmniRoute Provider Management (diegosouzapw/OmniRoute, 75k stars), Antipattern Prevention (doorkeeper-gem/doorkeeper, 5.5k stars) and Cognito (itsmostafa/aws-agent-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chrome Webstore Release Blueprint?

brianlovin (a GitHub user) maintains it in brianlovin/agent-config, which has 377 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on March 25, 2026.

Source: brianlovin/agent-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.