side-quests (遊)

Full creative synthesis that combines all three creative artifacts from a single technical insight: a Suno-ready song, a visual concept guide, and a full TED talk.

Trigger: 明示呼出 (explicit invocation) or when deep technical insight emerges

Core insight: "Context without action is paralysis. Action without context is chaos. Side quests are context made actionable through creative synthesis."

Installation

openclaw install leegitw/side-quests

Dependencies: None required, but works with component skills:

• leegitw/insight-song — Song component (can be used standalone)
• leegitw/visual-concept — Visual guide component (can be used standalone)
• leegitw/ted-talk — TED talk component (can be used standalone)

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.

What This Solves

Technical insights fade with context compression. Multi-format creative synthesis provides reinforcement through multiple channels:

1. Song — Audio reinforcement, emotional arc
2. Visual concept — Symbolic representation, visual metaphor
3. TED talk — Comprehensive narrative, concrete examples

The insight: Creation forces synthesis. Making creative artifacts about a concept reveals gaps that passive understanding cannot. Audio + visual + narrative = deeper learning.

Usage

/sq [topic]

Or use individual components:

/song [topic]    # Just the song
/vc [topic]      # Just the visual concept
/ted [topic]     # Just the TED talk

Arguments

Pre-Requisites

Before creating a side quest, ensure:

1. Sufficient conversation depth — Surface-level summaries don't make good artifacts
2. Clear narrative arc — Problem → Discovery → Solution → Impact
3. Main work documented — Save current progress first if mid-task

Context Understanding Checklist

You must be able to answer:

Red Flags (Don't Create)

• Surface-level summary of conversation
• Don't understand why a decision was made
• Insight is just standard practice
• No clear narrative arc
• Would be padding with generic content

Output Structure

Each side quest produces a single markdown file with three sections:

1. Song (Suno.ai Format)

## Song

**Title**: [Song Name]