Agent skill

Jacred Tracker Parser

by jacred-fdb in jacred-fdb/jacred

Adds and debugs JacRed torrent/anime tracker parsers (site probe, auth, magnet policy, SyncService, cron, fixtures, dry-run, OpenAPI wiring).

AGPL-3.0Auto-check passedTesting & QA

Install Jacred Tracker Parser

skills CLI
$ npx skills add jacred-fdb/jacred --skill jacred-tracker-parser -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jacred-fdb/jacred jacred-tracker-parser --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jacred-fdb/jacred.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/jacred-tracker-parser .claude/skills/jacred-tracker-parser && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
jacred-tracker-parser
GitHub stars
124
Token cost
~1.4k tokens
SKILL.md length
467 words
Files
2
Skills in repo
2
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Adds and debugs JacRed torrent/anime tracker parsers (site probe, auth, magnet policy, SyncService, cron, fixtures, dry-run, OpenAPI wiring).

  • Works in 5 steps: Fetch listing/home + one detail/show… → Check Jackett def if any; verify live… → Record: encoding, auth, magnet vs… → …
  • Adding a tracker
  • SKILL.md covers Workflow, Site probe (before code), Sync cluster (pick closest… and File set, plus 6 more sections
  • Calls python3, dotnet and npm

What it does

Jacred Tracker Parser is an agent skill from jacred-fdb/jacred. Adds and debugs JacRed torrent/anime tracker parsers (site probe, auth, magnet policy, SyncService, cron, fixtures, dry-run, OpenAPI wiring). Use when adding a tracker, scraping a listing/API, quality gates (1080-only), Batch packs, FlareSolverr, crontab, or when the user mentions tracker slug, ParseShows, limitpage, MagnetNoTrackers, or Jackett defs.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It sits in Testing & QA, covering Web scraping, Scheduled and recurring tasks and Quality gates. It works with OpenAPI. The repository describes itself as: JacRed - a torrent tracker aggregator. The licence is AGPL-3.0.

When your agent uses it

  • Adding a tracker
  • Scraping a listing/API
  • Quality gates (1080-only)
  • The user mentions tracker slug

Example prompts

  • “/jacred-tracker-parser”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Fetch listing/home + one detail/show page (and site JS if downloads are AJAX).
  2. Check Jackett def if any; verify live (paths drift).
  3. Record: encoding, auth, magnet vs .torrent, quality ladder, pagination, host mirrors.
  4. Passkey risk? Prefer BencodeTo.MagnetNoTrackers.
  5. Multi-torrent page? Stable unique FDB url (?ep= / ?id= / #quality).

What it can do on your machine

Read from SKILL.md and the folder at commit dbe1d8b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3
    • dotnet
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jacred Tracker Parser loads about 1.4k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 467 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jacred-fdb/jacred at commit dbe1d8b, republished under its AGPL-3.0 licence (© jacred-fdb). 467 words, ~1,402 tokens.

Download SKILL.mdSave it as .claude/skills/jacred-tracker-parser/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
jacred-tracker-parser
description
Adds and debugs JacRed torrent/anime tracker parsers (site probe, auth, magnet policy, SyncService, cron, fixtures, dry-run, OpenAPI wiring). Use when adding a tracker, scraping a listing/API, quality gates (1080-only), Batch packs, FlareSolverr, crontab, or when the user mentions tracker slug, ParseShows, limit_page, MagnetNoTrackers, or Jackett defs.

JacRed tracker parser

Project playbook for integrating a real tracker into JacRed. Pair with the specialist subagent .cursor/agents/jacred-tracker-parser.md. Full slug catalog: reference.md.

Workflow

Copy and track:

Tracker Progress:
- [ ] 1. Probe site (encoding, auth, API vs HTML, pagination, download path)
- [ ] 2. Choose sync cluster + magnet/auth policy (see reference.md)
- [ ] 3. Implement Parser + SyncService + Controller
- [ ] 4. Wire DI/config/schema/FileDB/crontab/OpenAPI/docs/icon
- [ ] 5. Fixtures + dry_run_{slug}_parser.py + fixture tests
- [ ] 6. Run dry-run + dotnet test --filter FullyQualifiedName~{Name}

Do not ship half-wired trackers. Do not edit the user’s .cursor/plans/*.plan.md unless asked.

Site probe (before code)

  1. Fetch listing/home + one detail/show page (and site JS if downloads are AJAX).
  2. Check Jackett def if any; verify live (paths drift).
  3. Record: encoding, auth, magnet vs .torrent, quality ladder, pagination, host mirrors.
  4. Passkey risk? Prefer BencodeTo.MagnetNoTrackers.
  5. Multi-torrent page? Stable unique FDB url (?ep= / ?id= / #quality).

Prefer official JSON when the site’s own JS uses it (SubsPlease/Knaben/Bitru/Aniliberty).

Sync cluster (pick closest clone)

ClusterClone fromCron shape
Rutor trio (+ ParseLatest)rutor, korsars, anibelka, ultradox, rutrackerHourly parse + daily tasks
Page-range / limit_pagebaibako, rudub, anidub, anistar, leproductionparseFrom/parseTo or limit_page
API latest + backfillknaben, bitru, subspleaseHourly latest + checkpointed crawl
Speciallostfilm, mazepaDedicated endpoints

Details per slug: reference.md.

File set

PiecePath
Parser / Sync / CategoriesInfrastructure/Trackers/{Name}/
CronControllers/Cron/{Name}Controller.cs → /cron/{slug}/…
Details (optional)Models/Details/{Name}Details.cs
Iconweb/public/img/ico/{slug}.ico (that site’s favicon)
Fixtures / teststests/JacRed.Tests/Fixtures/{Name}/, {Name}ParserFixtureTests.cs
Dry-runscripts/dry_run_{slug}_parser.py
Wiring checklist
  • AppOptions, ConfigSchema (slugs + block names), AppConfigurationProvider log case
  • TrackerServiceCollectionExtensions DI
  • FileDB.UrlParsing when URL id is non-obvious
  • Data/example.yaml|conf, Data/init.yaml|conf (synctrackers + block; no secrets)
  • Data/crontab via run-job.sh (stagger minutes; raise max_time for long crawls)
  • web/public/openapi.yaml TrackerSlug → cd web && npm run gen:api
  • Docs: docs/trackers/overview.mdx, tracker-specific page, docs/configuration/trackers.mdx, docs/api-reference/cron.mdx, docs/development/docs-workflow.mdx, README count

Runtime config: binary loads ./init.yaml from CWD, not Data/init.yaml (template only).

Magnet / auth rules (critical)

  • Anibelka: anonymous only — never cookie/login (passkeys).
  • Rutracker: FlareSolverr Warmup; Anistar does not use that path (host/alias mirror split).
  • Ultradox: google/yandex-like Referer or 503; magnets on detail pages.
  • RuDub / Mazepa: MagnetNoTrackers when auth announce has passkey.
  • Successor sites: new slug (e.g. rudub); never retarget predecessor (baibako).
Show full SKILL.md (177 more words)Show less

Quality / Batch

  • Gate only when requested (rudub 1080/2160, lostfilm 1080/2160, subsplease res==1080).
  • Batch/season packs via catalog/show crawl, not only latest window; mark [Batch].
  • JSON APIs: keep max useful fields + rich checkpoint even when filtering resolution.

Verify

bash
python3 scripts/dry_run_{slug}_parser.py
dotnet test tests/JacRed.Tests/JacRed.Tests.csproj --filter FullyQualifiedName~{Name}

Report: slug, auth, sync cluster, magnet policy, quality gate, cron endpoints, test counts.

Pagination (trio maps)

  • Last page comes from the live listing pager of that section, not a global /page/N/ scan and not numbers inside <script>.
  • UpdateTasksParse must prune map slots past the live tail when the pager shrinks.
  • Empty HTML is a failed fetch, not “zero pages”: do not wipe the map.

Anti-patterns

  • Half-wired tracker (missing OpenAPI / synctrackers / crontab / docs)
  • Copied sibling .ico
  • HTML scrape when a stable JSON API exists
  • Colliding FDB URLs on multi-episode pages
  • Committing live cookies/passwords
  • Assuming Data/init.yaml is what the running process loads
  • Treating script-injected page numbers as the listing tail
  • Pruning the task map when the listing fetch returned empty HTML
  • Subagent: .cursor/agents/jacred-tracker-parser.md
  • Catalog: reference.md
  • Lampa / PidTor / NUM card vs query: lampa-search
  • Rutracker CF: Infrastructure/Trackers/Rutracker/README.md
  • Ops docs: docs/trackers/overview.mdx, docs/configuration/trackers.mdx, docs/api-reference/cron.mdx, docs/development/adding-trackers.mdx, docs/development/docs-workflow.mdx

© jacred-fdb, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .cursor/skills/jacred-tracker-parser of jacred-fdb/jacred.

  • SKILL.md
  • reference.md

Open the folder on GitHubat commit dbe1d8b

Compare with similar skills

Jacred Tracker Parser next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jacred Tracker Parser compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jacred Tracker Parser this skilljacred-fdb/jacred124—~1.4kAutomated safety check: PassAGPL-3.0
703 Technologies Fuzzing Testingjabrena/plinth446—~874Automated safety check: PassApache-2.0
Cloud Agents Starterscalar/scalar16k—~1.4kAutomated safety check: PassMIT
Contract Testingpetrkindlmann/qa-skills165—~4.1kAutomated safety check: PassMIT
Type Safetyidavidov13/agentic-playwright223—~3.5kAutomated safety check: PassMIT
Automating API Testingjeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: PassMIT

Similar skills

  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Minimal starter runbook for cloud agents to install dependencies, run packages, execute tests, and troubleshoot the Scalar monorepo quickly.

    16k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Contract Testing

    petrkindlmann/qa-skills

    Implement consumer-driven contract testing with Pact-JS (v16).

    165 GitHub stars~4.1k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Type Safety

    idavidov13/agentic-playwright

    TypeScript type safety conventions for the Playwright scaffold — the "no any" rule, Zod 4 schema patterns (z.strictObject, top-level validators like z.uuid / z.email / z.url / z.int / z.enum)…

    223 GitHub stars~3.5k tokensUpdated 7 days ago
    Testing & QAAuto-check passed
  • Automating API Testing

    jeremylongshore/tons-of-skills-marketplace

    Test automate API endpoint testing including request generation, validation, and comprehensive test coverage for REST and GraphQL APIs.

    2.8k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Context

    counterfact/api-simulator

    Add and evolve Counterfact context classes in .context.ts files, including required unit test coverage for context behavior.

    170 GitHub stars~384 tokensUpdated today
    Testing & QAAuto-check passed

More from jacred-fdb/jacred

  • Lampa Search

    jacred-fdb/jacred

    Debugs JacRed search as Lampa, Lampac PidTor, and NUM actually call it (Jackett v2 card vs query, parselang, isserial, clarification, year gate).

    124 GitHub stars~848 tokensUpdated 3 days ago
    Auto-check passed

Works with

Questions about Jacred Tracker Parser

What does Jacred Tracker Parser do?

Adds and debugs JacRed torrent/anime tracker parsers (site probe, auth, magnet policy, SyncService, cron, fixtures, dry-run, OpenAPI wiring). Jacred Tracker Parser is an agent skill from jacred-fdb/jacred. Adds and debugs JacRed torrent/anime tracker parsers (site probe, auth, magnet policy, SyncService, cron, fixtures, dry-run, OpenAPI wiring).

When should I use Jacred Tracker Parser?

Jacred Tracker Parser fits situations like: adding a tracker; scraping a listing/API; quality gates (1080-only); the user mentions tracker slug.

How do I install Jacred Tracker Parser in Claude Code?

Run `npx skills add jacred-fdb/jacred --skill jacred-tracker-parser -a claude-code`. Or copy the skill folder (.cursor/skills/jacred-tracker-parser in jacred-fdb/jacred) into .claude/skills/jacred-tracker-parser in your project. Claude Code loads it when a task matches its description.

How do I install Jacred Tracker Parser in Codex?

Run `npx skills add jacred-fdb/jacred --skill jacred-tracker-parser -a codex`. Or copy the skill folder (.cursor/skills/jacred-tracker-parser in jacred-fdb/jacred) into .agents/skills/jacred-tracker-parser in your project. Codex loads it when a task matches its description.

Can I use Jacred Tracker Parser in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jacred-fdb/jacred --skill jacred-tracker-parser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jacred-tracker-parser, .gemini/skills/jacred-tracker-parser, .github/skills/jacred-tracker-parser and .opencode/skills/jacred-tracker-parser in your project.

What does Jacred Tracker Parser need to run?

Going by SKILL.md and its folder, Jacred Tracker Parser needs the command-line tools its instructions call (python3, dotnet and npm). Our summary lists: Python 3.

Does Jacred Tracker Parser access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Jacred Tracker Parser safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Jacred Tracker Parser use?

Jacred Tracker Parser is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jacred Tracker Parser use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jacred Tracker Parser?

Skills that share tags, products or a category with Jacred Tracker Parser: 703 Technologies Fuzzing Testing (jabrena/plinth, 446 stars), Cloud Agents Starter (scalar/scalar, 16k stars), Contract Testing (petrkindlmann/qa-skills, 165 stars) and Type Safety (idavidov13/agentic-playwright, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jacred Tracker Parser?

jacred-fdb (a GitHub organization) maintains it in jacred-fdb/jacred, which has 124 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.

Source: jacred-fdb/jacred on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.