extension-analyze
Extension Analyze (Security & Compliance Auditor)
Audit an existing Chrome extension. Do NOT just explain — execute the workflow.
Workflow (Execute This)
Step 1: Locate extension root and detect framework
Ask user for path if not provided. Detect framework:
ls wxt.config.ts plasmo.config.ts vite.config.ts manifest.json 2>/dev/null
- Plasmo: manifest auto-generated; check
package.jsonandplasmo.config.tsinstead - WXT: check
wxt.config.tsmanifest section - Vanilla/CRXJS: check
manifest.jsondirectly
Step 2: Scan manifest.json (or equivalent config)
More from quangpl/browser-extension-skills
extension-ui
Build polished Chrome extension UIs (popup/sidepanel/options). Analyze existing UI, suggest improvements, set up design systems, enforce a11y and UX best practices.
24extension-create
Auto-scaffold Chrome extensions with WXT or Plasmo. Ask user for name/features, scaffold, configure entrypoints. Use when: create extension, scaffold, new extension.
22extension-manifest
Generate and validate manifest.json with optimal permissions for Chrome MV3 extensions. Analyzes code to determine minimum permissions. Use when: manifest, permissions, manifest.json.
21extension-dev
Detect Chrome extension framework/stack, find proper docs, implement features, and debug across service worker, content script, and popup contexts.
20extension-assets
Generate and manage all Chrome extension assets: icons (16–128px), CWS listing images, promotional tiles, and public/ folder setup. Supports ImageMagick, Gemini API, and manual prompt templates.
19extension-review
Scan extension source code for Chrome Web Store rejection risks. Generates report with issues, root causes, and fixes. Use when: review, pre-submit, rejection, CWS compliance, store review.
18