CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

synology-api

Synology Download Station Web API reference covering API discovery, authentication, request format, common errors, and Download Station task 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

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/synology-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 an efficient, actionable API reference with concrete request examples and a clear end-to-end usage sequence, but it inlines what should be separate reference files and lacks validation/verification steps for destructive batch task operations.

Suggestions

Add validation checkpoints to the task workflow: after each mutating call (create/delete/pause/resume) check the response success flag and per-task error code before proceeding, especially before delete.

Split the bulk error-code tables and per-method reference into a bundled reference file (e.g. references/api_reference.md) and keep SKILL.md as an overview with one-level-deep pointers.

Add concrete example requests for create (including the POST/multipart upload form), delete, and edit so the most common mutating operations are copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean reference material — compact parameter lists and error-code tables with no padding explaining what an API or JSON is, fitting 'efficient; minor instances that could be trimmed'; not a 5 because the full error tables and every task method are inlined rather than deferred.

4 / 5

Actionability

Provides copy-ready request URL examples for discovery, login, logout, and list plus parameter tables for each method, matching 'mostly executable guidance; concrete commands with minor gaps'; gaps include no example for create/delete/edit and the create POST/multipart body is unspecified.

4 / 5

Workflow Clarity

The 'Electorrent usage' section gives a clear 7-step end-to-end sequence, but there are no validation checkpoints and the skill includes destructive batch ops (delete tasks), which per the rubric caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

Section headers give some structure, but no bundle files exist and the bulk API reference (all method docs, every error-code table) is inlined with only a single external PDF URL rather than one-level-deep bundled references, fitting 'some structure but could be better organized'.

3 / 5

Total

14

/

20

Passed

Description

58%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 about the domain and covered API areas and is clearly distinct, but it lacks an explicit 'when to use' trigger clause and omits common user synonyms (NAS, torrents, DSM), which limit completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when integrating with a Synology NAS Download Station via its Web API, or when adding/pausing/deleting download tasks.'

Include natural user synonyms and file/concept terms such as 'Synology NAS', 'torrents', 'magnet links', and 'DSM' so the description matches how users phrase the request.

Optionally enumerate the core task actions (list, create, pause, resume, delete) to push specificity toward a 5.

DimensionReasoningScore

Specificity

Names the concrete domain and five specific covered areas (API discovery, authentication, request format, common errors, task operations), matching the 'several specific actions; minor gaps' anchor; not a 5 because the task verbs (list/create/pause) are not enumerated.

4 / 5

Completeness

Provides a clear 'what' (API reference covering five areas) but has no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes 'Synology', 'Download Station', and 'Web API' but misses common user phrasings like 'Synology NAS', 'torrents', 'downloads', or 'DSM', fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Synology Download Station Web API reference' is a clearly distinct niche with minor overlap risk versus a general Synology skill, matching the 'mostly distinct; minor overlap risk' anchor rather than the niche-defining 5.

4 / 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/synology-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.