music-project-planner

Plans music production and release projects with milestones, task breakdowns, and Obsidian integration.

Quality

66%

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/music-project-planner/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.

The body is a well-structured, lean overview with a clear sequenced workflow and thoughtful failure-mode handling; its main weaknesses are the lack of an inline validation checkpoint and a task-list format template.

Suggestions

Add an inline validation checkpoint in the workflow (e.g. 'Before generating phases, confirm the project type and release date with the user') to move workflow_clarity to 5.

Provide a short task-list entry template (e.g. '- [ ] task — effort: Xh — phase: Y') so the 'Generate task list' step produces consistent, actionable output.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanations of concepts Claude already knows, but the Inputs and Outputs sections partly restate the workflow steps, leaving minor instances that could be trimmed — fitting the 'efficient; minor over-explanation' anchor rather than the perfectly lean 5.	4 / 5
Actionability	It gives concrete, specific guidance for an instruction-only skill (named phases, a concrete save path 'Projects/Music/project-title.md', explicit failure handling), with only minor gaps such as no task-list format template, matching the 'mostly executable guidance with minor gaps' anchor.	4 / 5
Workflow Clarity	The six workflow steps form a clear sequence and the Failure Modes section supplies error-recovery paths, but the workflow itself lacks inline validation checkpoints (e.g. confirm scope before phasing), placing it at the 'clear sequence, minor validation gaps' anchor rather than 5.	4 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections and only one-level-deep external references (Obsidian Tasks plugin, LANDR guide) with no nested references, so the simple-skill exception applies and it earns the top anchor.	5 / 5
	Total	17 / 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 clear and reasonably specific about the domain and deliverables, but it omits any 'Use when' trigger guidance and lacks synonym coverage, leaving completeness and trigger quality capped at the midpoint.

Suggestions

Append a 'Use when...' clause naming concrete trigger phrases, e.g. 'Use when the user wants to plan an EP, album, single, or remix release with milestones and a schedule.'

Add natural synonym/keyword coverage (album, EP, single, remix, release schedule, deadline) so the description matches phrasings users actually say.

List one or two more distinct actions (e.g. 'breaks projects into phased task lists with deadlines') to move specificity beyond a single 'Plans' verb.

Dimension	Reasoning	Score
Specificity	Names the domain ('music production and release projects') and a few concrete elements ('milestones, task breakdowns, and Obsidian integration'), but the only real action verb is 'Plans' — it does not list several distinct concrete actions, so it stops at the 'names domain and 1-2 concrete actions' anchor rather than reaching 4.	3 / 5
Completeness	The description gives a clear 'what' but contains no 'Use when...' clause or equivalent trigger guidance, which per the rubric guidelines caps completeness at 3 — matching the 'clear what but when is missing' anchor.	3 / 5
Trigger Term Quality	It includes some natural terms a user might say ('music production', 'release projects', 'Obsidian'), but it misses common variations and synonyms (album, EP, single, release schedule) and provides no explicit trigger phrase, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The niche ('music production and release projects' planning with Obsidian) is fairly distinct, with only minor overlap risk against the companion music skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than the fully-distinct 5 (no explicit triggers) or the broader 3.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: pvnkmnk/AgenticSelfHostSkills
Path: skills/music-project-planner/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.