← Back to Skills Marketplace
zack-dev-cm

Chrome Extension Studio

by Zakhar Pashkin · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
100
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install chrome-extension-studio
Description
Design, prototype, build, QA, and ship Chrome extensions across separate plugin, template, and product repos with explicit publish lanes.
README (SKILL.md)

Chrome Extension Studio

Use this skill when the task is to design, prototype, build, package, QA, or ship a Chrome extension and the workflow needs to stay clean across multiple repositories.

Core model

  • Plugin repo: workflow instructions, validation, and orchestration only
  • Template repo: reusable MV3 starter and release contract
  • Product repo: one extension per repo

Do not collapse those roles into one repo.

Publish lanes

  • prototype-local
  • beta-private
  • cws-public
  • source-release

Every product repo must declare exactly one lane in extension.release.json. Every product repo should keep structured design metadata in extension.release.json as the source of truth for the brief. Every product repo should also keep docs/release-plan.md generated from that profile. Every product repo should keep docs/extension-brief.md product-specific, not as a generic template. Every product repo should keep docs/store-listing.md generated from structured listing metadata in the profile.

Required files in each product repo

  • extension.release.json
  • docs/extension-brief.md
  • docs/store-listing.md
  • docs/qa-checklist.md
  • docs/release-plan.md

Workflow

  1. Confirm the target product repo and its current publish lane.
  2. If the repo does not exist yet, create it from the separate template repo:
python3 ../../scripts/create_product_repo.py "My Extension" --publish-type prototype-local --git-init
  1. Write or update the product brief before changing code.
  2. Keep permissions, host matches, and store copy intentionally narrow.
  3. Build the extension package inside the product repo, not inside the plugin repo.
  4. Regenerate docs/store-listing.md and docs/release-plan.md after release-profile changes.
  5. Run the local release cycle before recommending any ship step.
  6. Validate the release contract before recommending any ship step.

Validation

Run the validator from the plugin repo against the product repo profile:

python3 ../../scripts/validate_release_profile.py /path/to/product-repo/extension.release.json

Generate or refresh the release plan:

python3 ../../scripts/generate_release_plan.py /path/to/product-repo/extension.release.json

Generate or refresh the store-listing draft:

python3 ../../scripts/generate_store_listing.py /path/to/product-repo/extension.release.json

Generate or refresh the design brief:

python3 ../../scripts/generate_design_brief.py /path/to/product-repo/extension.release.json

Run the local release-preparation cycle:

python3 ../../scripts/execute_release_cycle.py /path/to/product-repo/extension.release.json

Guardrails

  • Do not publish a local prototype through the public lane.
  • Do not store Chrome Web Store metadata only in chat; keep it in repo docs.
  • Do not reuse one product repo for multiple unrelated extensions.
  • Do not change publish type silently; update extension.release.json first.
Usage Guidance
This skill appears safe and purpose-aligned for managing Chrome extension repositories. Before installing, make sure the referenced local ../../scripts helpers exist in a trusted repo, and review file changes before committing, packaging, or publishing anything publicly.
Capability Analysis
Type: OpenClaw Skill Name: chrome-extension-studio Version: 1.0.0 The chrome-extension-studio skill bundle provides a structured workflow for designing, building, and shipping Chrome extensions using a multi-repository approach. It includes instructions for an AI agent to manage product repositories, generate documentation, and validate release profiles using a set of Python scripts (e.g., `create_product_repo.py`, `validate_release_profile.py`). The skill incorporates helpful guardrails, such as preventing local prototypes from being published to public lanes and ensuring metadata is stored in the repository rather than just in the chat history. No indicators of malicious intent, data exfiltration, or harmful prompt injection were identified.
Capability Assessment
ℹ Purpose & Capability
The stated purpose matches the instructions: design, build, validate, and prepare Chrome extension repos. It can create or update repo files and release documents, so users should invoke it only for intended extension projects.
✓ Instruction Scope
The workflow asks the agent to confirm the target repo and publish lane, keep permissions narrow, validate before ship steps, and avoid silent publish-type changes.
ℹ Install Mechanism
There is no install spec and no included code, but SKILL.md references local Python helper scripts under ../../scripts. Those helpers were not available for review and should be trusted before use.
✓ Credentials
The artifacts do not request credentials, environment variables, network access, or broad system permissions. The described work is scoped to extension product repositories.
✓ Persistence & Privilege
No background persistence, account privilege, or credential storage is described. Persistent changes are expected repo files such as extension.release.json and docs.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install chrome-extension-studio
  3. After installation, invoke the skill by name or use /chrome-extension-studio
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial public release for lane-specific Chrome extension design, validation, QA, and packaging workflows.
Metadata
Slug chrome-extension-studio
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Chrome Extension Studio?

Design, prototype, build, QA, and ship Chrome extensions across separate plugin, template, and product repos with explicit publish lanes. It is an AI Agent Skill for Claude Code / OpenClaw, with 100 downloads so far.

How do I install Chrome Extension Studio?

Run "/install chrome-extension-studio" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Chrome Extension Studio free?

Yes, Chrome Extension Studio is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Chrome Extension Studio support?

Chrome Extension Studio is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Chrome Extension Studio?

It is built and maintained by Zakhar Pashkin (@zack-dev-cm); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments