Checks lyrics for rhyme, syllable count, stress and flow, or finds rhymes for a word. Use when the user wants a diagnosis or a line-level fix for sound or meter.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Rhyme Checker?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/vocaler-ai-rhyme-checker)
---
name: rhyme-checker
description: "Checks lyrics for rhyme, syllable count, stress and flow, or finds rhymes for a word. Use when the user wants a diagnosis or a line-level fix for sound or meter."
license: MIT
metadata:
author: Vocaler
version: "1.3.0"
category: songwriting
homepage: https://skills.vocaler.ai/rhyme-checker/
repository: https://github.com/Vocaler-AI/music-skills
---
# Rhyme Checker
Checks rhyme, syllable count, stress and flow, finds rhymes by sound, and fixes a line without losing its meaning, end rhyme or meter.
## When to use
- The user pastes lyrics and asks whether they rhyme, flow or scan.
- The user needs rhymes for a word, with options beyond the obvious.
- A line feels clunky and the user cannot tell why.
## What to look for in the request
- The lyrics or the word to rhyme.
- Language, accent and delivery when relevant. A beat, melody, target count or matching section can give a line its intended shape.
- Any constraints on what the fix must preserve, such as meaning, end word or scheme.
Do not interview the user. If something is missing, make a sensible assumption and deliver; mention an assumption only when it changes the result. Ask only when the answer would change the result completely.
Lead with the deliverable and skip closing notes that only restate it. Before answering, check your own numbers (syllables, bars, timings, totals) and facts. Never invent artists, records, dates, settings or product features; leave out what you are not sure of.
Deliver everything the user asked for in this answer; do not offer to do part of it later. Follow explicit requests exactly (named attributes, counts, limits). Count and calculate with code if you can run it; otherwise write the units out as you count. Then re-read your answer against your own tables: every number, note, time and claim must agree.
## Workflow
1. For a rhyme search, use the word's pronunciation in context. Group usable words or phrases by rhyme closeness, and give syllable counts or stress where they affect fit.
2. For a draft, map end rhymes by section and note internal rhymes that affect the flow. Describe closeness (perfect or near) separately from span (single or multiple syllables).
3. Count syllables and show natural word stress on the phrases being diagnosed. Use the supplied beat or melody to assess placement. With text alone, compare corresponding phrases and state any pronunciation that changes the diagnosis.
4. Identify whether the problem comes from sound, wording, count or stress placement. Fix that condition at line level. Preserve a working end rhyme when shortening an overlong line, and match the target phrase length when there is one.
5. Keep the user's stated constraints on meaning, rhyme and rhythm. Show the updated count or rhyme for each fix, and identify any tradeoff outside those constraints.
## Rules
- Judge by sound. For example, 'should have read' can rhyme with 'bed', while 'need to read' can rhyme with 'seed'.
- Keep deliberate slant rhymes, repetitions and delivery choices that work in context.
- Point out stock pairs (fire/desire, heart/apart) when they make a line predictable; keep them when the line earns them.
- Name the rhyme device when it matters: multisyllabic and internal rhyme (central to rap), assonance (shared vowels: building / children), consonance (shared consonants). Treat these as craft, not errors.
- Mark counts that depend on accent, contraction or delivery (I'ma, been, fire as one or two syllables) instead of presenting them as certain.
- Verify sound and count as facts; do not claim a line is emotionally strong or weak as if it were measurable. Label taste as an opinion.
- Match the depth of the review to the request. A count-only request needs counts and relevant pronunciation variants.
- Be exact about vowels: a perfect rhyme needs the same stressed vowel and everything after it (building / yielding is a slant rhyme, not perfect). Recount every line you change.
- Write out the syllables of every line you count (grind-ing all night), and count with code if you can. Map internal rhyme chains across bars (night / sight, vision / win it / in it), not only line endings.
- Judge rhyme on the stressed vowels. In rap and most pop, unstressed endings need not match: BUILD-ing / CHIL-dren (same stressed vowel and l) is a standard slant rhyme, not an error. Call a rhyme weak only relative to the style and the rhymes around it, and never 'fix' a working slant rhyme by default.
## Output format
```markdown
| Line | Syllables | Stress or phrasing | End rhyme |
|------|-----------|--------------------|-----------|
**Diagnosis** — [line and cause]
**Fix** — [replacement, updated count or rhyme, and any tradeoff]
For a rhyme search, list usable matches by rhyme closeness instead.
```
## Example
**Request:** This line has to take eight syllables and rhyme with 'train': 'I left your key outside in the pouring rain.' Help with the meter.
**Response (abridged):**
```
'Rain' and 'train' rhyme. The line has 11 syllables against a target of 8.
Try 'I left your key in driving rain' (8). The main phrase stresses can fall on LEFT, KEY, DRIV- and RAIN. It keeps the end rhyme and the heavy rain.
```
## Works well with
- `prosody-checker` for checking against the melody or beat
- `lyrics-writer` for rewriting more than a line
Suggest one of these only when the user's next step needs it.