Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Webstore Release Blueprint

Checked
brianlovin·vlatest·devops

Automates Chrome Web Store app releases by orchestrating steps like publishing and updating, streamlining your workflow for faster deployments.

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 brianlovin/agent-config --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

brianlovin

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 brianlovin/claude-config at 1a9819ebf3.

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

Commit
1a9819ebf3
Manifest
skills/chrome-webstore-release-blueprint/SKILL.md
Scanned
1 file, 260 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

The chrome-webstore-release-blueprint skill streamlines the deployment of Chrome extensions by generating a complete release workflow. It automates the creation of necessary configuration files and scripts required to publish an extension to the Web Store.

When to use it

  • You need to automate the repetitive steps of preparing an extension for submission.
  • You want to ensure consistent metadata and versioning across multiple extension releases.
  • You are integrating extension publishing into a continuous integration pipeline.
  • You require a standardized blueprint to reduce human error during the release process.

Key capabilities

  • Generates structured release workflows for Chrome extensions.
  • Creates configuration files tailored for Web Store submission.
  • Automates scripting tasks associated with deployment and versioning.

Example prompts

  • "Generate a release blueprint for my new Chrome extension including all required manifest updates."
  • "Create an automated script to prepare and submit version 2.0 of my extension to the Chrome Web Store."
  • "Produce a step-by-step workflow configuration for deploying this extension with specific metadata tags."

Tips & gotchas

This blueprint is specifically designed for Chrome extensions; do not attempt to use it for other browser add-ons or web apps without modification. Ensure your extension's manifest file is up to date before running the generated release scripts to avoid submission rejections.