use-rest-api
Provides access to the Torrust Tracker REST API for querying and testing.
Install
mkdir -p .claude/skills/use-rest-api && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16604" && unzip -o skill.zip -d .claude/skills/use-rest-api && rm skill.zipInstalls to .claude/skills/use-rest-api
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use the Torrust Tracker REST API. Covers authentication, all endpoints (stats, metrics, torrents, auth keys, whitelist), and making announce/scrape requests to verify API behaviour. Triggers on "use API", "test API", "call REST API", "query API", "API endpoint", "curl tracker", "tracker client", "announce request", or "verify API".Key capabilities
- →Authenticate with the Torrust Tracker REST API using header or query parameter methods
- →Query health check, stats, and metrics endpoints
- →Manage auth keys (POST, DELETE, GET reload)
- →Manage whitelist entries (POST, DELETE, GET reload)
- →Retrieve torrent information (GET single torrent, GET all torrents)
- →Make UDP and HTTP announce/scrape requests using `tracker_client`
How it works
This skill enables authenticated interaction with the Torrust Tracker REST API by providing methods for authentication, detailing available endpoints for stats, metrics, auth keys, whitelist, and torrents, and demonstrating how to make announce/scrape requests using the `tracker_client` binary. It also outlines a verif
Inputs & outputs
When to use use-rest-api
- →Querying tracker statistics
- →Testing API endpoint behavior
- →Sending announce/scrape requests
- →Managing API access tokens
About this skill
Moved: use-rest-api
This skill moved to .claude/skills/use-rest-api/SKILL.md in issue #2866.
When not to use it
- →When the tracker is not running or the REST API is not enabled
- →When the task does not involve interacting with the Torrust Tracker REST API
- →When the task requires permissions beyond those granted by the configured access tokens
Prerequisites
Limitations
- →The skill requires a running tracker with the REST API enabled
- →Authentication relies on access tokens defined in the TOML config file
- →The skill's examples use `http://localhost:1212` as the default base URL
How it compares
This skill provides a complete guide to interacting with the Torrust Tracker REST API, including authentication, endpoint details, and client usage examples, offering a structured approach compared to exploring the API without specific
Compared to similar skills
use-rest-api side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| use-rest-api (this skill) | 0 | 4mo | Review | Intermediate |
| add-api-version | 1 | 9mo | Review | Advanced |
| solana-dev | 0 | 7mo | Review | Advanced |
| mcp | 0 | 10mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by torrust
View all by torrust →You might also like
add-api-version
oxidecomputer
Add a new version to a Dropshot HTTP API. Use when the user wants to make versioned changes to a Dropshot-managed HTTP API, such as adding, making changes to, or removing an API endpoint.
solana-dev
mashharuki
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering
mcp
Piebald-AI
Guide for working with Splitrail's MCP server. Use when adding tools, resources, or modifying the MCP interface.
solana-dev
solanabr
Unified skill hub for Solana development. Routes to external submodule skills (solana-foundation, sendai, solana-game, trailofbits, cloudflare, qedgen, colosseum) and local skills. Progressive disclosure — read only what you need.
azure-eventhub-rust
RJsolucoes
|
tauri
EpicenterHQ
Tauri path handling, cross-platform file operations, and API usage. Use when working with file paths in Tauri frontend code, accessing filesystem APIs, or handling platform differences in desktop apps.