jgkme/chrome-extension-mv3-workflow
.cursor/skills/chrome-extension-mv3-workflow/SKILL.md
Build, debug, and validate Chrome Extension Manifest V3 changes in this repository. Use when editing background service worker logic, content scripts, popup/options pages, permissions, or extension messaging.
$ install --global
skillsauthnpx skillsauth add jgkme/Add-Remote-Torrent chrome-extension-mv3-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:58 PM4.6s1 file scanned
SKILL.md
- name:
- chrome-extension-mv3-workflow
- description:
- Build, debug, and validate Chrome Extension Manifest V3 changes in this repository. Use when editing background service worker logic, content scripts, popup/options pages, permissions, or extension messaging.
Chrome Extension MV3 Workflow
Quick Start
When asked to implement or fix extension behavior:
- Identify the target surface:
background.js,content_script.js,popup/*,options/*, ormanifest.json. - Verify permission and host requirement changes in
manifest.json. - Build with
bun run build. - Validate console/runtime errors in extension pages and service worker logs.
Editing Checklist
- Keep Manifest V3 constraints in mind (service worker lifecycle, no persistent background page).
- Use explicit message contracts between content script and background.
- Fail safely for network/client API errors and include actionable error text.
- Avoid DOM injection risks; sanitize any user-derived strings before rendering.
- Preserve existing user settings compatibility in
chrome.storage.
Validation Commands
Run from repo root:
bun install
bun run build
Done Criteria
- Build succeeds with no webpack errors.
- Required permissions are minimal and intentional.
- Affected user flows still work: add torrent, server selection, and options save.
Related Skills
jgkme/version-bump-and-changelog
tools
VerifiedTrustedCommunity
Perform safe extension version bumps and changelog updates for this repository. Use when preparing a release, synchronizing version metadata, updating changelog entries, and validating generated artifacts.
26SKILL.mdUpdated Apr 17, 2026
jgkme/torrent-client-handler-patterns
tools
VerifiedTrustedCommunity
Implement and review torrent client API handlers consistently across this repository. Use when adding or fixing files in api_handlers, authentication flow, request formatting, or post-add operations like labels, categories, and directories.
26SKILL.mdUpdated Apr 17, 2026
jgkme/release-packaging-checklist
tools
VerifiedTrustedCommunity
Create and verify release artifacts for this extension using the existing build pipeline. Use when bumping versions, generating zip/crx files, computing checksums, and checking release consistency.
26SKILL.mdUpdated Apr 17, 2026
jgkme/issue-triage-and-repro
tools
VerifiedTrustedCommunity
Triage bug reports and reproduce extension issues consistently in this repository. Use when analyzing user-reported failures, validating reproduction steps, collecting debug evidence, and preparing actionable fix notes.
26SKILL.mdUpdated Apr 17, 2026