CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

transmission-api

Transmission RPC reference covering JSON-RPC 2.0 transport, session token handling, torrent methods, session methods, and protocol versioning.

Quality

67%

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

Quality

Content

57%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.

This is a comprehensive, highly actionable RPC reference with concrete JSON examples and complete parameter tables, but it is a monolithic inlining of the upstream spec into SKILL.md rather than a lean overview pointing to bundle files, and it spends tokens explaining concepts Claude already knows.

Suggestions

Move the full protocol-version changelog (section 5, ~300 lines) into a separate references file (e.g. references/changelog.md) and keep only a one-line pointer plus the current rpc_version_semver note in SKILL.md.

Trim explanations of general concepts Claude already knows (CSRF mechanics, DNS rebinding, HTTP Basic Auth encoding, JSON-RPC error-data semantics) down to Transmission-specific behavior only.

Convert SKILL.md into a lean overview (transport + auth essentials, method index) and split the per-method field tables into references/methods.md so the top-level file stays a navigational hub.

DimensionReasoningScore

Conciseness

The bulk is dense, useful API reference (method/field tables and JSON examples), but it also explains concepts Claude already knows ('CSRF protection', 'DNS rebinding', HTTP Basic Auth encoding, JSON-RPC 2.0 error-data semantics) and inlines a ~300-line version changelog, matching 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean anchor above.

3 / 5

Actionability

Provides copy-paste-ready JSON request/response examples and complete typed parameter tables for every method, fitting 'mostly executable guidance; concrete code or commands with minor gaps'; it stops short of 5 because not every method includes a full round-trip worked example.

4 / 5

Workflow Clarity

There is numbered section structure and one explicit feedback loop (handle HTTP 409 by updating X-Transmission-Session-Id and resending), but no end-to-end usage workflow with validation checkpoints, matching 'sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The document is well-sectioned with headers and tables, but the entire 1135-line spec — especially the ~300-line protocol-version changelog — is inlined into SKILL.md with no split into bundle files, matching 'some structure … content that should be separate is inline'; external links point to repo docs, not skill bundle files.

3 / 5

Total

13

/

20

Passed

Description

65%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 clearly identifies a well-scoped, distinctive niche and surfaces good trigger keywords, but it is reference-style ('covering …') rather than action-oriented and omits any explicit 'Use when …' trigger guidance, which caps completeness at 3.

Suggestions

Rewrite in third-person action voice with concrete verbs, e.g. 'Build and send Transmission RPC requests over JSON-RPC 2.0 — manage torrents, query/set session options, and handle the CSRF session token handshake.'

Add an explicit 'Use when …' clause naming natural trigger phrases, e.g. 'Use when integrating with or scripting a Transmission BitTorrent client via its RPC API, or when the user mentions Transmission, torrent RPC, or X-Transmission-Session-Id.'

Include the synonymous product term 'BitTorrent' to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Transmission RPC domain and lists five concrete coverage areas ('JSON-RPC 2.0 transport, session token handling, torrent methods, session methods, and protocol versioning'), but uses the passive verb 'covering' with noun phrases rather than concrete action verbs, fitting the 'names domain and 1-2 concrete actions' anchor more than the multi-action anchors.

3 / 5

Completeness

The 'what' is clear ('Transmission RPC reference covering …'), but there is no 'Use when …' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3 — matching the 'clear what but when missing' anchor.

3 / 5

Trigger Term Quality

Includes strong natural keywords a developer would say ('Transmission', 'RPC', 'JSON-RPC 2.0', 'torrent', 'session'), matching the 'good keyword coverage; a few natural terms missing' anchor; synonyms like 'BitTorrent' or 'remote control' are absent, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

Targets a specific BitTorrent client's RPC protocol with distinct triggers ('Transmission', 'RPC', 'torrent'), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

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 (1135 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 2 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

tympanix/Electorrent

Path

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