agentsclimarketplace

Build chrome extension

Skill VRymarovich/product-launch-os/plugins/product-launch-os/skills/build-chrome-extension

Codex plugin with reusable agent skills for product discovery, launch, SEO, sales, and growth

Install
npx -y skills add VRymarovich/product-launch-os --skill build-chrome-extension

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implement, review, or plan Chrome extension product work with Manifest V3, permissions, service workers, content scripts, offscreen documents, messaging, storage, security, and release constraints. Use for Chrome extension features, architecture changes, bug fixes, permission changes, browser compatibility, or extension build verification.

SKILL.md

1.7 KB, 265 tokens by cl100k_base, as published. Nobody here has run it

Build Chrome Extension

Make extension changes without breaking browser lifecycle, permission trust, or store reviewability.

Workflow

  1. Read repository AGENTS.md files, manifest files, package scripts, architecture docs, and the relevant product brief.
  2. Map the change to extension surfaces: popup, content script, service worker, offscreen document, extension page, backend, or website.
  3. Trace messaging, storage ownership, permissions, and lifecycle boundaries before editing.
  4. Keep permissions minimal and explain every new permission or host match.
  5. Preserve Manifest V3 constraints: service workers are ephemeral; content scripts run in page contexts; offscreen documents should have narrow responsibilities.
  6. Implement the smallest coherent change and update architecture documentation when message flows or ownership change.
  7. Verify with the repository's real build, typecheck, lint, and targeted manual extension flow.
  8. Report store-review impact, privacy impact, migration needs, and remaining manual checks.

Read references/extension-review.md before permission, offscreen, messaging, or release-sensitive changes.

Guardrails

  • Never move secrets into extension code.
  • Avoid remote executable code.
  • Do not add broad host permissions for convenience.
  • Do not assume a long-lived service worker or reliable global memory.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.