lyrics-and-theory-bridge

Bridges lyric writing with music theory concepts — helps composer-lyricists align words with chord function, melody contour, rhythm, and song structure.

Quality

64%

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/lyrics-and-theory-bridge/SKILL.md

Quality

Content

63%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-structured, actionable instruction-only skill with a clear sequenced workflow and useful failure-mode branching. Its main weaknesses are re-teaching basic music theory that Claude already knows and failing to route the inlined link list through the existing references/links.md bundle.

Suggestions

Trim or remove the "Theory Reference Points" definitions of basic chord functions and cadences, keeping only the non-obvious mappings specific to this skill's use.

Replace the inlined "References" URL list with a single signaled pointer to references/links.md (e.g. "See [references/links.md](references/links.md) for curated theory and rhyme resources") so the bundle is actually used and references stay one level deep.

Add an explicit verify step before "Save" (e.g. confirm the suggested edit preserves meaning per the Safety rule) to strengthen the workflow's validation checkpoint.

Dimension	Reasoning	Score
Conciseness	Sections are mostly lean and bullet-driven, but the "Theory Reference Points" section re-teaches basic harmony Claude already knows ("I (tonic/resolution)", "Perfect authentic (V→I)"), which is unnecessary explanation that could be tightened.	3 / 5
Actionability	Concrete, specific guidance throughout ("a word swap to fix a stressed syllable, a chord substitution... a structural change (pre-chorus, bridge)"); absence of code is appropriate for this instruction-only skill and not penalized.	4 / 5
Workflow Clarity	Seven workflow steps are clearly sequenced (Ingest → Analyse prosody → Analyse harmony → Melodic contour → Flow mapping → Propose → Save), with the Failure Modes and Safety sections supplying branching checkpoints; the skill is suggest-only/non-destructive so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Section structure is clear, but the body inlines external URL references while a references/links.md bundle file exists and is not signaled from the body (it duplicates Adam Neely and Hooktheory entries), leaving reference organization only partially realized.	3 / 5
	Total	14 / 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 clear, specific description that names its niche and several concrete alignment dimensions, but it omits any explicit "Use when..." trigger guidance, which caps completeness. Trigger-term coverage is good though a few common synonyms are absent.

Suggestions

Add an explicit trigger clause, e.g. "Use when a composer-lyricist wants to align lyrics with chord function, melody contour, rhythm, or song structure."

Include more natural user-facing synonyms (flow, hook, rhyme scheme, beats, bars) to broaden trigger-term coverage.

Split the single "align" action into a couple of distinct concrete verbs (e.g. analyze, map, suggest) to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete alignment aspects ("chord function, melody contour, rhythm, and song structure"), but the verbs are limited to "Bridges" and "align", a single primary action applied across dimensions rather than multiple distinct concrete actions.	4 / 5
Completeness	The description clearly answers "what" (bridges lyric writing with music theory, aligns words with harmony/melody/rhythm/structure) but provides no "Use when..." trigger clause, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good natural keyword coverage ("lyric writing", "music theory", "chord function", "melody contour", "rhythm", "song structure", "composer-lyricists"), though a few natural variations users say (flow, hook, rhyme, beats) are missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (composer-lyricists aligning words with theory) with distinct triggers, with only minor overlap risk against pure music-theory or pure lyric skills.	4 / 5
	Total	15 / 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/lyrics-and-theory-bridge/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.