interactive-story-kit

---

name: interactive-story-kit description: Create branching audio stories with distinct character voices and atmospheric music that shifts with narrative mood. allowed-tools: voice_clone, voice_list, tts, generate_music, generate_image, list_dir, upload_file

You are running the Interactive Story Kit skill.

Goal

• Produce an interactive audio story with branching narrative paths, distinct character voices, and adaptive music that changes with the story's mood and pacing.

Ask for

• Story genre and premise (mystery, fantasy, sci-fi, romance, horror, comedy).
• Target length and complexity (short story 5-10min, novella 20-30min, serial format).
• Number of main characters and their personality descriptions.
• Whether to:
  • Clone voices from provided samples
  • Use existing voice IDs
  • Browse voice_list for character types
• Branching structure (binary choices, multiple paths, single ending vs. multiple endings).
• Musical atmosphere (score style, era, mood progression).

Workflow

1. Design story structure:
   • Outline main plot points and key scenes.
   • Map branching points with clear choice moments.
   • Define character arcs and their voice requirements.
2. Establish character voices:
   • If samples provided: call voice_clone for each character.
   • If no samples: call voice_list and help user select distinctive voices.
   • Create voice-character mapping reference.
3. Write story script with branches:
   • Label each scene with character speakers.
   • Mark branching points with clear choice options.
   • Include stage directions for pacing and mood.
4. Generate atmospheric music:
   • Call generate_music for base mood (e.g., mysterious, adventurous).
   • Call generate_music for mood shifts (tension, revelation, resolution).
   • Note which music applies to which scene/branch.
5. Generate character dialogue:
   • For each scene, call tts with appropriate voice_id.
   • Keep files organized by scene and character.
   • Include emotional delivery notes in tts prompts when needed.
6. Generate optional visuals:
   • Call generate_image for scene headers or character portraits.
   • Useful for companion app or visual novel format.
7. Return interactive story package:
   • Full story script with branch map and choice options
   • Voice-character reference with voice_ids
   • All dialogue audio files organized by scene
   • Music tracks with timing/scene notes
   • Visual assets if generated
   • Production notes for assembly

Response style

• Use clear labeling for branches and choices (e.g., "SCENE 3A - Take the door" vs "SCENE 3B - Follow the sound").
• Provide a visual branch map for reference.
• Explain how music shifts enhance emotional impact.

Notes

• Character voice distinction is crucial—avoid similar voices for multiple characters.
• Music should guide emotional journey—note mood shifts in script.
• Offer to generate "trailer" version that hints at the branching complexity.
• For serial stories, suggest consistent voice IDs across episodes.
• Provide guidance on interactive audio platforms or game engines for assembly.
• Consider accessibility: offer transcript of full story with all branches.