side-quests

What This Skill Does

Side-quests is an OpenClaw agent skill designed for high-level creative synthesis. It bridges the gap between raw technical information and conceptual retention by generating three distinct creative artifacts from a single technical insight: a Suno-ready song, a visual concept guide, and a full TED-style talk. The core philosophy is that context without action is paralysis; by forcing the AI to interpret a concept through music, visual metaphor, and persuasive narrative, the skill ensures the user internalizes the 'why' behind complex technical decisions.

Installation

To install this skill, run the following command in your OpenClaw environment: openclaw install leegitw/side-quests

Use Cases

This skill is best utilized when you have reached a significant technical milestone or realized a breakthrough in your project.

1. Technical Onboarding: Convert complex architectural diagrams or system logic into a TED talk to onboard new team members effectively.
2. Conceptual Reinforcement: Transform abstract patterns or algorithms into a song and visual guide for easier memory retention during long-term development.
3. Post-Mortem Reflection: Use the synthesis process to document why a specific technical approach succeeded, making the lessons learned actionable for future iterations.

Example Prompts

1. '/sq Explain the reasoning behind our migration to the new event-driven architecture'
2. '/sq Turn the technical constraints of the current database schema into a song and visual concept'
3. '/sq Create a side quest synthesis based on the troubleshooting process we just completed for the API latency issue'

Tips & Limitations

• Context is Key: The skill performs best when there is substantial depth in the conversation. Avoid using it on surface-level topics as the synthesis will lack the necessary weight.
• Modularity: If you only need one specific output, use the individual component skills (/song, /vc, or /ted) instead of the full /sq command.
• Preparation: Ensure your primary work is documented or saved before running the skill, as it shifts the agent into a creative, non-technical context which may deviate from the current task execution.