OpenClaw Video Creation Process: Reducing Automation to 80% with Improved Quality

A developer has shared their refined OpenClaw workflow for animated video creation, achieving significant quality improvements by reducing automation to 80% and implementing better prompt engineering techniques.
Key Process Improvements
The developer spent a week refining their bots and achieved noticeable quality improvements in their video output. The core changes include:
- Working with a script agent to refine prompts multiple times, resulting in deeper story structure
- Each scene now contains multiple 4-8 second clips
- Improved clip agent prompt template with specific sections: Description (what happens visually), Emotion (character emotions), Characters (who are in the clip), Setup (setup used in the clip, only 1 per clip), Image Prompt (explain the first frame), and Video Prompt (with camera, 1-2 dialogue only)
- Using a quality agent to double-check prompts contain all necessary information
- Generating at least 2 clips per video prompt to account for VEO 3 hallucinations
- Pre-generating environment and outfits for characters to maintain scene setup and appearance consistency
- Setup agent creates new environments if they don't exist
Manual Post-Processing Steps
The remaining 20% manual work includes:
- Selecting which clip videos to add to CapCut
- Redoing clips with low quality (about 10% of clips)
- Adding text and scene transitions
Story Prompt Structure
The developer shared their story prompt template for generating content:
Act as a professional Pixar and Disney children's story writer. Write a 15-minute emotional story for children (age 5–12). Requirements: - Focus on humans only (no fantasy creatures) - No dialogue (narration only) - Strong emotional storytelling like Pixar - Include a meaningful life lesson about family, emotions, or growing up. - No complex actions, mainly characters talk to each others Story Structure: 1. Beginning 2. Change 3. Conflict 4. Low Point 5. Growth 6. Ending | Stage | Emotion | | --------- | ---------------- | | Beginning | Comfortable | | Change | Jealous / Fear | | Conflict | Angry / Confused | | Low Point | Sad / Guilty | | Growth | Understanding | | Ending | Warm / Happy | Story style: - Warm, realistic family setting - Emotional but simple (easy to animate) - Focus on facial expressions, actions, and small moments Only Use the characters in the context provided in "Jack's Family.txt" Only Use the setup provided in "Jack Family House Setup.txt", "other_setups.txt", and "school_setups.txt" Topic: {TOPIC} Output format: - Title - Full story (narration only, no dialogue)This approach demonstrates how strategic manual intervention combined with refined automation can produce higher quality AI-generated video content.
📖 Read the full source: r/openclaw
👀 See Also

OpenClaw + Claude Code/Codex in tandem: a real-world best-of-both-worlds example
A practical architecture for using Claude Code/Codex to build and OpenClaw to run a lead generation and outreach engine. Specific tool choice, cost breakdown, and agent design.

Developer Reports AI Coding Challenges: Design Decisions and Real-User Debugging
A developer building an iOS app with Claude Code for 5 months reports that while the AI can generate functional code easily, making design decisions and debugging issues that only appear with real users are the most difficult parts. The app has 220k lines and real users are testing it.

Reducing AI Agent Context Bloat with Single Workspace Architecture
A developer shares how they reduced AI assistant startup context from 27,000 to 4,000 tokens by implementing a single workspace approach instead of complex agent swarms, using channel-level identity injection and segregated memory folders.

Developer builds anonymous love proposal app with Claude Code
A developer created BlushDrop, an anonymous love proposal platform with real-time tracking, using Claude Code to handle architecture, security, and deployment despite having no prior experience with Next.js or Supabase Realtime.