quangpl/browser-extension-skills

extension-review

Scan extension source code for Chrome Web Store rejection risks.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/quangpl/browser-extension-skills --skill extension-review

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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
aus demselben Repository

Weitere Skills

Alle Skills