CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

soulseek-network-orienter

Teaches Soulseek culture, etiquette, and search strategies; logs discoveries to Obsidian.

Quality

72%

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/soulseek-network-orienter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-organized, concise, and culturally substantive, with concrete etiquette rules, search strategies, and clear delegation to companion skills. Main improvement room is in making the workflow and suggestions slightly more executable (example queries, Obsidian log format).

DimensionReasoningScore

Conciseness

The body is lean and list-driven with no explanation of concepts Claude already knows, but the 5-line Invocation block and the "Soulseek is a community of music enthusiasts, not just a data source" framing are minor instances of padding that could be trimmed.

4 / 5

Actionability

Concrete, specific guidance throughout ("Search by artist, release, label, year, genre, or scene keywords", "Prioritize high-quality files (FLAC, high-bitrate MP3)", named delegation to slskd-media-acquisition and obsidian-music-journal) with minor gaps such as an example search term or an Obsidian entry format.

4 / 5

Workflow Clarity

A clear 4-step sequence (clarify intent, suggest terms, coordinate download, log) with a user-approval checkpoint and an explicit Failure Modes recovery section, but validation is implicit rather than inline in the workflow itself.

4 / 5

Progressive Disclosure

A short (~68-line), well-sectioned skill with no bundle files and nothing that warrants splitting into separate files; external pointers (slskd, slsknet.org) and companion-skill references are one level deep and clearly signaled.

5 / 5

Total

17

/

20

Passed

Description

53%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 a clear niche, but it omits any "when to use" guidance and never mentions music, its core subject. It reads as a topic list rather than a trigger-ready capability statement.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Soulseek, slskd, or wants to find/download music via P2P sharing, or asks about Soulseek etiquette."

Include the word "music" (and variations like "slsk"/"slskd") so the description matches what users naturally say.

Split the topic list into more distinct actions (e.g. "suggests targeted search terms", "recommends well-seeded FLAC/MP3 sources", "logs discoveries") to strengthen specificity.

DimensionReasoningScore

Specificity

"Teaches Soulseek culture, etiquette, and search strategies; logs discoveries to Obsidian" names the domain and two concrete actions (orient/teach, log to Obsidian), but the three topics ride on the single verb "teaches", so it does not reach anchor 4's "several specific actions".

3 / 5

Completeness

The description gives a clear "what" but contains no "Use when..." clause or equivalent trigger guidance; the rubric explicitly caps completeness at 3 in that case.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Soulseek", "etiquette", "search strategies", "Obsidian"), but the central noun "music" is absent along with "download"/"share" and platform variations (slsk, slskd), matching anchor 3's "relevant keywords but missing common variations".

3 / 5

Distinctiveness Conflict Risk

"Soulseek" is a highly distinct niche trigger with minimal conflict risk, but "logs discoveries to Obsidian" overlaps with companion Obsidian-journal skills, fitting anchor 4 ("mostly distinct; minor overlap risk with closely related skills") rather than 5.

4 / 5

Total

13

/

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/soulseek-network-orienter/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.