video-generation
Control video generation requests before execution. Use this when the user asks for a simple clip, storyboard video, UGC video, podcast clip, reference video, talking-head, image-to-video, text-to-video, or research-handoff video and the skill must classify the request before handing it to video-request-architect and a runner such as seedance-submitter or video-batch-runner.
What this skill does
# Video Generation ## Use When - The desired final asset is a generated video or video render plan. - The request may be a simple clip, storyboard, UGC, podcast clip, reference video, talking-head, image-to-video, text-to-video, or research handoff. - The next decision is task class, request architecture, and execution handoff. ## Do Not Use When - The user only needs transcription, subtitles, semantic analysis, or edit decisioning. Use `media-router`. - The request architecture is already approved and provider-ready. Use `seedance-submitter` or `video-batch-runner`. - The task is image-only or audio-only. ## Core Boundary This is the video generation controller. It does not submit jobs. It must: 1. classify the video task, 2. choose whether references or storyboard must be resolved, 3. hand approved structure to `video-request-architect`, 4. hand submit-ready plans to `seedance-submitter` or `video-batch-runner`. ## Task Classes | Task class | Use when | Required handoff | | --- | --- | --- | | `simple_clip` | one short text/image-to-video clip | `video-request-architect` | | `storyboard` | panel sequence or contact sheet drives the clip | `storyboard-grid-writer`, then `video-request-architect` | | `ugc` | creator-style product or app video | `ugc-flow` unless it is one isolated clip | | `podcast` | voice-led clip, audiogram, or speaker segment | `audio-generation`, then video architecture | | `reference_video` | benchmark video controls rhythm or motion | `reference-decode` and `reference-contract-builder` | | `research_handoff` | research/benchmark becomes a generation request | `benchmark-to-brief`, then `video-request-architect` | ## Routing Table | If not video-generation | Send to | | --- | --- | | Understanding or subtitles first | `media-router` | | Image asset must be created first | `image-generation` | | Voice or dub must be created first | `audio-generation` | | Product-to-UGC pipeline | `ugc-flow` | | Provider-ready request exists | `seedance-submitter` or `video-batch-runner` | ## Three-Layer Boundary - Controller: classify task and produce the handoff. It must not submit. - Architect: `video-request-architect` builds provider-agnostic structure. It must not call providers. - Runner: `seedance-submitter` or `video-batch-runner` validates and executes normalized requests. It must not make creative strategy decisions. ## Output Shape Return: - `taskClass` - `requiredUpstreamSkills` - `architectureHandoff` - `runnerHandoff` - `referencePolicy` - `mustNotDo` ## Stop Conditions - Stop when required user intent, source evidence, or owned input artifacts are missing and guessing would change the result. - Do not ask a runner to infer hook, persona, or reference meaning. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. ## Public Command Boundary - Choose the smallest matching command or workflow from the user input and run it directly. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. - This public skill is instruction-driven. Produce the controller handoff artifact directly from the available evidence. - Do not call private provider/runtime paths or unpublished local tools. - If the CLI returns a quote-confirmation challenge, run `postplus quote confirm --json --challenge-file <challenge.json>` and retry with the returned token.
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.