Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Webstore Release Blueprint

Checked
iannuttall·vlatest·devops·MIT

Automates Chrome Web Store app releases by streamlining deployment steps and configurations for efficient DevOps workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add iannuttall/skills --skill chrome-webstore-release-blueprint -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

iannuttall

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned iannuttall/skills at 0a35cb006a.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0a35cb006a
Manifest
skills/chrome-webstore-release-blueprint/SKILL.md
Scanned
2 files, 265 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates the release process for Chrome extensions to the Chrome Web Store. It handles tasks such as version bumping, building extension packages, and publishing updates directly to the store. This streamlines development workflows and reduces manual effort associated with releasing new versions of Chrome extensions.

When to use it

  • You need to regularly update your Chrome extension with bug fixes or new features.
  • Your team wants to automate the release process for multiple Chrome extensions.
  • You are looking for a way to reduce errors and inconsistencies in your Chrome extension releases.
  • You want to ensure consistent versioning across development, staging, and production environments.

Key capabilities

  • Automated version bumping
  • Extension package building
  • Chrome Web Store publishing

Example prompts

  • "Release version 1.2.3 of my Chrome extension."
  • "Build the latest version of my extension for deployment."
  • "Publish the current build to the Chrome Web Store staging environment."

Tips & gotchas

Requires appropriate credentials and permissions configured within the Google Developer Console to publish extensions. Ensure your extension's manifest file is correctly formatted before attempting a release.