CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deluge-api

Deluge Web JSON-RPC and core RPC reference covering session login, web methods, and commonly used core torrent operations.

Quality

69%

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

Quality

Content

65%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 content is a well-structured, mostly executable API reference with good conciseness, but it lacks validation checkpoints for destructive operations and inlines bulk method tables that belong in a separate reference file.

Suggestions

Add validation checkpoints to the session flow (e.g., verify web.connected() after web.connect and check the returned method list) and a warning before destructive calls like core.remove_torrent(remove_data=True).

Move the large web/core method tables into a bundled reference file (e.g. references/methods.md) and keep SKILL.md as an overview with a one-level-deep link, improving progressive disclosure.

Add a brief error-handling note for the documented RPC error response format so callers can detect and react to failures rather than only seeing the happy path.

DimensionReasoningScore

Conciseness

The body is a lean reference—method tables, exact parameters, and a concrete request-body example with no padding about what Deluge or JSON-RPC is; the only minor trim is the Electorrent section re-listing methods already in the tables.

4 / 5

Actionability

Provides an executable JSON request body, a precise session-flow sequence, and method tables with exact parameter signatures—mostly executable guidance with only minor gaps (e.g., no full end-to-end call example).

4 / 5

Workflow Clarity

The session flow is clearly sequenced (auth.login → web.get_hosts → web.connect → use core/web methods), but there are no validation checkpoints, and destructive/batch operations like core.remove_torrent(remove_data) are present, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Sections are well-organized and external docs are linked, but the large web and core method tables are inlined in SKILL.md rather than split into a bundled reference file, and no references/scripts/assets bundle files exist to offload the bulk.

3 / 5

Total

14

/

20

Passed

Description

57%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 distinctive and names the Deluge domain well, but it lacks an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrases, capping completeness and trigger-term quality at 3.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when integrating with the Deluge Web UI, calling Deluge JSON-RPC or core RPC, or managing torrents through Deluge.'

Include more natural user-facing trigger terms and synonyms ('Deluge API', 'Deluge WebUI', 'torrent management', '.torrent') alongside the technical jargon to improve trigger-term quality.

Replace the noun-style 'reference covering' with concrete action verbs ('Call', 'Authenticate to', 'Manage torrents via') to lift specificity above 3.

DimensionReasoningScore

Specificity

Names the domain ('Deluge Web JSON-RPC and core RPC') and a few concrete areas ('session login, web methods, and commonly used core torrent operations'), but frames them as a 'reference covering' rather than concrete action verbs, leaving coverage non-comprehensive.

3 / 5

Completeness

It clearly answers 'what' (a reference covering session login, web methods, core torrent operations) but provides no 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

'Deluge' and 'torrent operations' are natural user terms, but much of the description is technical jargon ('JSON-RPC', 'core RPC', 'web methods') and common variations/synonyms like 'Deluge API' or 'Deluge WebUI' are absent.

3 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to Deluge's Web JSON-RPC and core RPC, giving it a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

14

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tympanix/Electorrent

Path

.agents/skills/deluge-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.