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

61%

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

65%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 content is concise, well-organized, and presents a clear end-to-end DJ library workflow. It is held back by a lack of executable code/commands, missing validation checkpoints for batch/destructive metadata operations, and empty bundle directories that limit progressive disclosure.

Suggestions

Add concrete, copy-paste-ready commands for the analyze/tag/export steps (e.g. exact bpm-tools and keyfinder-cli invocations) to lift actionability.

Insert explicit validation checkpoints into the workflow (e.g. 'Verify metadata was written before curating'; 'Confirm crate membership before export') to satisfy the batch/destructive feedback-loop requirement.

Populate references/ with real per-tool reference files (or a detailed USAGE.md) and link to them from the body so detail is offloaded one level deep instead of inlined.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no over-explanation of concepts Claude already knows; each section earns its place (purpose, invocation examples, ordered workflow, safety, references).	5 / 5
Actionability	It names concrete tools (bpm-tools, keyfinder-cli, essentia) and gives invocation examples, but provides no executable commands, code, or exact CLI invocations — only high-level guidance like 'Run BPM and key analysis (e.g. via bpm-tools...)'.	3 / 5
Workflow Clarity	A clear 7-step sequence (Ingest → Analyze → Tag → Curate → Playlist export → Journal → Log) is present, but the Safety section lists precautions without validation checkpoints in the workflow; because steps involve batch/destructive metadata writes, the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Structure is reasonable with clear sections and external reference URLs, but the references/ and scripts/ bundles contain only .gitkeep — there are no real reference files to offload detail to, so content that could be split out (e.g. per-tool usage) is inline and navigation is shallow.	3 / 5
	Total	14 / 20 Passed

Description

58%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 domain-specific and lists several concrete DJ actions, giving it solid specificity and distinctiveness. Its main weakness is the absence of an explicit 'Use when...' trigger clause and limited natural trigger-term coverage, which cap completeness and trigger quality at 3.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural phrases (e.g. 'Use when the user mentions analyzing BPM, detecting key, building DJ crates, or syncing DJ playlists').

Broaden trigger terms with synonyms users actually say ('DJ library', 'crates', 'analyze tracks', 'energy level', 'M3U export') to improve keyword coverage.

Optionally mention the target DJ platforms (Rekordbox/Serato/Traktor) in the description to sharpen distinctiveness from the general music-library-organizer skill.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('manage BPM analysis, key detection, genre tagging, and crate/playlist creation') but omits some core DJ tasks like energy-level tagging and M3U export that the body later reveals, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear (curate/tag/organize a DJ library with specific metadata), but there is no explicit 'when'/'Use when...' trigger clause, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant DJ keywords (BPM, key, genre, crates, playlists) are present, but it lacks natural trigger phrases and synonyms users would actually say (e.g. 'DJ library', 'crate', 'analyze BPM') and misses the 'Use when...' framing.	3 / 5
Distinctiveness Conflict Risk	The DJ-specific niche (BPM, key detection, crates, Rekordbox/Serato framing) is fairly distinct from general music-organizing skills, with only minor overlap risk with a generic music library organizer.	4 / 5
	Total	14 / 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: 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.