CtrlK
BlogDocsLog inGet started
Tessl Logo

qbittorrent-api

qBittorrent WebUI API reference covering authentication, sync, transfer, torrent, RSS, and search endpoints for qBittorrent 5.0+.

60

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/qbittorrent-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-organized, token-efficient API reference that is concrete and distinctive, but it lacks executable code examples, validation checkpoints for destructive operations, and any file-based progressive disclosure structure.

Suggestions

Add a few executable request/response examples (e.g., a curl login flow showing the SID cookie, and a sync/maindata poll) to move actionability toward 3.

Add verification checkpoints for destructive/batch operations (e.g., confirm hashes via /torrents/info before /torrents/delete, and validate preferences after setPreferences) to raise workflow clarity.

Move the full endpoint listing into a separate references file (e.g., REFERENCE.md) and keep SKILL.md as a concise overview with well-signaled links, to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is a lean endpoint reference with minimal, purposeful prose and no explanations of concepts Claude already knows (e.g., what qBittorrent or torrents are), so every token earns its place.

3 / 3

Actionability

Concrete HTTP methods, paths, and params are listed throughout (e.g., 'POST /torrents/setDownloadLimit - param: limit bytes/sec') and maindata response fields are enumerated, but there are no executable request/response code examples, leaving it short of copy-paste-ready guidance.

2 / 3

Workflow Clarity

The auth flow is sequenced and endpoints are logically grouped, but destructive/batch operations such as 'POST /torrents/delete' (deleteFiles), 'POST /app/setPreferences', and batch 'hashes' calls have no validation or verification checkpoints, capping workflow clarity at 2 per the rubric guideline.

2 / 3

Progressive Disclosure

Sections are well organized and the external References links are one-level-deep, but with no bundle files the ~170-line full endpoint reference lives entirely inline in SKILL.md rather than being split into a separate reference file, matching the 'content that should be separate is inline' anchor.

2 / 3

Total

9

/

12

Passed

Description

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive for the qBittorrent WebUI API niche with good natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' clause naming common trigger phrases (e.g., 'Use when integrating with qBittorrent, automating torrent management, or interacting with the qBittorrent WebUI API') to raise completeness.

Reframe 'covering...endpoints' as concrete verb-actions (e.g., 'Authenticate to, query, and control qBittorrent via its WebUI API') to push specificity toward 3.

DimensionReasoningScore

Specificity

The description names the domain and enumerates six endpoint groups ('authentication, sync, transfer, torrent, RSS, and search endpoints'), but uses 'covering...endpoints' rather than concrete verb-actions, matching the 'names domain and some actions' anchor rather than the multi-action anchor.

2 / 3

Completeness

It clearly states what the skill covers but includes no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2 rather than reaching the what-AND-when anchor.

2 / 3

Trigger Term Quality

'qBittorrent WebUI API' and the endpoint group names are exactly the natural terms a user integrating with qBittorrent would say, giving good domain coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

'qBittorrent WebUI API' is a specific, narrow niche with distinct triggers that is very unlikely to overlap with other skills, matching the clear-niche anchor.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tympanix/Electorrent
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.