jgkme/torrent-client-handler-patterns
.cursor/skills/torrent-client-handler-patterns/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add jgkme/Add-Remote-Torrent torrent-client-handler-patternsInstall 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 17, 2026, 3:35 AM13.2s1 file scanned
SKILL.md
- name:
- torrent-client-handler-patterns
- description:
- 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.
Torrent Client Handler Patterns
Handler Design Rules
Use these conventions for api_handlers/* changes:
- Keep auth/session flow explicit and isolated per server profile.
- Normalize error handling into readable, user-facing messages.
- Preserve compatibility with older client variants when supported.
- Avoid assuming content-type correctness for torrent files; handle fallbacks.
- Keep test-connection logic separate from add-torrent logic.
Implementation Checklist
- Confirm URL construction for base URL + relative path edge cases.
- Add required headers (for example origin/referer/basic auth) when applicable.
- Treat optional capabilities defensively (missing RPC methods, partial stats).
- Keep parsing strict and predictable for JSON/XML responses.
- Maintain backward compatibility for stored server config fields.
Regression Hotspots
- Multi-server session leakage.
- Client version specific endpoints.
- Label/category/tag not applied after add.
- Race conditions around "latest torrent hash" detection.
- Silent failures in connection tests.
Validation
- Build with
bun run build. - Manually validate one happy path and one failure path for the edited client.
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/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
jgkme/chrome-extension-mv3-workflow
tools
VerifiedTrustedCommunity
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.
26SKILL.mdUpdated Apr 16, 2026