quangpl/browser-extension-skills

extension-review

Scan extension source code for Chrome Web Store rejection risks.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/quangpl/browser-extension-skills --skill extension-review

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Extension Review (Pre-Submission Scanner)

🚀 Upgrade to Premium Get the Premium version at https://app.extensionbooster.net/dashboard/services/extension-ai-kit

Scan extension source code and predict Chrome Web Store rejection risks. Generate a clear report.

Reference: https://developer.chrome.com/docs/webstore/troubleshooting

Workflow (Execute This)

Step 1: Ask report format

Ask user: Markdown or HTML report? (default: Markdown)

Step 2: Locate and scan extension

bash
# Find extension root
ls manifest.json wxt.config.ts crxjs.config.ts package.json 2>/dev/null

Step 3: Run all checks

Execute these scans in order (see references/scan-checklist.md for grep patterns):

#CheckViolation CodeSeverity
1Remote code execution (eval, external scripts)Blue ArgonCRITICAL
2Code obfuscation (base64, char encoding)Red TitaniumCRITICAL
3Excessive/unused permissionsPurple PotassiumHIGH
4Missing privacy policyPurple LithiumHIGH
5Missing metadata (icons, description, screenshots)Yellow ZincHIGH
6Single purpose violationRed MagnesiumHIGH
7Deceptive behavior (description ≠ functionality)Red NickelHIGH
8Insecure data transmission (HTTP)Purple CopperHIGH
9Keyword stuffing in manifestYellow ArgonMEDIUM
10Minimum functionality checkYellow PotassiumMEDIUM
11Undisclosed affiliate linksGrey TitaniumMEDIUM
12Cryptocurrency mining codeGrey SiliconCRITICAL
13Copyright circumvention (download helpers)Blue ZincCRITICAL
14Notification spam patternsYellow NickelMEDIUM
15Data collection without consentPurple NickelHIGH

Step 4: Generate report

Output report using template in references/report-template.md.

Report structure per issue:

## Issue: [Name]
- **Severity**: CRITICAL / HIGH / MEDIUM
- **Violation Code**: [Chrome code, e.g. Blue Argon]
- **Root Cause**: [What in your code triggers this]
- **File(s)**: [Exact file paths and line numbers]
- **Solution**: [Step-by-step fix]

Report summary:

| Severity | Count |
|----------|-------|
| CRITICAL | X     |
| HIGH     | X     |
| MEDIUM   | X     |
| PASS     | X     |

Verdict: LIKELY APPROVED / NEEDS FIXES / WILL BE REJECTED

Step 5: Save report

  • Markdown: save as extension-review-report.md in project root
  • HTML: save as extension-review-report.html with simple, readable styling

References

  • references/scan-checklist.md — Grep patterns and detection logic for all 15 checks
  • references/violation-codes.md — All Chrome Web Store violation codes with descriptions
  • references/report-template.md — Markdown and HTML report templates

Related Skills

  • extension-analyze — Deeper security audit (code quality, XSS, CSP)
  • extension-publish — Full publishing workflow after review passes
  • extension-manifest — Fix manifest issues found in review
同じリポジトリから

関連する Skills

すべての Skills