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

68%

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

56%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-organized, sensibly sequenced analysis workflow with good failure-mode handling, weakened by an unnecessary theory primer Claude already knows, action steps that lack concrete output formats or worked examples, and a references/links.md bundle file that the SKILL.md never points to while inlining overlapping links.

Suggestions

Replace the inlined "## References" URL list with a single pointer to references/links.md (e.g. "See [links.md](references/links.md) for theory, rhyme, and chord-analysis resources"), which also surfaces the extra resources (12tone, Open Music Theory, RapPad) currently hidden in the bundle.

Cut or collapse the "Theory Reference Points" section — chord-function labels and textbook cadences are knowledge Claude already has; keep only genuinely project-specific conventions (e.g., the genre-caution about not assuming a 4/4 trap grid).

Make one or two steps executable with a concrete format — e.g., show how a stress map is notated against a bar grid ("pro-MO-tion → [x . x .]") and one worked word-swap suggestion — so the analysis and edit steps can be followed verbatim.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the "Theory Reference Points" section re-explains textbook knowledge Claude already has — "I (tonic/resolution), IV (subdominant/yearning), V (dominant/tension)" and "Perfect authentic (V→I), plagal (IV→I)" — plus a rhyme-type list. That primer is unnecessary padding, matching the "mostly efficient but includes some unnecessary explanation" anchor rather than the minor-trim 4.	3 / 5
Actionability	Steps are concretely named ("Map syllable stress patterns to the beat grid", "map multisyllabic rhyme schemes, internal rhymes, and cadence against the bar grid") but stop short of executable specifics — no example of how to notate a stress map, no worked example of an edit suggestion, no format for the saved analysis note. Guidance is real but missing key details, fitting the 3 anchor rather than the mostly-executable 4.	3 / 5
Workflow Clarity	The seven numbered steps (Ingest → Analyse prosody → Analyse harmony → Melodic contour → Flow mapping → Propose → Save) form a clear sequence, and the Failure Modes section supplies decision points for missing chord progressions, fragmentary lyrics, and absent genre context. There is no explicit validate/retry checkpoint — acceptable since the workflow only suggests edits and never mutates the draft — leaving it just below the 5 anchor.	4 / 5
Progressive Disclosure	A bundle file references/links.md exists but is never referenced from SKILL.md — the body's "## References" section inlines external URLs (MusicTheory.net, Adam Neely, Rhymezone, Hooktheory) that partially duplicate it, while links.md contains additional resources (12tone, Open Music Theory, RapPad) that are never surfaced. Content that should live in the bundle is inlined and the reference is buried, matching the 3 anchor.	3 / 5
	Total	13 / 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, third-person description with a concrete "what" built on specific theory-facing actions, but it omits any explicit "when to use" trigger clause, which caps its completeness. Trigger terms are good though not exhaustive, and the niche is well differentiated.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user is writing lyrics over a chord progression or beat, asks why a line doesn't sit right on the beat, or wants to match melody contour and harmony to lyrical intent."

Include natural synonyms users would actually say — songwriting, rhyme, flow, hooks, bars, rap/hip-hop cadence — to broaden trigger coverage.

Mention the analysis and edit-suggestion outputs (prosody mapping, targeted word/chord edits) so the "what" covers the skill's full capability set.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete actions — "align words with chord function, melody contour, rhythm, and song structure" — going well beyond generic phrasing. It falls short of 5 because coverage is incomplete: it names what gets aligned but not the analysis/editing capabilities the body actually delivers (prosody analysis, targeted edits, flow mapping).	4 / 5
Completeness	The "what" is clear — "Bridges lyric writing with music theory concepts" with the alignment capabilities enumerated — but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline. It is above 2 because the what-half is concrete and multi-faceted, not vague.	3 / 5
Trigger Term Quality	It contains natural user terms like "lyric writing", "music theory", "chord", "melody", "rhythm", and "song structure" that a composer-lyricist would plausibly say. Missing common synonyms such as "songwriting", "rhyme", "flow", "hook", or "bars", which keeps it below the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The lyric-theory alignment niche ("Bridges lyric writing with music theory concepts") is distinct from generic music-theory or lyric-only skills, and terms like "composer-lyricists" narrow it further. Minor overlap risk remains with broad music-theory or songwriting skills, so it does not reach 5.	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: 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.