ipollowork-video-voiceover
Add or revise scene-bound narration in an active iPolloWork Video Studio project using its selected voice, media actions, timing contract, and final validation.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/ipollowork-video-voiceover && cp -r /tmp/ipollowork-video-voiceover/.agents/skills/ipollowork-video-voiceover ~/.claude/skills/ipollowork-video-voiceoverSKILL.md
# iPolloWork Video Voiceover Use this Skill only when narration helps the confirmed brief or the user explicitly requests it. The Video Studio and its media services remain core iPolloWork capabilities and do not depend on this Skill being installed. ## Workflow 1. Read the active session's exact video project, `voiceover.json`, and injected voiceover contract before synthesizing anything. 2. Build narration per visual scene from that scene's visible text in reading order. Do not paraphrase or narrate another scene. 3. Use only the media action and selected voice supplied by iPolloWork. Do not substitute a generic speech tool or another provider. 4. Treat returned duration and timing data as authoritative. Extend the current scene and shift every later scene, transition, caption, audio start, and animation timestamp when narration runs longer. 5. Keep one immutable narration asset and one timeline audio node per narrated scene; remove only obsolete narration references, never music or sound effects. 6. Run both the HyperFrames project check and the active session's voiceover timeline validation before finishing. If no valid voice selection exists, continue without narration instead of inventing a voice or blocking visual video work.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.