← 返回 Skills 市场

Chrome Extension Studio

Name: Chrome Extension Studio
Author: zack-dev-cm

作者 Zakhar Pashkin · GitHub ↗ · v1.0.0 · MIT-0

cross-platform ✓ 安全检测通过

100

总下载

当前安装

版本数

在 OpenClaw 中安装

/install chrome-extension-studio

功能描述

Design, prototype, build, QA, and ship Chrome extensions across separate plugin, template, and product repos with explicit publish lanes.

使用说明 (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

Confirm the target product repo and its current publish lane.
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

Write or update the product brief before changing code.
Keep permissions, host matches, and store copy intentionally narrow.
Build the extension package inside the product repo, not inside the plugin repo.
Regenerate docs/store-listing.md and docs/release-plan.md after release-profile changes.
Run the local release cycle before recommending any ship step.
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.

安全使用建议

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.

功能分析

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.

能力评估

ℹ 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.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install chrome-extension-studio
安装完成后，直接呼叫该 Skill 的名称或使用 /chrome-extension-studio 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

v1.0.0

Initial public release for lane-specific Chrome extension design, validation, QA, and packaging workflows.

元数据

Slug chrome-extension-studio

版本 1.0.0

许可证 MIT-0

累计安装 0

当前安装数 0

历史版本数 1

常见问题