CtrlK
BlogDocsLog inGet started
Tessl Logo

synology-api

Synology Download Station Web API reference covering API discovery, authentication, request format, common errors, and Download Station task operations.

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

80%

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 tight, actionable API reference with concrete examples, but it is monolithic and lacks validation feedback loops for destructive operations. Splitting the per-method reference into a bundled file and adding response-check guidance would lift the two weakest dimensions.

Suggestions

Move the per-method DownloadStation.Task reference (list/getinfo/create/delete/pause/resume/edit) into a references/ file (e.g. TASK_API.md) and keep SKILL.md as an overview pointing to it.

Add an explicit validation step after destructive/batch calls, e.g. 'Check the response success field and per-task error codes; retry or surface failures before proceeding.'

Provide a complete `create` example (POST with uri and file payload) since it is the primary add-download path and currently only described.

DimensionReasoningScore

Conciseness

The body is a dense reference of tables, param lists, and full request examples with no padding about what APIs/HTTP/JSON are, assuming Claude's competence throughout.

3 / 3

Actionability

It provides concrete, copy-paste-ready query-string examples (e.g. the auth login and task list URLs) plus explicit parameter lists and response field shapes for each method.

3 / 3

Workflow Clarity

The 'Electorrent usage' section sequences the API call flow, but there are no explicit validation checkpoints or error-recovery feedback loops despite destructive operations like 'delete'.

2 / 3

Progressive Disclosure

All ~230 lines live in a single monolithic SKILL.md with no bundle files; the per-method API reference is inline content that would be better split into a separate reference file.

2 / 3

Total

10

/

12

Passed

Description

67%

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 well-scoped to a distinct niche, but omits an explicit 'when to use' trigger clause, which is the primary gap. Adding a Use-when phrase would raise completeness and trigger-term quality.

Suggestions

Append a trigger clause such as 'Use when integrating with Synology DSM Download Station via its Web API, or when the user mentions Synology downloads, torrents, or Download Station tasks.'

Add natural user-facing variations ('add torrents', 'manage downloads', 'magnet links') to broaden trigger-term coverage.

Keep the concrete capability list but pair it with the trigger guidance so both 'what' and 'when' are explicit.

DimensionReasoningScore

Specificity

The description lists multiple concrete areas — 'API discovery, authentication, request format, common errors, and Download Station task operations' — matching the anchor for listing several specific actions.

3 / 3

Completeness

It clearly answers 'what' the skill covers, but lacks any 'Use when...' clause or equivalent trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

It surfaces relevant domain terms ('Synology Download Station', 'Web API') a user might say, but offers no trigger phrasing or common variations like 'add downloads' or 'manage torrents'.

2 / 3

Distinctiveness Conflict Risk

The narrow Synology Download Station Web API niche is clearly distinguishable and unlikely to trigger for unrelated skills.

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.