Venice Video
Wire Venice.ai video generation and transcription into agent planning when you need API-backed clips or transcripts without hunting the upstream repo.
Overview
venice-video is an agent skill for the Build phase that advertises Venice.ai API video generation and transcription workflows and routes you to the upstream skills bundle to run them.
Install
npx skills add https://github.com/nexu-io/open-design --skill venice-videoWhat is this skill?
- Catalogues Venice.ai video generation and transcription via API workflows
- Open Design entry with upstream bundle at github.com/veniceai/skills
- Trigger phrases: venice video, venice video gen, venice transcribe
- Mode video, category video-generation in Open Design metadata
- Install upstream skills directory for full scripts, assets, and references
- Upstream source: github.com/veniceai/skills
- Open Design category: video-generation
Adoption & trust: 771 installs on skills.sh; 61.4k GitHub stars.
What problem does it solve?
You want Venice-backed video or transcribe automation in your agent but only have a fragmentary catalogue stub without the real scripts and API steps.
Who is it for?
Solo builders using Open Design who already use or plan to use Venice.ai and want discoverable, nameable video-gen and transcribe skills in the agent catalog.
Skip if: Teams that need a self-contained SKILL.md with inlined API steps, or builders who do not use Venice.ai and only need generic local ffmpeg scripting.
When should I use this skill?
User or planner mentions venice video, venice video gen, or venice transcribe, or needs Venice.ai video generation and transcription workflows.
What do I get? / Deliverables
The agent recognizes Venice video workflows during planning, installs the upstream Venice.ai skills package, then runs generation or transcription per that bundle’s instructions.
- Installed upstream Venice video/transcribe skill bundle
- Agent-invoked video or transcription per upstream workflow
Recommended Skills
Journey fit
Canonical shelf is Build because the skill advertises an external generative API workflow agents invoke while assembling product or content pipelines. integrations fits Venice as a third-party API bundle the agent discovers and installs, not in-repo frontend or backend code.
How it compares
A catalogue pointer to Venice’s upstream skill pack—not a built-in MCP server or a single-shot local ffmpeg generator.
Common Questions / FAQ
Who is venice-video for?
Indie builders and agent users who standardize on Venice.ai for API video generation or transcription and want Prism/Open Design to surface the official upstream workflow during planning.
When should I use venice-video?
Use it in Build when wiring generative media into a product or content pipeline, or when a task explicitly mentions Venice video gen or transcribe; after discovery, install github.com/veniceai/skills and invoke by skill name or trigger phrase.
Is venice-video safe to install?
Treat it like any third-party API skill: review the Security Audits panel on this Prism page and inspect the upstream Venice.ai repository before granting network access and API keys.
SKILL.md
READMESKILL.md - Venice Video
# venice-video > Curated from the Venice.ai team. ## What it does Video generation and transcription workflows via the Venice.ai API. ## Source - Upstream: https://github.com/veniceai/skills - Category: `video-generation` ## How to use This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory: ```bash # Inspect the upstream README for exact paths open https://github.com/veniceai/skills ``` Then ask the agent to invoke this skill by name (`venice-video`) or with one of the trigger phrases listed in this skill's frontmatter.