Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Transform technical insights into Suno-ready songs with lyrics, style tags, and emotional arc
Transform technical insights into Suno-ready songs with lyrics, style tags, and emotional arc
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Transform technical conversations and insights into songs formatted for Suno.ai. Creates lyrics with emotional arc that mirrors the technical journey, complete with style tags and section markers. Trigger: ๆ็คบๅผๅบ (explicit invocation) or when deep technical insight emerges Core insight: "Creation forces synthesis. Making a song about a concept reveals gaps that passive understanding cannot."
openclaw install leegitw/insight-song Dependencies: None (standalone creative skill) Data handling: This skill synthesizes content from user-supplied input or the current conversation context (default). It does NOT read files from the workspace or access project artifacts directly. Results are returned to the invoking agent, who decides how to use them.
Technical insights fade with context compression. Songs provide audio reinforcement that makes concepts memorable and transferable. This skill: Synthesizes technical conversations into narrative arc Transforms abstract concepts into singable lyrics with visual imagery Formats output for direct use with Suno.ai The insight: Technical principles conveyed through metaphor and emotional arc stick better than documentation alone.
/song [topic]
ArgumentRequiredDescriptiontopicNoTopic focus (default: synthesize current conversation)
Before creating a song, ensure: Sufficient conversation depth โ Surface-level summaries don't make good songs Clear narrative arc โ Problem โ Discovery โ Solution โ Impact Main work documented โ Save current progress first if mid-task
You must be able to answer: QuestionWhat It MeansCore insight?Not "we talked about X" but "we discovered X solves Y"Problem solved?The pain point, not just the topicWhy, not just what?The reasoning, not just the outcomeSubstantial depth?Teaches something new, not standard practice
Surface-level summary of conversation Don't understand why a decision was made Insight is just standard practice No clear narrative arc Vague lyrics that could apply to anything
## Song **Title**: [Song Name] **Suno.ai Style Tags**: [300-500 characters describing musical style, mood, instrumentation] [Verse 1] [Lyrics conveying the problem/pain] [Chorus] [Core message, repeatable, memorable] [Verse 2] [Discovery/insight] [Bridge] [Technical depth through metaphor] [Chorus] [Outro] [Resolution/call to action]
RuleDescriptionTell a storyBeginning, middle, end with clear arcTechnical but singableDon't sacrifice accuracy for rhymeVisual imageryDesigned for audio+visual reinforcementEmotional arcMatches the technical journeyNO literal specificsUse metaphor and symbol, not file names or metricsNO artist namesExtract essence, not references
Bad (too literal): We fixed the bug in handler.go The timeout was set to 300 Good (metaphorical): Three in the morning, the logs are all silent System's on fire but the metrics don't know Building in darkness, no baseline to measure Can't debug what you've never seen before
Read full conversation context Identify key decisions, "aha" moments Extract core insight or pattern
ElementQuestionProblemWhat was broken/painful?DiscoveryWhat did we learn?SolutionWhat pattern emerged?ImpactWhy does this matter?
Structure (flexible): Intro: Set the problem/context Verse 1: The pain/current state Verse 2: The discovery/insight Bridge: Technical depth through metaphor Chorus: Core message (repeatable, memorable) Outro: Resolution/call to action
Add title Write 300-500 character style tags Add section markers: [Verse 1], [Chorus], [Bridge], etc.
Context: Discovered reproduce-to-debug problem. Introduced Bootstrap โ Learn โ Enforce phases. Narrative arc: Problem: Debugging without reproduction is impossible Discovery: Greenfield systems don't know what "normal" is Solution: Bootstrap โ Learn โ Enforce phases Impact: Debug with sight instead of in darkness
Title: Bootstrap Before You Break Suno.ai Style Tags: Atmospheric indie folk with building intensity, finger-picked acoustic guitar opening, gradually adding warm synth pads and driving drums, introspective male vocals with occasional harmonies, dynamic shifts between quiet verses and powerful choruses, ethereal reverb on bridge section, cinematic crescendo finale [Verse 1] Three in the morning, the logs are all silent System's on fire but the metrics don't know Building in darkness, no baseline to measure Can't debug what you've never seen before [Chorus] Bootstrap before you break Learn the patterns while you wait Enforce what the data shows Now you see where the failure goes [Verse 2] Started collecting every signal Cast the net wide, caught it all Fourteen days of patient watching Now we know what normal's called
Layer: Creative Depends on: None (standalone) Used by: side-quests (combo skill) Complements: visual-concept, ted-talk
ConditionBehaviorInsufficient contextAsk clarifying questions firstNo clear narrative arcDecline, explain what's missingSurface-level topicSuggest deeper exploration first
Input sources: User-supplied context (if provided) Current conversation context (default) What this skill does NOT do: Read files from the workspace Access project artifacts directly Send data to external services Call external APIs Output behavior: This skill returns the song directly to the invoking agent. The agent can then display, save, or pass the result to another skill as needed. Provenance note: This skill is developed by Live Neon (https://github.com/live-neon/skills) and published to ClawHub under the leegitw account. Both refer to the same maintainer.
Can explain core insight in one sentence Understand why, not just what Song tells story with beginning, middle, end Emotional arc matches technical journey No literal specifics (file names, metrics, etc.) Style tags are 300-500 characters Section markers present: [Verse], [Chorus], [Bridge], etc.
/song synthesizes input or conversation into Suno-ready format Output includes title, 300-500 char style tags, sectioned lyrics Lyrics convey technical insight through metaphor Emotional arc matches the technical journey Result returned to invoking agent Part of the Live Neon Creative Suite.
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.