CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

netrunner-media-orchestrator

Orchestrates the full acquisition-to-playback media pipeline for the netrunner project.

Quality

64%

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/netrunner-media-orchestrator/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.

The body is a well-structured, lean overview that sequences the pipeline clearly and delegates detail to eleven companion skills, with a genuine failure-handling section. Its main weakness is actionability: steps name which skill to invoke but give few executable specifics for the operations this skill itself performs.

Suggestions

Add concrete verification detail to the ingest step, e.g. the actual Subsonic API call or skill command used to confirm new files appear after a rescan.

Give each workflow step a one-line executable anchor (command or API endpoint) so the orchestrator is actionable even before companion skills load.

Drop the redundant 'Companion Skills' section or replace it with a short mapping of step → skill, removing the duplicate listing.

DimensionReasoningScore

Conciseness

Sections are lean with no explanations of concepts Claude already knows, and the ASCII pipeline diagram is token-efficient. Minor duplication remains: 'Companion Skills' restates skill names already cited in 'Workflow Steps', and the agent-specific 'Invocation' section is meta-overhead.

4 / 5

Actionability

Routing guidance is concrete ('Run `music-library-organizer` on downloaded files', 'poll `getScanStatus`; retry after timeout') but there are no executable commands or code, and checkpoints like 'verify new files appear' omit the how — matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

Seven steps are clearly sequenced with an ingest verification ('verify new files appear') and a Failure Modes section providing retry loops (pause/notify, poll/retry, queue/retry). Not 5: validation is not woven into every step — e.g. the organize step has no verification of tags or structure.

4 / 5

Progressive Disclosure

Well-organized sections delegate detail one level deep to companion skills instead of inlining it, and both references/ and scripts/ are empty (no buried or nested files). Scored 4 rather than 5 because the ~77-line body exceeds the under-50-line simple-skill exception and no reference files exist.

4 / 5

Total

15

/

20

Passed

Description

45%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 concise and names its domain clearly, but it relies on the single generic verb 'orchestrates' without stating concrete capabilities, trigger terms, or any 'use when' guidance. It would rarely be selected from a vague user request alone.

Suggestions

List concrete pipeline capabilities in the description, e.g. 'Downloads music via Soulseek/slskd, tags and organizes files, ingests them into Subsonic, and logs sessions to an Obsidian vault'.

Add an explicit trigger clause such as 'Use when coordinating netrunner media sessions — acquiring, organizing, serving, or DJ-curating music'.

Include natural trigger terms users would say: 'download music', 'Soulseek', 'Subsonic', 'DJ set', 'music library' alongside the existing pipeline vocabulary.

DimensionReasoningScore

Specificity

The description names the domain ('acquisition-to-playback media pipeline for the netrunner project') but the only action offered is the generic verb 'orchestrates' — no concrete capabilities such as downloading, tagging, ingesting, or curating are stated.

2 / 5

Completeness

A clear 'what' is present ('orchestrates the full acquisition-to-playback media pipeline'), but there is no 'when' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'media pipeline', 'acquisition', 'playback', and 'netrunner' are relevant keywords, but the natural phrases a user would actually say ('download music', 'Soulseek', 'Subsonic', 'DJ set', 'music library') are missing.

3 / 5

Distinctiveness Conflict Risk

It is scoped to a specific project ('netrunner'), but as a top-level orchestrator over a large family of sibling skills (slskd-media-acquisition, subsonic-media-server, music-library-organizer) with no distinctive trigger phrases, it could still overlap with those closely related skills.

3 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

pvnkmnk/AgenticSelfHostSkills

Path

skills/netrunner-media-orchestrator/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.