obsidian-music-journal

Create and maintain music-related journal entries in Obsidian; log listening sessions, DJ set plans, album reviews, discovery notes, and curation reflections.

Quality

71%

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/obsidian-music-journal/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.

The body is lean, well-structured, and actionable with concrete template paths, metadata fields, tags, and folder conventions. Its main gap is the absence of explicit validation checkpoints in the vault-writing workflow, which caps workflow clarity despite a clear step sequence.

Suggestions

Add explicit validation checkpoints to the workflow, e.g., after Save verify the note exists and after Index confirm no duplicate entry was created.

Integrate the Safety rules (never overwrite, confirm before delete) as in-workflow checkpoints rather than only a standalone section.

Trim the redundant Purpose section since it restates the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows (no 'what is Obsidian' padding), but the Purpose section mildly restates the frontmatter description and the Invocation list has some redundancy, leaving minor trimming possible.	4 / 5
Actionability	Provides concrete, specific guidance — template paths (templates/listening-session.md), metadata fields, tag set, and save folder (Music Journal/YYYY/MM/) — which is actionable for an instruction-only skill; absence of code is not penalized given the actionable specifics.	4 / 5
Workflow Clarity	A clear 7-step sequence is present, but vault-writing plus index-updating is a batch/destructive-ish context with no explicit validation checkpoints (e.g., verify note created, wikilinks resolve, index deduplicated), capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	At under 50 lines with empty bundle directories and no need for external reference files, the well-organized section structure (Purpose, Invocation, Workflow Steps, Safety, MCP, References, Companion Skills) provides easy navigation, satisfying the simple-skill exception for a 5.	5 / 5
	Total	16 / 20 Passed

Description

71%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 specific and domain-distinct, listing multiple concrete journal-entry types, but omits any explicit 'Use when...' trigger guidance, which limits its completeness and slightly weakens trigger-term quality. It is mostly distinguishable from sibling skills with only minor overlap risk.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when logging a listening session, drafting a DJ set plan, or reviewing an album in Obsidian').

Include natural synonyms and the .md file extension in the trigger terms to improve keyword coverage.

Sharpen distinctiveness from dj-set-architect by clarifying that this skill journals set plans rather than architecting them.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create and maintain music-related journal entries' plus 'log listening sessions, DJ set plans, album reviews, discovery notes, and curation reflections' — giving comprehensive coverage of the music-journal domain.	5 / 5
Completeness	Has a clear 'what' but no 'when' — there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes good natural terms users would say (listening session, album review, DJ set plan, discovery notes), but lacks synonyms, file extensions (.md), and any explicit 'Use when...' phrasing, keeping it below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Obsidian music journal) with distinct triggers, but 'DJ set plans' overlap with the companion dj-set-architect skill, creating minor overlap risk.	4 / 5
	Total	16 / 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/obsidian-music-journal/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.