Building an automated video editing pipeline with OpenClaw MCP tools
Automated video editing pipeline implementation
A developer created an OpenClaw skill that connects to a video editor to automate processing of recorded content like streams, talking head videos, and tutorials. The skill handles converting long recordings into shorts and clips for social media, addressing a problem where manual editing previously took 3-4 hours per recording.
Technical approaches for long-running tasks
The developer implemented three patterns to handle video processing in an MCP context where operations can't complete within typical timeout limits:
- WebSocket polling with HTTP fallback: The skill opens a socket connection for real-time progress events and falls back to HTTP polling if the socket fails
- Webhook support: For fire-and-forget workflows, users can pass a callback URL, and the server sends a signed project.completed event when done
- Watch mode with state: The skill stores a watchers.json file locally that tracks which channel URLs to monitor and which video IDs have already been processed
Key implementation insights
Spend control: When agents can spend money on your behalf, guardrails are essential. The developer built a three-tier spend policy with per-action limits and caps.
Presets for configuration: Instead of exposing many configuration fields, the skill defines 8 named presets. Agents can simply say "use the podcast preset" to apply complex configurations.
Next_steps in tool responses: After operations like downloads complete, responses include hints like "generate thumbnails" that agents naturally pick up and suggest without prompting.
Watch mode pattern for monitoring workflows
The watch mode pattern follows this structure:
- User registers a source like a YouTube channel URL
- Skill stores it locally with configuration (like daily caps)
- On each "check," the skill lists videos from the source and processes new ones
This pattern works for any "monitor a source and process items" workflow, including RSS feeds or Dropbox folders.
Performance metrics
- Processed about 15 recordings
- Average turnaround: 4 minutes for a 20-minute video
- Each processed video returns with a jump-cut edit, subtitles, and 20-30 shorts
The skill is available as @web2labs/studio on ClawHub with public source code on GitHub, using Web2Labs Studio as the backend.
📖 Read the full source: r/openclaw
👀 See Also
OpenClaw's Bub AI agent struggles with delegation, burns $20 in 15 minutes during mobile site optimization
During QA for Driftwatch V3, the OpenClaw bot Bub burned $20 in 15 minutes by failing to delegate tasks properly. The developer discovered detailed spec templates reduce costs, while mobile retrofitting added unexpected time and expense.
Building an AI Receptionist for a Mechanic Shop: RAG Pipeline and Voice Integration
A developer built a custom AI receptionist named Axle for a luxury mechanic shop using a RAG pipeline with MongoDB Atlas and Voyage AI embeddings, then connected it to a real phone line via Vapi with FastAPI and Ngrok.
Debugging a Tiny AI Agent on an Old Nokia Phone: 18 Attempts to Success
A developer documented 18 failed attempts to run Picobot, a ~12 MB AI agent, on an old Nokia phone via Termux, testing free models, OpenRouter, and Groq before settling on Google's Gemini Flash API for a fast, reliable setup.
OpenClaw Orchestrator Routing Issues: When Delegation Fails
A developer reports their OpenClaw main orchestrator incorrectly handles requests itself about 40-50% of the time instead of routing to specialist sub-agents, despite using an explicit routing table and delegation rules. The setup includes 7 specialist agents for services like Gmail, Todoist, Notion, and weather.