MCP HubMCP Hub
스킬 목록으로 돌아가기

lyric-reviewer

bitwize-music-studio
업데이트됨 2 days ago
6 조회
209
37
209
GitHub에서 보기
메타ai

정보

lyric-reviewer 스킬은 Suno 생성 전에 가사의 운율, 운율법, 발음, 구조에 대한 문제를 14가지 품질 체크리스트로 분석합니다. 이 스킬은 기악 트랙을 자동으로 건너뛰며, 개별 트랙 또는 전체 앨범을 처리할 수 있습니다. 음악 생성 전, 가사 작성 후에 이 스킬을 사용하여 잠재적인 문제를 발견하고 수정하세요.

빠른 설치

Claude Code

추천
기본
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git 클론대체
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/lyric-reviewer

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

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
  • Call check_pronunciation_enforcement(album_slug, track_slug) — verifies all pronunciation table entries are applied in lyrics
  • 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.)

WordContext ASpellingContext BSpelling
liveverb (to live)livadjective (live show)lyve
readpresent tensereedpast tensered
leadverb (to lead)leednoun (metal)led
windnoun (air)windverb (to wind)wynd
tearnoun (crying)teerverb (to rip)tare
bassnoun (fish)bassnoun (music)bayss
bownoun (ribbon)bohverb (to bow)bow
closeverb (to close)clozeadjective (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

LevelDefinitionAction Required
CriticalWill cause Suno problems or legal riskMust fix before generation
WarningQuality issue, impacts songShould fix, can proceed with caution
InfoNitpick, optional improvementNice 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. You are QC, not creative - Identify issues, don't rewrite lyrics yourself
  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.

GitHub 저장소

bitwize-music-studio/claude-ai-music-skills
경로: skills/lyric-reviewer
0
ai-musicai-music-toolsaudio-masteringclaudeclaude-codeclaude-code-plugin

연관 스킬

content-collections

메타

이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.

스킬 보기

polymarket

메타

이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.

스킬 보기

creating-opencode-plugins

메타

이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.

스킬 보기

sglang

메타

SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.

스킬 보기