Skip to content
Back to skills

Documentary Producer

ASecurity

Coordinate Tutopanda CLI and MCP to generate, edit, inspect, and preview documentary videos (video-audio-music blueprint with FinalVideo export). Use when users ask for Tutopanda to build, edit, or review movies inside Claude Code.

  • 666 stars
  • 0 votes
  • 0 copies
  • 7 views
  • Added February 8, 2026
toolsbash

Works with

  • claude code
  • cli
  • mcp

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill documentary-producer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Documentary Producer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Documentary Producer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-documentary-producer/badge)](https://www.skillsdirectory.com/skills/majiayu000-documentary-producer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: tutopanda-documentary-producer
description: Coordinate Tutopanda CLI and MCP to generate, edit, inspect, and preview documentary videos (video-audio-music blueprint with FinalVideo export). Use when users ask for Tutopanda to build, edit, or review movies inside Claude Code.
---

# Tutopanda Documentary Producer

Use this skill whenever a user wants Tutopanda to create or modify documentary-style videos, export an MP4, or preview results from within Claude Code.

## Preconditions
- `tutopanda` binary is available on PATH. If not, stop and ask the user to install the published CLI manually.
- Tutopanda has been initialized (`tutopanda init --rootFolder=<absolute-path>`). Confirm the config path or `TUTOPANDA_CLI_CONFIG` before running any command.
- Default blueprint is `video-audio-music.yaml` because it emits `FinalVideo` (MP4) in addition to the timeline. Switch blueprints only if the user requests a different workflow.

## Generation workflow
1. Collect required inputs from the user: `InquiryPrompt`, `Duration`, `NumOfSegments`, `SegmentDuration`, `VideoStyle`, `AspectRatio`, `Resolution`, `VoiceId`, plus optional `Audience`, `Language`, `Emotion`, `MusicalStyle`. Do not fabricate values.
2. Write an inputs YAML with those values at an absolute path the user approves.
3. Run Tutopanda via MCP (preferred) or CLI:
   - CLI example:
     ```bash
     tutopanda query "<InquiryPrompt>" \
       --inputs=/absolute/path/to/inputs.yaml \
       --usingBlueprint=video-audio-music.yaml \
       --concurrency=<workers-if-needed> \
       --nonInteractive
     ```
4. Capture the `movieId`, plan path, and friendly view path from the output.
5. If the user wants a preview, call `tutopanda viewer:view --movieId=<movieId>`.

## Editing workflow
- Require the existing `movieId` and an explicit inputs file path. Run:
  ```bash
  tutopanda edit \
    --movieId=<movie-id> \
    --inputs=/absolute/path/to/inputs.yaml \
    --usingBlueprint=video-audio-music.yaml \
    --concurrency=<workers-if-needed> \
    --nonInteractive
  ```
- Use `--dryRun` or `--upToLayer` only when the user asks for them. After the run, refresh the viewer.

## Inspection and review
- For prompts/timelines, run `tutopanda inspect --movieId=<movie-id> --prompts --all` and summarize key findings.
- Keep outputs and artefact paths tied to the configured root; do not relocate them.

## Failure handling
- If the CLI or config is missing, stop and ask the user to install or initialize Tutopanda rather than guessing paths or creating defaults.
- Avoid silently falling back to placeholder inputs—always confirm required fields before running.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.