mirror of
https://github.com/bytedance/deer-flow.git
synced 2026-06-10 09:25:57 +00:00
cd5bedaa74
* docs(spec): MiniMax integration for generation skills + new music skill Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(plan): MiniMax generation providers implementation plan Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(skills): add importlib loader + FakeResp for skill tests * test(skills): register loaded module in sys.modules; raise requests.HTTPError in FakeResp * feat(image-generation): add MiniMax provider with env auto-detect Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * refactor(image-generation): guard unknown provider, derive ref MIME, strengthen tests Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(video-generation): add MiniMax provider with async poll/download Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * refactor(video-generation): surface base_resp errors while polling; add timeout test * feat(podcast-generation): add MiniMax t2a_v2 provider with env auto-detect Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * refactor(podcast-generation): restore TTS credential guard; add volcengine + voice tests Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat(music-generation): new MiniMax music skill via skill-creator Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * refactor(music-generation): treat empty lyrics as absent; test no-audio-data path * refactor(skills): add request timeouts to MiniMax network calls Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Potential fix for pull request finding 'Explicit returns mixed with implicit (fall through) returns' Co-authored-by: Copilot Autofix powered by AI <223894421+github-code-quality[bot]@users.noreply.github.com> * fix(models): strip inconsistent user-message names for MiniMax chat DeerFlow middlewares tag user messages with provenance names (user-input, summary, loop_warning); langchain serializes them into the OpenAI-compatible payload and MiniMax rejects mismatched user-message names with "user name must be consistent (2013)". PatchedChatMiniMax now drops the per-message name from user-role messages. Point the config.example MiniMax models at PatchedChatMiniMax so they also get reasoning_content mapping. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(image-generation): MiniMax sends JSON prompt field, guard 1500-char limit MiniMax image-01 takes one text string capped at 1500 chars, but the skill was sending the whole structured JSON. The MiniMax provider now extracts the JSON `prompt` field (relying on prompt_optimizer to expand it) and fails fast with a clear error before calling the API when that field exceeds 1500 chars. Authoring stays provider-agnostic; Gemini still receives the full JSON. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(podcast-generation): per-provider TTS concurrency and retry/backoff Each TTS provider owns its concurrency internally — MiniMax runs single-threaded to reduce rate-limit failures, Volcengine keeps 4 workers — with automatic retry and backoff on transient HTTP and base_resp errors. No caller-facing concurrency knob. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(skills): address Copilot review comments on generation skills - video: add raise_for_status + timeout to the Gemini download/POST/poll calls so non-2xx responses surface as clear HTTP errors instead of JSON/KeyError or hangs - video: check the task Fail status before the generic base_resp check so the failure keeps its task_id context - video/image: create the output file parent directory before writing (matching music-generation) so nested output paths do not raise FileNotFoundError - music: require a non-empty prompt and fail fast with ValueError instead of sending an empty prompt to the API Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(scripts): reclaim dev ports across worktrees in make stop/dev All deer-flow worktrees (main checkout + linked worktrees) hardcode the same dev ports (8001/3000/2026), so a service started from any worktree must be reclaimable from another. stop_all now resolves the set of worktree roots (DEERFLOW_ROOTS) and treats a process as deer-flow-owned when its open files live under any of them. It also force-kills survivors on 2026 alongside 8001/3000, fixing `make dev` aborting on the nginx port preflight when a prior nginx lingered on 2026. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(view-image): hide the injected image-context message from the UI ViewImageMiddleware injects a HumanMessage (text + base64 images) so the vision model can see viewed images, but it was the only internal injector that set neither hide_from_ui nor a hidden name, so it leaked into the chat UI (and IM channels) as a user bubble reading "Here are the images you've viewed:". Mark it with additional_kwargs={"hide_from_ui": True}, matching todo/dynamic_context injections, which the frontend isHiddenFromUIMessage and the channel sender already honor. The model still receives the full content. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(minimax): mark M2.7 models as text-only (no vision) MiniMax M2.7 / M2.7-highspeed do not support vision; only M3 does. The provider config asserted vision support for M2.7 in four places. - config.example.yaml: 4 M2.7 entries -> supports_vision: false - backend/docs/CONFIGURATION.md: M2.7 + highspeed -> supports_vision: false - wizard: add LLMProvider.model_vision_overrides + extra_config_for() so selecting an M2.7 model writes supports_vision: false while M3 (default) keeps vision; wire it through setup_wizard.py - tests: M2.7-highspeed fixture -> supports_vision=False; add test_minimax_vision_is_per_model Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Willem Jiang <willem.jiang@gmail.com> Co-authored-by: Copilot Autofix powered by AI <223894421+github-code-quality[bot]@users.noreply.github.com>
152 lines
5.2 KiB
Markdown
152 lines
5.2 KiB
Markdown
---
|
|
name: video-generation
|
|
description: Use this skill when the user requests to generate, create, or imagine videos. Supports structured prompts and reference image for guided generation.
|
|
---
|
|
|
|
# Video Generation Skill
|
|
|
|
## Overview
|
|
|
|
This skill generates high-quality videos using structured prompts and a Python script. The workflow includes creating JSON-formatted prompts and executing video generation with optional reference image.
|
|
|
|
## Core Capabilities
|
|
|
|
- Create structured JSON prompts for AIGC video generation
|
|
- Support reference image as guidance or the first/last frame of the video
|
|
- Generate videos through automated Python script execution
|
|
|
|
## Workflow
|
|
|
|
### Step 1: Understand Requirements
|
|
|
|
When a user requests video generation, identify:
|
|
|
|
- Subject/content: What should be in the image
|
|
- Style preferences: Art style, mood, color palette
|
|
- Technical specs: Aspect ratio, composition, lighting
|
|
- Reference image: Any image to guide generation
|
|
- You don't need to check the folder under `/mnt/user-data`
|
|
|
|
### Step 2: Create Structured Prompt
|
|
|
|
Generate a structured JSON file in `/mnt/user-data/workspace/` with naming pattern: `{descriptive-name}.json`
|
|
|
|
### Step 3: Create Reference Image (Optional when image-generation skill is available)
|
|
|
|
Generate reference image for the video generation.
|
|
|
|
- If only 1 image is provided, use it as the guided frame of the video
|
|
|
|
### Step 3: Execute Generation
|
|
|
|
Call the Python script:
|
|
```bash
|
|
python /mnt/skills/public/video-generation/scripts/generate.py \
|
|
--prompt-file /mnt/user-data/workspace/prompt-file.json \
|
|
--reference-images /path/to/ref1.jpg \
|
|
--output-file /mnt/user-data/outputs/generated-video.mp4 \
|
|
--aspect-ratio 16:9
|
|
```
|
|
|
|
Parameters:
|
|
|
|
- `--prompt-file`: Absolute path to JSON prompt file (required)
|
|
- `--reference-images`: Absolute paths to reference image (optional)
|
|
- `--output-file`: Absolute path to output image file (required)
|
|
- `--aspect-ratio`: Aspect ratio of the generated image (optional, default: 16:9)
|
|
|
|
[!NOTE]
|
|
Do NOT read the python file, instead just call it with the parameters.
|
|
|
|
## Video Generation Example
|
|
|
|
User request: "Generate a short video clip depicting the opening scene from "The Chronicles of Narnia: The Lion, the Witch and the Wardrobe"
|
|
|
|
Step 1: Search for the opening scene of "The Chronicles of Narnia: The Lion, the Witch and the Wardrobe" online
|
|
|
|
Step 2: Create a JSON prompt file with the following content:
|
|
|
|
```json
|
|
{
|
|
"title": "The Chronicles of Narnia - Train Station Farewell",
|
|
"background": {
|
|
"description": "World War II evacuation scene at a crowded London train station. Steam and smoke fill the air as children are being sent to the countryside to escape the Blitz.",
|
|
"era": "1940s wartime Britain",
|
|
"location": "London railway station platform"
|
|
},
|
|
"characters": ["Mrs. Pevensie", "Lucy Pevensie"],
|
|
"camera": {
|
|
"type": "Close-up two-shot",
|
|
"movement": "Static with subtle handheld movement",
|
|
"angle": "Profile view, intimate framing",
|
|
"focus": "Both faces in focus, background soft bokeh"
|
|
},
|
|
"dialogue": [
|
|
{
|
|
"character": "Mrs. Pevensie",
|
|
"text": "You must be brave for me, darling. I'll come for you... I promise."
|
|
},
|
|
{
|
|
"character": "Lucy Pevensie",
|
|
"text": "I will be, mother. I promise."
|
|
}
|
|
],
|
|
"audio": [
|
|
{
|
|
"type": "Train whistle blows (signaling departure)",
|
|
"volume": 1
|
|
},
|
|
{
|
|
"type": "Strings swell emotionally, then fade",
|
|
"volume": 0.5
|
|
},
|
|
{
|
|
"type": "Ambient sound of the train station",
|
|
"volume": 0.5
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
Step 3: Use the image-generation skill to generate the reference image
|
|
|
|
Load the image-generation skill and generate a single reference image `narnia-farewell-scene-01.jpg` according to the skill.
|
|
|
|
Step 4: Use the generate.py script to generate the video
|
|
```bash
|
|
python /mnt/skills/public/video-generation/scripts/generate.py \
|
|
--prompt-file /mnt/user-data/workspace/narnia-farewell-scene.json \
|
|
--reference-images /mnt/user-data/outputs/narnia-farewell-scene-01.jpg \
|
|
--output-file /mnt/user-data/outputs/narnia-farewell-scene-01.mp4 \
|
|
--aspect-ratio 16:9
|
|
```
|
|
> Do NOT read the python file, just call it with the parameters.
|
|
|
|
## Output Handling
|
|
|
|
After generation:
|
|
|
|
- Videos are typically saved in `/mnt/user-data/outputs/`
|
|
- Share generated videos (come first) with user as well as generated image if applicable, using `present_files` tool
|
|
- Provide brief description of the generation result
|
|
- Offer to iterate if adjustments needed
|
|
|
|
## Notes
|
|
|
|
- Always use English for prompts regardless of user's language
|
|
- JSON format ensures structured, parsable prompts
|
|
- Reference image enhance generation quality significantly
|
|
- Iterative refinement is normal for optimal results
|
|
|
|
## Providers (Gemini / MiniMax)
|
|
|
|
Auto-selected by environment variables (CLI unchanged):
|
|
|
|
- `GEMINI_API_KEY` set → Gemini Veo (default, unchanged).
|
|
- Only `MINIMAX_API_KEY` set → MiniMax video (`/v1/video_generation`, async 3-step poll/download).
|
|
- Force with `VIDEO_GENERATION_PROVIDER=gemini|minimax`.
|
|
|
|
MiniMax overrides: `MINIMAX_API_HOST` (default `https://api.minimaxi.com`),
|
|
`MINIMAX_VIDEO_MODEL` (default `MiniMax-Hailuo-2.3`). The first reference image is used
|
|
as MiniMax `first_frame_image`. MiniMax ignores `--aspect-ratio` (it uses resolution/duration).
|