CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qbittorrent-api

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

Quality

70%

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 ./.agents/skills/qbittorrent-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

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

The body is a thorough, mostly executable API reference, but it is a monolithic inlined document with no progressive disclosure and lacks validation/confirmation guidance for destructive batch operations.

Suggestions

Split the inlined reference into separate per-endpoint-group files under references/ (e.g. auth.md, torrents.md, rss.md, search.md) and keep SKILL.md as a concise overview pointing to them.

Add explicit validation/confirmation steps for destructive and batch operations (e.g. 'Delete torrents' with deleteFiles=true or hashes=all), such as verifying the torrent list before deletion.

Trim or collapse the redundant 100-line Table of Contents since the markdown headings already provide navigation.

DimensionReasoningScore

Conciseness

Per-endpoint content is lean reference material (parameter tables, return codes, curl examples) with little concept padding, but the 3287-line body inlines the entire API reference and a ~100-line redundant Table of Contents that duplicates the headings, so it could be tightened.

3 / 5

Actionability

Most endpoints provide concrete, executable curl/http examples plus parameter and return tables (e.g. the login curl example), but not every endpoint includes an example, leaving minor gaps.

4 / 5

Workflow Clarity

Only a weak sequence is implied (authenticate via login, then call authenticated endpoints); destructive/batch operations like 'Delete torrents' with deleteFiles=true or hashes=all carry no validation or confirmation guidance, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

The entire API reference is inlined as a monolithic 3287-line SKILL.md with no bundle files (references/, scripts/, assets/ are absent); the content clearly belongs in split per-group reference files, though the Table of Contents and headings provide some structure.

2 / 5

Total

12

/

20

Passed

Description

75%Weight 40%Scale 1-5

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, distinctive, and names the right natural keywords, but it omits any explicit 'when to use' trigger guidance, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to interact with qBittorrent's WebUI API to manage torrents, transfers, RSS feeds, or searches.'

Include a couple of synonyms or natural phrasings users might say (e.g. 'qBittorrent remote control', 'add/manage torrents via API') to round out trigger terms.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete endpoint groups ('authentication, sync, transfer, torrent, RSS, and search endpoints'), giving comprehensive coverage of the API surface rather than generic actions.

5 / 5

Completeness

The 'what' is clear (a WebUI API reference covering named endpoint groups) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('qBittorrent', 'WebUI API', 'torrent', 'RSS', 'search') but omits synonyms and file/extension variants, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (qBittorrent 5.0+ WebUI API) with distinct, product-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (3288 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

tympanix/Electorrent

Path

.agents/skills/qbittorrent-api/SKILL.md

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.