dj-library-curator

Curate, tag, and organize the DJ music library; manage BPM analysis, key detection, genre tagging, and crate/playlist creation for DJ workflows.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/dj-library-curator/SKILL.md

Quality

Content

72%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 concise, well-organized skill body with a clear sequenced workflow and appropriate safety notes, but it stops short of being executable: no command examples for the named analysis tools, no tagging syntax, and no validation step to confirm metadata writes after batch operations. Progressive disclosure is appropriately handled for a skill of this size.

Suggestions

Add executable command examples for the core analysis steps, e.g. `bpm-tools track.mp3` or `keyfinder-cli -a track.wav`, and the tagging command used to write BPM/key back to files.

Insert a validation step after batch tagging/re-analysis (e.g., re-read tags with a spot-check on a sample of tracks and re-run analysis on outliers) to satisfy the batch-operation feedback-loop requirement.

Give concrete rules for crate assignment (e.g., key compatibility via the Camelot wheel, BPM-range thresholds) instead of the current open-ended criteria list.

Dimension	Reasoning	Score
Conciseness	The 44-line body is lean and efficient: short sections (Purpose, Invocation, Workflow, Safety, MCP, References, Companion Skills) with no explanation of concepts Claude already knows and no padding. Every token earns its place, matching anchor 5.	5 / 5
Actionability	Specific tools ("bpm-tools", "keyfinder-cli", "essentia") and concrete outputs (M3U/PLS) are named, but no executable commands, flags, or code examples appear anywhere — guidance is concrete but incomplete with missing key details, matching anchor 3. Not 4 because nothing in the skill is copy-paste executable; not 2 because the named tools and specific outputs go beyond minimal high-level hints.	3 / 5
Workflow Clarity	Seven steps are clearly sequenced and the Safety section adds pre-operation safeguards ("Back up metadata before bulk re-analysis"), but there are no validation checkpoints verifying that tags were written correctly or that analysis output is sane. Since the workflow involves batch tagging/re-analysis, the rubric's batch-operation cap limits this to 3. Not 4 because backup guidance is precautionary, not a verify-after-write feedback loop.	3 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections and no bundle files to reference (references/ and scripts/ are empty); external tool URLs are clearly signaled and one level deep. Per the simple-skill exception this matches anchor 5.	5 / 5
	Total	16 / 20 Passed

Description

66%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 solid, specific description with good natural DJ terminology, held back by a missing explicit "Use when..." trigger clause and by not mentioning the DJ software integrations (Rekordbox/Serato/Traktor) or export actions that would broaden trigger coverage. Distinct from related skills but with some overlap risk against a general music-library organizer.

Suggestions

Append a trigger clause, e.g. "Use when the user mentions DJ software (Rekordbox, Serato, Traktor), crates, BPM/key tagging, or preparing tracks for a DJ set."

Include the export/sync capability in the description (e.g., "export crates as M3U playlists and sync to Subsonic") so those invocations are discoverable from the frontmatter.

Add natural synonyms such as "tempo analysis" or "harmonic mixing" to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("manage BPM analysis, key detection, genre tagging, and crate/playlist creation") with a named domain, but coverage has minor gaps — playlist export, M3U generation, and DJ software sync covered by the body are absent, matching anchor 4 rather than the comprehensive anchor 5.	4 / 5
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines a missing 'when' clause caps completeness at 3. Not 4 because the 'when' is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	Natural DJ phrases like "DJ music library", "BPM analysis", "key detection", and "crate/playlist" are present, but common variations users would say — Rekordbox, Serato, Traktor, M3U, tempo/harmonic mixing — are missing, placing it at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The DJ niche with BPM/key/crate terminology is mostly distinct, with only minor overlap risk against a generic music-library-organizer skill, matching anchor 4. Not 5 because "tag, and organize the DJ music library" could collide with general library organization skills.	4 / 5
	Total	15 / 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/dj-library-curator/SKILL.md
Commit: ff4471e

Reviewed: 2 hours 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.