agentleFS
AgnesAI-LabsAgnesAI-Labs/agnet-skills-cn/songwriting-and-ai-music/SKILL.md

songwriting-and-ai-music

Skill1 starsChanged 3 months agoApache-2.0View on GitHub

Write song structure, lyrics, rhyme, and emotional arc, and produce a Suno Style block plus lyric tags the user pastes into their own Suno Custom Mode. Asks for a theme or mood when neither is given. Does not generate audio and does not log in to Suno. Not for translation, coding, or academic literature reviews.

17 other projects use a version of this, 17 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use teams-meeting-pipeline, touchdesigner-mcp and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • john-data-chenSkill

    teams-meeting-pipeline

    Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.

    Also in 10 projects that use this

  • john-data-chenSkill

    touchdesigner-mcp

    Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.

    Also in 6 projects that use this

  • tunnckoCoreSkill

    python-debugpy

    Debug Python: pdb REPL + debugpy remote (DAP).

    Also in 9 projects that use this

  • tunnckoCoreSkill

    node-inspect-debugger

    Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

    Also in 8 projects that use this

  • AsharibAliSkill

    pretext

    DOM-free multiline text measurement and layout using @chenglou/pretext. Use when the user needs text height calculation, virtualized list row sizing, canvas/SVG text rendering, rich-text inline flow, or any scenario involving text layout without DOM reflow.

    Also in 6 projects that use this

  • yusei531642Skill

    claude-design

    Vibe-Editor の UI を「Claude.ai + Claude Code 公式風」にリファインする際に参照するデザインガイド。色 (warm off-white / terra cotta #d97757)、タイポ (Claude 返答は serif・ユーザーは sans)、余白、記号 (⏺・⎿・スピナー)、アニメ (150ms / cubic-bezier(.4,0,.2,1))、メッセージングトーンの具体値を提供する。UI 刷新・新規コンポーネント作成・テーマ追加・エージェント発話の装飾など、見た目やトーンの判断が必要な作業で必ず参照。

    Also in 9 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. 21 are common, 2 are distinctive, and 1 is very specific to this project.

  • 21

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    All slant rhymes can sound lazy.

    line 114
  2. Common:

    Place it where it lands hardest (often first/last line of chorus)

    line 158
  3. Common:

    AVOID (unless you're doing it on purpose):

    line 168
  4. Common:

    When rewriting an existing song with new lyrics:

    line 178
  5. Common:

    Start from the title/hook and build outward

    line 198
  6. Common:

    If you need a specific line somewhere, reverse-engineer the rhyme scheme backward to set it up

    line 201
  7. Common:

    KEEP SOME ORIGINALS: Leaving a few original lines or structures intact adds recognizability and lets the audience feel the connection.

    line 204
  8. Distinctive:

    Only reuse lines the user supplied or clearly has the right to use.

    line 206
  9. Distinctive:

    Do not paste a full copyrighted lyric from memory.

    line 207
  10. Common:

    NO artist names or trademarks.

    line 236
  11. Common:

    Use Exclude Styles field for what you DON'T want

    line 240
  12. Common:

    Put tags in BOTH style field AND lyrics for reinforcement.

    line 276
  13. Common:

    Keep to 5-8 tags per section max — too many confuses the AI.

    line 277
  14. Common:

    Don't contradict yourself ([Calm] + [Aggressive] in same section).

    line 278
  15. Common:

    Always use Custom Mode for serious work (separate Style + Lyrics)

    line 281
  16. Very specific:

    Always add structural tags — without them Suno defaults to flat verse/chorus/verse with no emotional arc

    line 283
  17. Common:

    ALL CAPS = louder, more intense

    line 300
  18. Common:

    Test proper nouns/unusual words in a short 30-second clip first

    line 308
  19. Common:

    Write the concept/hook first — what's the emotional core?

    line 317
  20. Common:

    If adapting, map the original structure (syllables, rhyme, stress)

    line 318
  21. Common:

    Read/sing aloud — catch stumbles, fix meter

    line 321
  22. Common:

    Add metatags to lyrics for performance direction

    line 323
  23. Common:

    If something great happens by accident, keep it

    line 326
  24. Common:

    Don't be precious about rules.

    line 347

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

来源与修改说明

  • 本 Skill 基于 songwriting-and-ai-music 适配,原作者 Teknium (teknium1)、Hermes Agent;调用名:songwriting-and-ai-music。
  • 本版本变化:
    • 删除 Hermes 本地安装 heartmula / audiocraft 的段落;不承诺在对话里出音频。
    • 交付物固定为:歌词(分节 + 结构标签)+ Suno Style 段;生成在用户自己的 Suno 完成。
    • 歌词用用户的对话语言;Style 场默认英文(Suno 对英文风格描述更稳)。没有主题时先补问。
  • 上游许可证全文见本包 LICENSE(MIT,Copyright (c) 2025 Nous Research)。

写歌与 AI 音乐提示词

这里是写作指南,不是死规则。对歌曲有用的就留,没用的就扔。

何时使用

  • 写新词、定结构、钩子和情绪弧。
  • 写给 Suno Custom Mode 的 Style 与歌词标签。
  • 在用户提供原词或明确有权使用的材料上,做节奏对齐的改词/戏仿。

不要用于:点餐、写代码、纯翻译、文献综述、论文打分。
不要声称已经生成 mp3,也不要让用户在本 Skill 里粘贴 Suno 账号或 API Key。

缺什么就先问

开始写整首之前,至少要有:主题或情绪、语言(默认跟用户对话语言)、可选的风格/人声。信息不够就问一轮,不要空写一首无关的歌。

戏仿或改词:用户未提供原词时,只给结构映射方法,或请用户粘贴他们有权使用的歌词;不要整首复述受版权保护的原词。

交付物(每首至少这三块)

  1. 结构:用了哪种骨架(如 ABABCB)以及各段功能。
  2. 歌词:分节;节名用 [Verse] [Chorus] 等标签;按用户语言写。
  3. Suno Style:一段英文风格描述(流派 + 情绪 + 年代 + 乐器 + 人声 + 动态弧)。可选 Exclude Styles。

然后写一句:请到 Suno 打开 Custom Mode,Style 粘风格段,Lyrics 粘带标签的歌词。本对话不生成音频。

表格若出现,只用标准 Markdown,单元格内不要写 <br>。


1. Song Structure (Pick One or Invent Your Own)

Common skeletons — mix, modify, or throw out as needed:

ABABCB  Verse/Chorus/Verse/Chorus/Bridge/Chorus    (most pop/rock)
AABA    Verse/Verse/Bridge/Verse (refrain-based)    (jazz standards, ballads)
ABAB    Verse/Chorus alternating                    (simple, direct)
AAA     Verse/Verse/Verse (strophic, no chorus)     (folk, storytelling)

The six building blocks:

  • Intro — set the mood, pull the listener in
  • Verse — the story, the details, the world-building
  • Pre-Chorus — optional tension ramp before the payoff
  • Chorus — the emotional core, the part people remember
  • Bridge — a detour, a shift in perspective or key
  • Outro — the farewell, can echo or subvert the rest

You don't need all of these. Some great songs are just one section that evolves. Structure serves the emotion, not the other way around.


2. Rhyme, Meter, and Sound

RHYME TYPES (from tight to loose):

  • Perfect: lean/mean
  • Family: crate/braid
  • Assonance: had/glass (same vowels, different endings)
  • Consonance: scene/when (different vowels, similar endings)
  • Near/slant: enough to suggest connection without locking it down

Mix them. All perfect rhymes can sound like a nursery rhyme. All slant rhymes can sound lazy. The blend is where it lives.

INTERNAL RHYME: Rhyming within a line, not just at the ends. "We pruned the lies from bleeding trees / Distilled the storm from entropy" — "lies/flies," "trees/entropy" create internal echoes.

METER: The rhythm of stressed vs unstressed syllables.

  • Matching syllable counts between parallel lines helps singability
  • The STRESSED syllables matter more than total count
  • Say it out loud. If you stumble, the meter needs work.
  • Intentionally breaking meter can create emphasis or surprise

3. Emotional Arc and Dynamics

Think of a song as a journey, not a flat road.

ENERGY MAPPING (rough idea, not prescription): Intro: 2-3 | Verse: 5-6 | Pre-Chorus: 7 Chorus: 8-9 | Bridge: varies | Final Chorus: 9-10

The most powerful dynamic trick: CONTRAST.

  • Whisper before a scream hits harder than just screaming
  • Sparse before dense. Slow before fast. Low before high.
  • The drop only works because of the buildup
  • Silence is an instrument

"Whisper to roar to whisper" — start intimate, build to full power, strip back to vulnerability. Works for ballads, epics, anthems.


4. Writing Lyrics That Work

SHOW, DON'T TELL (usually):

  • "I was sad" = flat
  • "Your hoodie's still on the hook by the door" = alive
  • But sometimes "I give my life" said plainly IS the power

THE HOOK:

  • The line people remember, hum, repeat
  • Usually the title or core phrase
  • Works best when melody + lyric + emotion all align
  • Place it where it lands hardest (often first/last line of chorus)

PROSODY — lyrics and music supporting each other:

  • Stable feelings (resolution, peace) pair with settled melodies, perfect rhymes, resolved chords
  • Unstable feelings (longing, doubt) pair with wandering melodies, near-rhymes, unresolved chords
  • Verse melody typically sits lower, chorus goes higher
  • But flip this if it serves the song

AVOID (unless you're doing it on purpose):

  • Cliches on autopilot ("heart of gold" without earning it)
  • Forcing word order to hit a rhyme ("Yoda-speak")
  • Same energy in every section (flat dynamics)
  • Treating your first draft as sacred — revision is creation

5. Parody and Adaptation

When rewriting an existing song with new lyrics:

THE SKELETON: Map the original's structure first.

  • Count syllables per line
  • Mark the rhyme scheme (ABAB, AABB, etc.)
  • Identify which syllables are STRESSED
  • Note where held/sustained notes fall

FITTING NEW WORDS:

  • Match stressed syllables to the same beats as the original
  • Total syllable count can flex by 1-2 unstressed syllables
  • On long held notes, try to match the VOWEL SOUND of the original (if original holds "LOOOVE" with an "oo" vowel, "FOOOD" fits better than "LIFE")
  • Monosyllabic swaps in key spots keep rhythm intact (Crime -> Code, Snake -> Noose)
  • Sing your new words over the original — if you stumble, revise

CONCEPT:

  • Pick a concept strong enough to sustain the whole song
  • Start from the title/hook and build outward
  • Generate lots of raw material (puns, phrases, images) FIRST, then fit the best ones into the structure
  • If you need a specific line somewhere, reverse-engineer the rhyme scheme backward to set it up

KEEP SOME ORIGINALS: Leaving a few original lines or structures intact adds recognizability and lets the audience feel the connection. Only reuse lines the user supplied or clearly has the right to use. Do not paste a full copyrighted lyric from memory.


6. Suno AI Prompt Engineering

Style/Genre Description Field

FORMULA (adapt as needed): Genre + Mood + Era + Instruments + Vocal Style + Production + Dynamics

BAD:  "sad rock song"
GOOD: "Cinematic orchestral spy thriller, 1960s Cold War era, smoky
       sultry female vocalist, big band jazz, brass section with
       trumpets and french horns, sweeping strings, minor key,
       vintage analog warmth"

DESCRIBE THE JOURNEY, not just the genre:

"Begins as a haunting whisper over sparse piano. Gradually layers
 in muted brass. Builds through the chorus with full orchestra.
 Second verse erupts with raw belting intensity. Outro strips back
 to a lone piano and a fragile whisper fading to silence."

TIPS:

  • V4.5+ supports up to 1,000 chars in Style field — use them
  • NO artist names or trademarks. Describe the sound instead. "1960s Cold War spy thriller brass" not "James Bond style" "90s grunge" not "Nirvana-style"
  • Specify BPM and key when you have a preference
  • Use Exclude Styles field for what you DON'T want
  • Unexpected genre combos can be gold: "bossa nova trap", "Appalachian gothic", "chiptune jazz"
  • Build a vocal PERSONA, not just a gender: "A weathered torch singer with a smoky alto, slight rasp, who starts vulnerable and builds to devastating power"

Metatags (place in [brackets] inside lyrics field)

STRUCTURE: [Intro] [Verse] [Verse 1] [Pre-Chorus] [Chorus] [Post-Chorus] [Hook] [Bridge] [Interlude] [Instrumental] [Instrumental Break] [Guitar Solo] [Breakdown] [Build-up] [Outro] [Silence] [End]

VOCAL PERFORMANCE: [Whispered] [Spoken Word] [Belted] [Falsetto] [Powerful] [Soulful] [Raspy] [Breathy] [Smooth] [Gritty] [Staccato] [Legato] [Vibrato] [Melismatic] [Harmonies] [Choir] [Harmonized Chorus]

DYNAMICS: [High Energy] [Low Energy] [Building Energy] [Explosive] [Emotional Climax] [Gradual swell] [Orchestral swell] [Quiet arrangement] [Falling tension] [Slow Down]

GENDER: [Female Vocals] [Male Vocals]

ATMOSPHERE: [Melancholic] [Euphoric] [Nostalgic] [Aggressive] [Dreamy] [Intimate] [Dark Atmosphere]

SFX: [Vinyl Crackle] [Rain] [Applause] [Static] [Thunder]

Put tags in BOTH style field AND lyrics for reinforcement. Keep to 5-8 tags per section max — too many confuses the AI. Don't contradict yourself ([Calm] + [Aggressive] in same section).

Custom Mode

  • Always use Custom Mode for serious work (separate Style + Lyrics)
  • Lyrics field limit: ~3,000 chars (~40-60 lines)
  • Always add structural tags — without them Suno defaults to flat verse/chorus/verse with no emotional arc
  • This Skill does not run Suno. The user pastes the two fields themselves.

7. Phonetic Tricks for AI Singers

AI vocalists don't read — they pronounce. Help them:

PHONETIC RESPELLING:

  • Spell words as they SOUND: "through" -> "thru"
  • Proper nouns are highest failure rate — test early
  • "Nous" -> "Noose" (forces correct pronunciation)
  • Hyphenate to guide syllables: "Re-search", "bio-engineering"

DELIVERY CONTROL:

  • ALL CAPS = louder, more intense
  • Vowel extension: "lo-o-o-ove" = sustained/melisma
  • Ellipses: "I... need... you" = dramatic pauses
  • Hyphenated stretch: "ne-e-ed" = emotional stretch

ALWAYS:

  • Spell out numbers: "24/7" -> "twenty four seven"
  • Space acronyms: "AI" -> "A I" or "A-I"
  • Test proper nouns/unusual words in a short 30-second clip first
  • Once generated, pronunciation is baked in — fix in lyrics BEFORE

中文歌词:不要为了迁就英文发音规则把句子改成英文;需要时用拼音或空格提示专有名词。


8. Workflow

  1. Write the concept/hook first — what's the emotional core?
  2. If adapting, map the original structure (syllables, rhyme, stress)
  3. Generate raw material — brainstorm freely before structuring
  4. Draft lyrics into the structure
  5. Read/sing aloud — catch stumbles, fix meter
  6. Build the Suno style description — paint the dynamic journey
  7. Add metatags to lyrics for performance direction
  8. Tell the user to generate 3–5 takes in Suno Custom Mode
  9. Pick the best, use Extend/Continue in Suno to build on promising sections
  10. If something great happens by accident, keep it

EXPECT: ~3-5 generations per 1 good result. Revision is normal. Style can drift in extensions — restate genre/mood when extending.


9. Lessons Learned

  • Describing the dynamic ARC in the style field matters way more than just listing genres. "Whisper to roar to whisper" gives Suno a performance map.
  • Keeping some original lines intact in a parody adds recognizability and emotional weight — the audience feels the ghost of the original.
  • The bridge slot in a song is where you can transform imagery. Swap the original's specific references for your theme's metaphors while keeping the emotional function (reflection, shift, revelation).
  • Monosyllabic word swaps in hooks/tags are the cleanest way to maintain rhythm while changing meaning.
  • A strong vocal persona description in the style field makes a bigger difference than any single metatag.
  • Don't be precious about rules. If a line breaks meter but hits harder, keep it. The feeling is what matters. Craft serves art, not the other way around.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.