CtrlK
BlogDocsLog inGet started
Tessl Logo

subsonic-media-server

Manage and interact with a Subsonic-compatible music streaming server (Navidrome or Airsonic); control playback, manage playlists, and trigger library rescans via the OpenSubsonic API.

57

Quality

65%

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 ./skills/subsonic-media-server/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 skill body is concise, well-structured, and clearly scoped, but its workflow steps lack executable request examples and inline validation checkpoints for destructive/batch operations. Adding a concrete authenticated request example and embedding validation steps would materially improve actionability and workflow clarity.

Suggestions

Add at least one copy-paste-ready authenticated request example (e.g., a curl call assembling u/t/s/v/c params against /rest/startScan or /rest/search3) to lift actionability.

Integrate the Safety validation rules into the workflow as explicit checkpoints (e.g., a 'Verify reachability' step before bulk operations, a 'Confirm before delete' gate before destructive actions).

Show a short example response snippet and how to parse it, so the 'Parse' step is concrete rather than abstract.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding of concepts Claude already knows; the only trimmable redundancy is the Purpose section restating the description, keeping it just below the fully-lean anchor.

4 / 5

Actionability

It names concrete endpoints ('/rest/getArtists', '/rest/search3', '/rest/startScan') and auth tokens ('u=', 't=', 's=', 'v=', 'c='), but provides no assembled executable request, code example, or sample response, matching the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

A clear six-step sequence exists, but validation is relegated to a separate Safety section rather than embedded as workflow checkpoints, and the rubric caps batch/destructive skills without inline validation at 3.

3 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections with one-level-deep pointers (MCP file, external API URLs, companion skills), with only minor organization gaps keeping it below the ideal anchor.

4 / 5

Total

14

/

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.

The description is specific and well-targeted to a distinct niche with good trigger keywords, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding a usage-trigger sentence would raise the completeness score.

Suggestions

Append an explicit trigger clause such as 'Use when the user wants to control playback, manage playlists, search, or rescan a Navidrome/Airsonic/Subsonic music server.'

Include a few more natural synonyms ('music', 'songs', 'streaming') alongside the product names to broaden trigger-term coverage.

Optionally add 'search the library' to the action list to round out coverage of capabilities mentioned in the body.

DimensionReasoningScore

Specificity

Lists several concrete actions ('control playback, manage playlists, and trigger library rescans') plus the specific API surface ('via the OpenSubsonic API'), matching the anchor for several specific actions with minor coverage gaps; not a 5 because only three actions are named and search/browsing/scrobble are absent.

4 / 5

Completeness

It clearly answers 'what' (manage/interact, playback, playlists, rescans) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage including product names ('Navidrome', 'Airsonic', 'Subsonic') and terms ('playback', 'playlists', 'library rescans'), but a few common synonyms users might say ('music', 'songs', 'stream') are missing, so it falls short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Subsonic-compatible self-hosted streaming servers) with distinct product/API triggers, giving minimal overlap risk with other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pvnkmnk/AgenticSelfHostSkills
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.