Communitygithub.com

EvovexAI/EvoFlow

在 Plan 協作模式中按照結構化流程完成短片影片製作:先詢問用戶需求,確認後直接用 plan 工具將所有工種(編劇、視覺策劃、美術、導演、後期)納入步驟規劃,並依序執行。

EvoFlow 是什麼?

這個技能專為需要在 Plan 協作模式下進行視覺/影片產出的任務而設計,例如生成圖片、短片、配音和字幕。它提供了一個完整的結構化工作流程,從收集用戶需求開始,然後使用 `plan` 工具建立一個包含所有媒體製作角色的逐步計畫。這些角色包括編劇、視覺策劃、美術、影片導演和後期製作,每個角色都負責特定的輸出,例如腳本、提示詞、關鍵影格和最終影片。此技能支援多個供應商,包括用於圖片生成的 Seedream 和用於影片生成的 Seedance,並透過環境變數進行設定。其核心優勢是將整個影片製作流程自動化,並在 Plan 模式中確保所有步驟按順序執行與驗收,從而避免手動委派和錯誤。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/EvovexAI/EvoFlow/tree/HEAD/skills/public/plan-video-production

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

Plan 影片製作技能

適用範圍

前提:當前已開啟 Plan 協作(scenario(activate, plan) 已啟用),需要進行包含視覺/影片產出(生圖、短片、配音、字幕)的任務。

廠商選擇:生圖請參考 byted-ark-seedream-skill;生影片請參考 media-production 腳本(火山 Seedance)。其他廠商請見 agnes-media-generation / wan-media-generation / kling-media-generation。

憑證(環境變數)

在 設定 → 環境變數 新增技能要求的 KEY=VALUE(例如 VOLCENGINE_API_KEY / ARK_API_KEY)。也可在 設定 → 模型 → 創意媒體 填入其他廠商 Key。

能力常用 KEY技能
生圖VOLCENGINE_API_KEY / ARK_API_KEYbyted-ark-seedream-skill
生影片同上media-production
AgnesAGNES_API_KEYagnes-media-generation

核心變更:所有媒體工種(編劇、視覺策劃、美術、導演、後期)全部在 plan(goal, steps[]) 的 steps 中透過 assigned_agent 指定,plan 儲存後用戶確認即進入 executing 並依序執行,不再在 plan 之外單獨委派 subagent。

工作流程

用戶表達需求
     ↓
詢問並確認用戶需求(主題、時長、風格、畫幅等)
     ↓
直接用 plan(goal, steps[]) 規劃
  step 1: media-screenwriter  — 劇本/分鏡/口播
  step 2: media-visual-planner — 生圖 prompt
  step 3: media-artist        — 生成關鍵影格
  step 4: media-video-director — 出片 + 原生配音
  step 5: media-post          — 硬字幕
     ↓
用戶確認 → 執行(依序,每步驗收)

操作步驟

第一步:詢問用戶需求

主動向用戶收集以下資訊:

問題範例
影片主題/產品/內容是什麼?新款智慧手錶宣傳
目標時長?15 秒 / 30 秒
視覺風格?科技感 / 溫暖 / 國風
畫幅比例?16:9 / 9:16 直式
口播文案方向?功能亮點 + 品牌 slogan
是否有參考素材?參考圖 / 競品影片

第二步:確認後直接 plan

用戶確認需求後,直接用 plan 工具將所有步驟寫入結構化計畫:

plan(
  goal="製作一支 15 秒產品宣傳短片,主題:xxx,風格:xxx",
  steps=[
    {
      "step_id": 1,
      "description": "編劇撰寫 production brief,包含 logline、分鏡、口播稿",
      "assigned_agent": "media-screenwriter",
      "expected_output": "outputs/production-brief.md",
      "acceptance_criteria": "包含 User intent、logline、visual style、shot list、narration script"
    },
    {
      "step_id": 2,
      "description": "視覺策劃將分鏡轉為生圖 prompt",
      "assigned_agent": "media-visual-planner",
      "expected_output": "outputs/shot-prompts.json",
      "depends_on": [1]
    },
    {
      "step_id": 3,
      "description": "美術生成首影格關鍵影格圖片",
      "assigned_agent": "media-artist",
      "expected_output": "outputs 內 PNG 關鍵影格",
      "depends_on": [2]
    },
    {
      "step_id": 4,
      "description": "影片導演生成帶原生配音的 MP4",
      "assigned_agent": "media-video-director",
      "expected_output": "outputs/*.mp4",
      "depends_on": [3]
    },
    {
      "step_id": 5,
      "description": "後期加硬字幕,交付最終 MP4",
      "assigned_agent": "media-post",
      "expected_output": "outputs/*-subtitled.mp4",
      "depends_on": [4]
    }
  ],
  flowchart_mermaid="..."
)

第三步:用戶確認執行

plan 儲存後用戶確認「開始執行」,進入 executing 階段,各步驟按依賴順序依序執行,每步完成後主 Agent 驗收產物再進入下一步。

媒體子智能體清單

assigned_agent職責核心工具
media-screenwriter寫劇本、分鏡、口播稿read_file, write_to_file
media-visual-planner寫生圖 promptread_file, write_to_file
media-artistSeedream 生圖(jimeng)read_file, terminal → scripts/image_generate.py
media-video-directorSeedance 圖生影片 + 原生配音read_file, terminal → scripts/video_generate.py, task_wait.py
media-postSRT 字幕 + ffmpeg 硬字幕read_file, terminal → scripts/subtitle_build.py, subtitle_burn.py

注意:不要把 media-voice-director 放入步驟——Seedance 已原生帶聲(generate_audio=true 預設開啟)。

技術棧

腳本目錄:skills/public/media-production/scripts/(須先讀 media-production skill)

能力腳本provider
生圖image_generate.pyjimeng(火山方舟 Seedream)
生影片video_generate.py + task_wait.pyjimeng(火山方舟 Seedance,預設帶聲)
字幕subtitle_build.py + subtitle_burn.py本地 ffmpeg

失敗處理:jimeng 失敗後禁止自動切換 wan/kling,提示用戶開啟 Ark 模型接入點。相同參數失敗最多重試 1 次。

常見錯誤

  • 在 plan 模式下主會話直接執行 image_generate.py → 應由 plan 步驟裡的 media-artist 等工種執行
  • 在 plan 步驟外單獨委派 subagent → 所有工種應寫在 plan steps 的 assigned_agent 中
  • 跳過 task_wait.py → 影片生成未完成就交付
  • 預設管道仍委派 media-voice-director → Seedance 已原生帶聲,多餘

Individual skills in this repo

This repo contains 15 individual skills — each has its own dedicated page.

EvovexAI/EvoFlow

Add captions to a talking-head video. ONE catalog (CATALOG.md) of 32 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions (anchor/ordnance/terminal/neonsign/stardust/stomp/scoreboard/transit/vhs/arcade/dossier/laser/thunder/hologram/biolume/aurora/spectrum/papercut/popup/chalkboard/graffiti/brush/inkwater/ransom/lastpage/nightcity — e.g. a glyph-decode climax, a neon sign WRITTEN stroke by stroke, or the quiet `anchor` rail default). Route by identity, never by mode. Trigger on "captions/subtitles", "embed/cinematic captions", "VFX captions", "炸/特效/酷炫字幕", a named identity, or top-tier motion-graphics asks. Embedding every word is wrong for most talking-head content — `anchor` is the verbatim default. Pipeline: transcription → hyperframes remove-background matting → HTML render → ffmpeg overlay. Requires hyperframes and a single-subject clip.

EvovexAI/EvoFlow

The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a website, a topic explainer, a GitHub PR, existing footage, a short motion graphic, or a Remotion port — prefer it (see /hyperframes); use this only as the general fallback when none fit.

EvovexAI/EvoFlow

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). HyperFrames-native: single paused timeline, seek-safe, deterministic.

EvovexAI/EvoFlow

HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (`hyperframes lambda deploy / render / progress / destroy / policies`).

EvovexAI/EvoFlow

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

EvovexAI/EvoFlow

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

EvovexAI/EvoFlow

Audio and media assets for HyperFrames compositions, produced by one shared audio engine (`scripts/audio.mjs`) — multi-provider TTS (HeyGen / ElevenLabs / Kokoro local), background music + sound effects (HeyGen audio-library retrieval by default, with local Lyria / MusicGen BGM generation and a bundled SFX library as the no-credential fallback), Whisper transcription, background removal, and caption authoring. Use for voiceover / TTS, BGM, SFX / sound effects, transcription, captions / subtitles / lyrics / karaoke / per-word styling, voice + provider selection, and music-mood prompting.

EvovexAI/EvoFlow

Install and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add, installing a block or component, wiring an installed item into index.html, or working with hyperframes.json. Covers the add command, install locations, block sub-composition wiring, component snippet merging, registry discovery, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

EvovexAI/EvoFlow

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

EvovexAI/EvoFlow

Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s and up to ~30s, with no narration arc, voice-over, or live-action subject. Can render to MP4 or transparent overlay. Not for longer, multi-scene, narrated, or brand-reel pieces (use general-video), narrated website videos (general-video), topic explainers (faceless-explainer), product promos (product-launch-video), PR videos (pr-to-video), or captions on existing footage (embedded-captions). When unsure whether it's a quick motion-first piece or a longer / narrated treatment, see /hyperframes.

EvovexAI/EvoFlow

Use when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting. The music drives everything: one analyzer reads it once, the orchestrator lays out the frames and fills a per-frame plan, and one sub-agent builds each frame. Typography and templates are the floor — a complete video needs zero assets — but any images or videos the user supplies are cut into the frames on the same beat grid (beat-cut / ken-burns). The genre (lyric video, slideshow, kinetic promo) falls out of the per-frame choices; the pipeline never branches on it.

EvovexAI/EvoFlow

turn a product or marketing URL, pasted script, or brief into a product launch video, including SaaS promos, feature reveals, app launches, company promos, and product marketing videos. Use this skill when the user wants to market, launch, promote, or reveal a product. Do not use it for general non-launch website tours, non-product topic explainers, GitHub pull requests, captioning existing footage, or short unnarrated motion graphics. If the intent is unclear, route through /hyperframes first. This is the new shot-sequence architecture: every visual frame is authored as a time-coded shot sequence picked from a menu of golden blueprints, so frames develop over their full duration instead of freezing after entrance.

EvovexAI/EvoFlow

turn a GitHub pull request (a PR URL like github.com/<owner>/<repo>/pull/<N>, an <owner>/<repo>#<N> ref, or 'this PR' in a checked-out repo) into a code-change explainer video, up to ~3 min (sweet spot 30-90s) — changelog, feature reveal, fix, or refactor walkthrough, rendered from the diff / commits / files. The input is a CODE CHANGE read via the gh CLI; there is no website capture. Use this skill for a GitHub PR. Do not use it for a product launch/promo (use /product-launch-video), a tour of a real website (use /general-video), a topic explainer with no PR (use /faceless-explainer), captions on existing footage (use /embedded-captions), or a short unnarrated motion graphic (use /motion-graphics). If the intent is unclear, route through /hyperframes first.

EvovexAI/EvoFlow

Port an existing Remotion (React) composition to HyperFrames HTML. Use ONLY when the user explicitly asks to port/convert/migrate/translate a Remotion source. Do NOT use: (a) authoring a new HyperFrames composition; (b) Remotion mentioned in passing; (c) Remotion code shared as reference only; (d) "same video as my Remotion one" without explicit migrate request — treat as fresh build. Doubt → `/general-video`. One-way, Remotion-only: no reverse export (HyperFrames→Remotion or any framework), no non-Remotion source (After Effects, Framer Motion, plain React/CSS) → out of scope, re-create via `/general-video`. Flags unsupported patterns (useState, useEffect, async calculateMetadata, third-party React libs, `@remotion/lambda`) and recommends runtime interop over lossy translation. Unsure whether to port vs. build fresh, or only a passing Remotion mention? → /hyperframes.

EvovexAI/EvoFlow

本地文字转语音,使用sherpa-onnx(离线,无需云端)。当需要离线语音合成时使用。

相關技能