Chrome Extension Studio
PassAudited by ClawScan on May 15, 2026.
Overview
This is a coherent Chrome-extension workflow skill, with the main caveat that it expects local helper scripts that were not included in the reviewed artifacts.
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.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the local helper scripts are untrusted or different from what the skill expects, they could create or modify extension repositories in unexpected ways.
The skill tells the agent to run helper scripts via relative paths, but those scripts are not part of the provided artifact set, so their provenance and behavior cannot be assessed here.
python3 ../../scripts/create_product_repo.py "My Extension" --publish-type prototype-local --git-init
Before using the skill, verify the referenced ../../scripts helpers come from a trusted plugin repository and review what they do.
The skill may execute local build/release-preparation scripts and change files in the selected product repository.
The workflow includes running local Python commands that may build or modify release artifacts. This is purpose-aligned for an extension build skill, but still worth noticing.
Run the local release-preparation cycle: ```bash python3 ../../scripts/execute_release_cycle.py /path/to/product-repo/extension.release.json ```
Run it only in the intended repo, review generated changes before committing or publishing, and avoid using it with unknown helper scripts.