CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slskd-media-acquisition

Manage and automate music downloads via slskd (Soulseek daemon), including search, queue management, and transfer monitoring.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/slskd-media-acquisition/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, token-efficient workflow overview with sensible safety guidance and a clear step sequence. The main weaknesses are the absence of executable API examples (relying on description-level guidance like 'submit search query') and a dangling internal reference to mcp/slskd-mcp.json that doesn't exist in the bundle.

Suggestions

Add a concrete example API call or two (e.g., authenticated curl against the search and /transfers/downloads endpoints), or explicitly instruct using the slskd-mcp tools with their exact tool names.

Fix or remove the 'mcp/slskd-mcp.json' reference — no such file exists in the bundle's references/ or scripts/ directories.

Specify the retry policy for stalled transfers (e.g., max attempts, backoff, when to report failure to the user) and how to verify a completed download is a valid audio file.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explanation of what Soulseek or a REST API is, and steps are terse. Minor trimmable tokens remain: the 'Invocation' section partially duplicates what belongs in the description's trigger clause, and the 'Companion Skills' list adds context beyond the skill's core job. Not anchor 5 because those sections don't each earn their place; well above anchor 3 since there is no unnecessary explanation.

4 / 5

Actionability

Some concrete anchors exist — the default base URL 'http://localhost:5030' and the '/transfers/downloads' endpoint — but there are no executable examples (curl/API calls, auth header format, search request shape, response parsing). Steps like 'Submit search query' and 'retrieve results ranked by quality' describe rather than instruct, matching anchor 3's 'concrete guidance but incomplete, missing key details'; not anchor 4, which requires mostly concrete code/commands.

3 / 5

Workflow Clarity

A clear 7-step sequence with checkpoints present: 'Poll transfer status until complete; handle stalled or failed transfers with retry' and 'Validate file extensions before passing to library pipeline'. Since validation/verification steps do exist for this batch operation, the batch-operation cap at 3 does not apply. Not anchor 5 because the retry handling is vague (no failure limits or escalation) and there is no verification that downloaded files are complete/valid audio before handoff.

4 / 5

Progressive Disclosure

The body is ~40 lines with well-organized sections and one-level-deep external references (slskd GitHub, API docs), which under the simple-skill guidance would merit a 5 — except the bundle structure shows 'mcp/slskd-mcp.json' does not exist in the bundle (references/ and scripts/ are empty), making the sole internal reference a dangling path. This minor organization gap fits anchor 4 better than anchor 5.

4 / 5

Total

15

/

20

Passed

Description

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

A specific, well-scoped description with strong trigger keywords and excellent distinctiveness. Its main weakness is the missing 'when to use' guidance, which caps completeness and leaves trigger behavior implicit.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user wants to download music or albums from Soulseek/slskd, check the download queue, or monitor transfers.'

Include natural synonyms and formats users would say — 'FLAC', '320kbps', 'peer-to-peer music sharing' — to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('music downloads via slskd (Soulseek daemon)') and several concrete actions — 'search, queue management, and transfer monitoring'. Falls short of anchor 5's comprehensive coverage because selection criteria, post-download handoff, and format handling are absent; it clearly exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is clear (manage/automate music downloads via slskd with search, queue management, transfer monitoring), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the judging guideline explicitly caps completeness at 3 in that case. Not anchor 4, which requires both what and when with the when present.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'music downloads', 'Soulseek', 'slskd', 'search', 'queue', 'transfer monitoring'. Not anchor 5 because common variations and synonyms users might say (e.g., 'FLAC', 'peer-to-peer', 'SoulseekQT', 'P2P file sharing') are missing; well above anchor 3's sparse keyword set.

4 / 5

Distinctiveness Conflict Risk

Naming 'slskd (Soulseek daemon)' carves out a clear niche with distinct triggers — a user mentioning Soulseek or slskd would unambiguously mean this skill. Minimal conflict risk with generic download or media skills, matching anchor 5.

5 / 5

Total

16

/

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

pvnkmnk/AgenticSelfHostSkills

Path

skills/slskd-media-acquisition/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.