video-prompt-builder

Routes video generation briefs to provider-specific prompt builders via a task-kind matrix.

9|Updated May 8, 2026
One-click install
npx skills add https://github.com/simpletibr/simplicio-loop-marketing --skill video-prompt-builder-simpletibr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: video-prompt-builder
Source: https://github.com/simpletibr/simplicio-loop-marketing/tree/main/.skills/video-prompt-builder
Command: npx skills add https://github.com/simpletibr/simplicio-loop-marketing --skill video-prompt-builder-simpletibr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right video generation provider for each creative task is error-prone and scattered across multiple specialist skills. This Skill centralizes that decision by reading a routing matrix and delegating each brief to the correct provider-specific prompt builder. ## Core Features & Use Cases - Provider routing: Parses the Video matrix in .specs/architecture/PROVIDERS.md to map task kinds like cinematic_reel, ugc_product_holder, or programmatic_short to Higgsfield, Topview, Wavespeed, or Hyperframes. - Override and fallback handling: Honors provider_override.video in piece files, falls back to the cinematic default for unknown task kinds, and drops to the next provider when required env vars are missing. - Dry-run and cost visibility: Returns the resolved provider, params, MCP tool, and cost estimate without calling the MCP, and logs every run to data/video-usage.jsonl. - Use Case: A marketing pipeline receives a brief for a 6-second editorial reel; the Skill resolves cinematic_reel to Higgsfield, translates the brief into the specialist's input shape, and returns the generated artifact reference. ## Quick Start Ask the agent to build a video generation prompt from your brief, specifying the task kind such as cinematic_reel or ugc_product_holder, and let it route to the right provider.

Frequently Asked Questions about video-prompt-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right AI video generation provider for a task?

Define a task_kind such as cinematic_reel, ugc_product_holder, or batch_hook_test and let the routing matrix in PROVIDERS.md map it to a provider. The Skill resolves the provider, builds the params, and returns the MCP tool to call.

How do I override the default video provider for a specific piece?

Add a provider_override.video field to the piece file under .specs/pieces/. When piece_path is passed in, the override takes precedence over the routing matrix lookup.

What happens when a video provider API key is missing?

The Skill checks env vars like HIGGSFIELD_MCP_ACTIVE, TOPVIEW_API_KEY, WAVESPEED_API_KEY, and HYPERFRAMES_ACTIVE before dispatch. If the chosen provider's variable is missing, it drops to the next provider in the matrix and surfaces a warning.

Can I test video prompt routing without calling the API?

Yes, set dry_run to true. The Skill returns the resolved provider, the final params object, and the MCP tool name without invoking the MCP or incurring generation costs.

What task kinds does the video prompt router support?

Supported task kinds include cinematic_reel, motion_control, ugc_product_holder, product_demo, talking_head, batch_hook_test, motion_typography, data_viz_reel, and programmatic_short. Unknown kinds fall back to the cinematic_reel default with a logged warning.