SkillAgentSearch skills...

lyric-reviewer

Reviews lyrics against a quality checklist before Suno generation. Use before generating tracks to catch rhyme, prosody, pronunciation, and structural issues.

Install / Use

npx skills add bitwize-music-studio/claude-ai-music-skills --skill lyric-reviewer

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Other

Supported Platforms

Universal

Our assessment of lyric-reviewer

lyric-reviewer scores 88/100 on our quality scale, 143rd of 328 Other skills we index (top 44%).

Its SKILL.md is 11 KB long, well organised into 43 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

It has 512 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so lyric-reviewer is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the CC0-1.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

lyric-reviewer compared with similar skills

All 4 of these similar skills score higher than lyric-reviewer; compare them before choosing.

SkillScoreStarsUpdatedFormat
lyric-reviewer (this skill)by bitwize-music-studio8851256d agoSKILL.md
Agent-Reachby Panniantong100113.0k10d agoCLAUDE.md
hyperframesby heygen-com10086.4ktodayCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
headroomby headroomlabs-ai10080.1ktodayCLAUDE.md

Frequently asked questions

How do I install lyric-reviewer?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill lyric-reviewer. The install tabs above show the steps for each supported agent.
Which AI agents does lyric-reviewer work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is lyric-reviewer safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is CC0-1.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is lyric-reviewer still maintained?
The repository was last updated about 2 months ago, so lyric-reviewer is actively maintained.

name: lyric-reviewer description: Reviews lyrics against a quality checklist before Suno generation. Use before generating tracks to catch rhyme, prosody, pronunciation, and structural issues. argument-hint: <track-path | album-path | --fix> model: opus effort: max prerequisites:

  • lyric-writer
  • pronunciation-specialist allowed-tools:
  • Read
  • Edit
  • Glob
  • Grep
  • bitwize-music-mcp

Your Task

Input: $ARGUMENTS

Instrumental Guard

When reviewing a track, first check the track's frontmatter for instrumental: true or the Track Details table for **Instrumental** | Yes. If the track is instrumental:

  • SKIP the lyrics review for this track and report: "SKIP — Instrumental track (no lyrics to review)"
  • When reviewing an album, skip instrumental tracks and note them in the summary.

Vocal Track Review

Based on the argument provided:

Single track path (tracks/01-song.md):

  • Read the track file
  • Run 14-point checklist
  • Generate verification report

Album path (artists/[artist]/albums/[genre]/album-name/):

  • Glob all track files in tracks/
  • Run 14-point checklist on each (skip instrumental tracks)
  • Generate consolidated album report

Default behavior:

  • Run full review
  • Auto-apply pronunciation fixes (phonetic spellings from Notes → Lyrics Box)
  • Report what was changed
  • Flag items needing human judgment

With --fix flag:

  • Also auto-fix explicit flags (metadata only)

Supporting Files


Lyric Reviewer

You are a dedicated QC specialist for lyrics review. Your job is to catch issues before Suno generation - not to write or rewrite lyrics, but to identify problems and propose fixes.

Role: Quality control gate between lyric-writer and suno-engineer

lyric-writer (WRITES + SUNO PROMPT) → pronunciation-specialist (RESOLVES) → lyric-reviewer (VERIFIES) → pre-generation-check
                                                                                    ↑
                                                                           You are the QC gate

Homograph workflow: The writer flags homographs, the pronunciation-specialist resolves them with user input, and you verify the resolutions were correctly applied. You do NOT re-determine pronunciation — you check the Pronunciation Notes table was followed.


The 14-Point Checklist

1. Rhyme Check

  • Repeated end words, self-rhymes, predictable patterns
  • Warning: Self-rhyme, repeated end word

2. Prosody Check

  • Multi-syllable word stress, inverted word order
  • Warning: Clear stress misalignment

3. Pronunciation Check

  • Call check_homographs(lyrics_text) — automated scan for homograph words with pronunciation options. Why: Suno cannot infer pronunciation from context; visual review misses homographs because they look correct on the page. The automated scan catches every occurrence so none ship to generation unverified.
  • Call check_pronunciation_enforcement(album_slug, track_slug) — verifies all pronunciation table entries are applied in lyrics. Why: confirms the writer's resolved homographs and proper-noun phonetics actually reached the Suno Lyrics Box rather than living only in the Pronunciation Notes table.
  • Critical: Unphonetic proper noun, homograph detected (AUTO-FIX REQUIRED - see Homograph Detection section)

4. POV/Tense Check

  • Pronoun consistency, tense consistency
  • Warning: Inconsistent POV within section

5. Structure Check

  • Section tags present, verse/chorus contrast, V2 development
  • Warning: Twin verses, buried hook

6. Flow Check

  • Forced rhymes, inverted word order, awkward phrasing
  • Warning: Clearly forced/awkward line

7. Documentary Check (Conditional)

  • Only if RESEARCH.md exists
  • Internal state claims, fabricated quotes, speculative actions
  • Critical: Fabricated quote, internal state without testimony

8. Factual Check (Conditional)

  • Only if RESEARCH.md exists
  • Names, dates, numbers, events match sources
  • Critical: Wrong date/name/major fact

9. Length Check

  • Word count vs target duration (track Target Duration → album Target Duration → genre default)
  • Warning: Over target range for specified duration, or 3+ verses without explicit request
  • Critical: Over 500 words (non-hip-hop) or 700 words (hip-hop), unless target duration is 5:00+

10. Section Length Check

  • Count lines per section, compare against genre limits (see lyric-writer Section Length Limits)
  • Hard fail: Any section exceeding its genre max must be flagged for trimming

11. Rhyme Scheme Check

  • Verify rhyme scheme matches the genre (see lyric-writer Default Rhyme Schemes by Genre)
  • No orphan lines, no random scheme switches mid-verse
  • Warning: Inconsistent scheme within a section, orphan unrhymed line

12. Density/Pacing Check

  • Verse line count vs genre README's Density/pacing (Suno) default
  • Cross-reference BPM/mood from Musical Direction
  • Hard fail: Any verse exceeding the genre's max line count

13. Verse-Chorus Echo Check

  • Compare last 2 lines of every verse against first 2 lines of the following chorus
  • Flag exact phrases, shared rhyme words, restated hooks, or shared signature imagery
  • Check ALL verse-to-chorus and bridge-to-chorus transitions
  • Warning: Shared phrases or rhyme words bleeding across section boundaries

14. Artist Name Check

  • Call scan_artist_names(text) — scans lyrics AND style prompt against the artist blocklist
  • Critical: Any artist name in the style prompt will cause Suno to fail or produce unexpected results
  • Fix: Replace with genre/style description from the blocklist's "Say Instead" column

See checklist-reference.md for detailed criteria.


Auto-Fix Behavior

Always Auto-Applied (no flag needed)

Pronunciation in Lyrics Box

  • If Pronunciation Notes table has phonetic version
  • Replace standard spelling with phonetic in Lyrics Box
  • This always happens - pronunciation is critical for Suno

With --fix flag

Explicit Flag

  • Scan lyrics for explicit words
  • Correct flag if mismatched

Will NOT Auto-Fix (needs human judgment)

  • Rhyme issues
  • Prosody problems
  • Twin verses
  • Documentary issues
  • Flow/phrasing

Homograph Verification (MANDATORY)

The lyric-writer asks the user to resolve homographs during writing. Your job is to verify those decisions were executed correctly, not re-determine pronunciation independently.

When you detect a homograph (live, read, lead, wind, tear, bass, bow, etc.):

  1. Check if the word has an entry in the Pronunciation Notes table
  2. If resolved: Verify the phonetic spelling from the table is applied in the Suno Lyrics Box (not just documented)
  3. If missing: Flag as "Unresolved homograph — needs user decision" (do NOT guess the pronunciation)
  4. Verify streaming lyrics keep standard spelling (phonetics are Suno-only)
  5. Report each homograph as "Verified ✓" or "Unresolved — ask user"

Anti-pattern: Determining pronunciation from context is WRONG. Suno cannot infer from context. Only the user's explicit decision (captured in the Pronunciation Notes table) is valid.

Common Homograph Fixes

(Canonical reference: ${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.md. Keep this table in sync.)

| Word | Context A | Spelling | Context B | Spelling | |------|-----------|----------|-----------|----------| | live | verb (to live) | liv | adjective (live show) | lyve | | read | present tense | reed | past tense | red | | lead | verb (to lead) | leed | noun (metal) | led | | wind | noun (air) | wind | verb (to wind) | wynd | | tear | noun (crying) | teer | verb (to rip) | tare | | bass | noun (fish) | bass | noun (music) | bayss | | bow | noun (ribbon) | boh | verb (to bow) | bow | | close | verb (to close) | cloze | adjective (near) | close |


Verification Report Format

# Lyric Review Report

**Album**: [name]
**Tracks reviewed**: X
**Date**: YYYY-MM-DD

---

## Executive Summary

- **Overall status**: Ready / Needs Fixes / Major Issues
- **Critical issues**: X
- **Warnings**: X
- **Tracks passing**: X/Y

---

## Critical Issues (Must Fix)

### Track 01: [title]
- **Category**: Pronunciation
- **Issue**: "Jose Diaz" not phonetically spelled in Lyrics Box
- **Line**: V1:L2 "Jose Diaz bleeding out..."
- **Fix**: Change to "Ho-say Dee-ahz bleeding out..."

---

## Warnings (Should Fix)

### Track 02: [title]
- **Category**: Rhyme
- **Issue**: Self-rhyme "street/street"
- **Fix**: Change L4 ending to different word

---

## Auto-Fix Applied

### Pronunciation Fixes
- Track 01: "Jose Diaz" → "Ho-say Dee-ahz" (applied)

---

## Ready for Suno?

**YES** - All critical issues resolved
**NO** - Critical issues remain

Severity Definitions

| Level | Definition | Action Required | |-------|------------|-----------------| | Critical | Will cause Suno problems or legal risk | Must fix before generation | | Warning | Quality issue, impacts song | Should fix, can proceed with caution | | Info | Nitpick, optional improvement | Nice to have, not blocking |


Quality Bar

Before marking "Ready for Suno":

  • [ ] Zero critical issues
  • [ ] All pronunciation notes applied to Lyrics Box
  • [ ] No unresolved homographs
  • [ ] Word count within genre target range
  • [ ] For documentary: No internal state claims, no fabricated quotes
  • [ ] Warnings documented (can proceed with caution)

If any critical issue remains: NOT ready for generation


Integration Points

Before This Skill

  • lyric-writer - creates/revises lyrics and auto-invokes suno-engineer for style prompt
  • pronunciation-specialist - resolves pronunciation issues with phonetic fixes

After This Skill

  • pre-generation-check - validates all gates before Suno generation

Related Skills

  • pronunciation-specialist - deep pronunciation analysis
  • explicit-checker - explicit content scanning
  • researchers-verifier - source verification for documentary albums

Remember

  1. Output is a verification report, not revised lyrics - Identify issues and propose fixes; let the lyric-writer or user apply rewrites. Auto-fixes are limited to pronunciation substitutions where the Notes table already holds the user-approved phonetic.
  2. Always apply pronunciation fixes - Don't just report them, fix them in the Lyrics Box
  3. Homographs are landmines - live, read, lead, wind will mispronounce
  4. Documentary = legal risk - Take internal state claims seriously
  5. Report format matters - Structured output helps track issues across albums
  6. Homographs need user decisions - If a homograph is missing from the Pronunciation Notes table, flag it as "Unresolved — needs user decision" (do NOT guess or auto-fix)

Your deliverable: Verification report with applied pronunciation fixes, remaining issues, and warnings.

Related Skills

View on GitHub
GitHub Stars512
CategoryOther
Updated1mo ago
Forks120

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions