music-library-safety

Guard consequential personal music-library work with explicit ownership, preview, recovery, and approval checks. Use before scanning, tagging, moving, deduplicating, importing, deleting, or synchronizing music files, metadata, playlists, samples, stems, or mixlists.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%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 well-organized safety-gate skill with clear sequencing, validation steps, and clean routing to companion skills. Its main weakness is actionability: it gives procedural direction but no concrete executable commands or tool invocations for the operations it governs.

Suggestions

Add one or two concrete executable commands or tool examples (e.g., a read-only beets list/duplicate query) so the inspect/preview steps are copy-paste ready rather than purely descriptive.

Spell out an explicit validate → fix → re-validate feedback loop in the Safe Workflow rather than leaving recovery implicit, to push workflow_clarity to the top anchor.

Tighten the Purpose and Hard Stops enumerations slightly to trim redundant phrasing and improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows (no 'what is a music library' filler), but a few phrases like the full enumeration in Purpose and Hard Stops could be tightened, placing it at 4 rather than the maximally lean 5.	4 / 5
Actionability	The workflow gives concrete procedural guidance (inspect, confirm recovery, preview, request approval, execute, validate) but provides no executable commands, code, or specific tool invocations — it describes rather than scripts, matching the score-3 anchor of incomplete/pseudocode-level guidance.	3 / 5
Workflow Clarity	The Safe Workflow is a clear six-step sequence with explicit validation (step 6 'Validate and record') and the Hard Stops act as checkpoints, but the validate-fix-retry feedback loop is only weakly implied rather than fully spelled out, so it sits at 4 instead of 5.	4 / 5
Progressive Disclosure	The skill is a concise overview that appropriately routes detail to companion skills (music-library-organizer, dj-library-curator, homelab-change-control) with clear one-level navigation and no nested or buried references, matching the score-5 anchor for a well-structured overview.	5 / 5
	Total	16 / 20 Passed

Description

96%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 strong, specific description with concrete actions, comprehensive natural trigger terms, and an explicit 'Use before...' clause answering both what and when. Minor overlap risk with its listed companion skills keeps distinctiveness just below the top anchor.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'scanning, tagging, moving, deduplicating, importing, deleting, or synchronizing' — covering the music-library domain comprehensively, matching the score-5 anchor for multiple specific concrete actions.	5 / 5
Completeness	It explicitly answers 'what' (guard consequential music-library work with ownership/preview/recovery/approval checks) and 'when' via the explicit 'Use before scanning, tagging, moving...' trigger clause, matching the score-5 anchor for both.	5 / 5
Trigger Term Quality	It enumerates natural user-facing terms including 'music files, metadata, playlists, samples, stems, or mixlists' plus verbs users would say, giving comprehensive coverage of natural phrases and synonyms.	5 / 5
Distinctiveness Conflict Risk	The music-library safety niche is fairly distinct and scoped to consequential writes, but the broad term 'synchronizing music files' plus overlap with companion skills (organizer, curator) creates minor conflict risk, so it sits at 4 rather than 5.	4 / 5
	Total	19 / 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-safety/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.