CtrlK
BlogDocsLog inGet started
Tessl Logo

soulseek-network-orienter

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

50

Quality

55%

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

57%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 and concise, but it offers mostly abstract guidance and delegates all concrete execution to companion skills, while the download/log workflow lacks validation checkpoints. Adding a concrete search example and an approval/verification checkpoint would substantially improve it.

Suggestions

Include at least one concrete, copy-paste-ready example (e.g., a sample slskd search query string or a representative search-term construction) so the guidance is actionable rather than only delegated.

Add an explicit validation/approval checkpoint in the Workflow before coordinating downloads (e.g., "Confirm targets with the user; never auto-download") and verify the Obsidian write succeeded before declaring completion.

Tighten the "Soulseek Culture" intro and deduplicate tools already named in the Workflow section from the Companion Skills list to remove minor redundancy.

DimensionReasoningScore

Conciseness

Sections are terse bullet lists with no padding about basics Claude already knows; only minor trim opportunities like "not just a data source" and repeated companion-skill mentions, matching anchor 4.

4 / 5

Actionability

Guidance is high-level ("Search by artist, release, label…", "Maintain a good share ratio") and delegates execution to companion skills without any concrete search syntax, slskd API call, or example query, matching anchor 2.

2 / 5

Workflow Clarity

A clear 4-step sequence exists, but steps coordinating downloads and writing to the Obsidian vault are batch/destructive operations with no validation checkpoint, so the rubric cap of 3 applies.

3 / 5

Progressive Disclosure

The references/scripts bundles are empty and the body is a simple, well-organized skill with clear section headers and one-level external links, so the simple-skill exception yields a 5.

5 / 5

Total

14

/

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 third-person and clearly scoped to Soulseek, but it lacks an explicit "Use when…" trigger clause and only hints at concrete actions. Adding natural trigger phrases and a few more specific actions would lift completeness and trigger-term quality.

Suggestions

Add an explicit "Use when…" clause naming natural triggers (e.g., "Use when the user wants to find music on Soulseek, research the Soulseek community, or log discoveries to Obsidian").

Expand the action list with concrete specifics (e.g., "crafts targeted search queries, evaluates share ratios and queue etiquette, and journals results") to improve specificity.

Include common synonyms/file extensions users say (e.g., "Soulseek", "slsk", "music discovery") for better trigger-term coverage.

DimensionReasoningScore

Specificity

"Teaches Soulseek culture, etiquette, and search strategies; logs discoveries to Obsidian" names the domain plus two action families, but does not enumerate the distinct concrete actions (matching anchor 3).

3 / 5

Completeness

The description gives a clear "what" but omits any "Use when…" trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"Soulseek" and "Obsidian" are relevant natural keywords, but common variations or natural phrasings users would say are missing, so it fits anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The Soulseek-focused framing plus Obsidian logging carves a clear niche with only minor overlap risk against generic music/Obsidian skills, matching anchor 4.

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.

Validation15 / 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
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.