music-library-organizer

Import, tag, and organize music files using beets; enforce consistent folder structure, metadata, and MusicBrainz tagging across the local music library.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/music-library-organizer/SKILL.md

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.

A lean, well-structured skill body with concrete core commands and a clear sequenced workflow including safety validation, but several peripheral steps (rescan, logging, checksum) describe intent without executable specifics, and validation is not embedded as in-flow feedback-loop checkpoints.

Suggestions

Make peripheral steps executable: specify the rescan trigger (e.g., an exact MCP call or CLI), the logbook record command, and the checksum tool/command for integrity validation.

Embed validation as an explicit in-flow checkpoint — e.g., 'After move, run checksum; if mismatch, restore from inbox backup and halt' — to add a validate→fix→retry feedback loop and lift workflow clarity.

Trim the Purpose section's overlap with the frontmatter description to nudge conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept-explanation padding (it does not explain what beets or MusicBrainz are), and workflow steps are terse. Not a 5 because the Purpose section restates the frontmatter description ('tag, organize, MusicBrainz, folder structure, metadata'), a minor redundancy that could be trimmed.	4 / 5
Actionability	Core steps are concrete and executable — 'beet import -A', 'beet duplicates', the 'Library/Artist/Year - Album/Track - Title.ext' template, and an explicit tag list — but peripheral steps ('Signal subsonic-media-server to rescan', 'Record import summary in homelab-logbook', 'Validate file integrity (checksum)') lack specific commands or mechanisms. Not a 3 because the actionable core is strong; not a 5 because several steps give direction rather than executable specifics.	4 / 5
Workflow Clarity	Eight clearly sequenced steps plus validation in the Safety section (checksum before/after move, inbox backup, no-delete-without-confirmation) mean the destructive/batch cap does not apply. Not a 5 because validation lives in a separate section rather than as an explicit in-flow checkpoint with a validate→fix→retry feedback loop embedded in the sequence.	4 / 5
Progressive Disclosure	Under 50 lines, no local bundle files needed (references/ and scripts/ hold only .gitkeep), and content is organized into clearly headed sections — meeting the simple-skill exception that allows a 5 with well-organized sections. Not a 4 because there are no organization gaps; the single-file overview is appropriate for this scope.	5 / 5
	Total	17 / 20 Passed

Description

75%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 that lists comprehensive concrete actions and occupies a clear niche, but it omits any explicit 'Use when…' trigger guidance, which caps completeness and leaves the 'when to use' question unanswered.

Suggestions

Add an explicit 'Use when…' clause naming trigger phrases (e.g., 'Use when organizing downloaded music, tagging a library for Subsonic/Navidrome, or fixing missing metadata') to lift completeness above 3.

Include natural synonyms and file extensions users actually say (e.g., 'mp3, flac, music collection') to push trigger-term coverage toward comprehensive.

Keep the third-person imperative voice ('Import, tag, and organize…') which is already correct — no change needed there.

Dimension	Reasoning	Score
Specificity	Quotes 'Import, tag, and organize music files using beets; enforce consistent folder structure, metadata, and MusicBrainz tagging' — names the domain plus six concrete actions (import, tag, organize, enforce folder structure, enforce metadata, MusicBrainz tagging), which is comprehensive coverage matching the anchor-5 example. Not a 4 because the action list is more than 'several with minor gaps'; it covers the skill's full surface.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when…' clause or equivalent explicit trigger guidance, which the guidelines say caps completeness at 3. Not a 4 because 'when' is entirely absent rather than present-but-could-be-more-explicit.	3 / 5
Trigger Term Quality	Natural terms like 'music files', 'tag', 'import', 'music library', and 'beets' are present, but there are no synonyms or file extensions (e.g., mp3, flac, 'music collection') that anchor 5 requires. Not a 3 because the keyword coverage is genuinely good rather than 'some relevant keywords missing common variations'.	4 / 5
Distinctiveness Conflict Risk	The beets + MusicBrainz + local music library niche is specific with distinct triggers and minimal overlap with other skills. Not a 4 because it is not merely 'mostly distinct with minor overlap' — the tool-bound niche makes conflict risk minimal.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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/music-library-organizer/SKILL.md
Commit: 0f62e6b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.