agentleFS
Sign inStart free
emeradutiable111emeradutiable111/AutoVideo-Agent/skills/auto-video/SKILL.md

auto-video

Skill0 starsChanged 3 months agoMITView on GitHub

Run and validate AutoVideo-Agent Markdown-to-video workflows, including the v0.1-compatible deterministic offline command and v0.2 provider mode with ComfyUI media, Mock or Command TTS, scene-level SRT, normalized timelines, FFmpeg, and deterministic QA. Use for build, plan, provider, or QA requests; MiniMax, hosted TTS integrations, and word-level subtitle alignment remain planned.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. wddxh/ShortVideoDirector★ 21same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to operate the AutoVideo-Agent repository honestly and reproducibly.

    line 8
  2. Distinctive:

    Read AGENTS.md and inspect the target Markdown script before running anything.

    line 12
  3. Very specific:

    Run autovideo run <script.md> for v0.1-compatible offline mode, or add --config <config.yaml> for provider mode.

    line 14
  4. Distinctive:

    Run autovideo qa <build-directory>.

    line 16
  5. Very specific:

    When changing core behavior, run python -m pytest and git diff --check before reporting completion.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AutoVideo Pipeline

Use this skill to operate the AutoVideo-Agent repository honestly and reproducibly.

Workflow

  1. Read AGENTS.md and inspect the target Markdown script before running anything.
  2. Confirm the script has a top-level '#' title and one or more '##' scene headings. Scene fields may include duration, visual, and narration.
  3. Run autovideo run <script.md> for v0.1-compatible offline mode, or add --config <config.yaml> for provider mode. Use --output <dir> when the build must be isolated.
  4. Inspect the JSON printed by the CLI and then read <output>/report.json and <output>/manifest.json.
  5. Run autovideo qa <build-directory>. Treat PASS as validated, WARNING as usable with declared limitations, and FAIL as incomplete.
  6. When changing core behavior, run python -m pytest and git diff --check before reporting completion.

Mode Boundaries

Without --config, preserve the v0.1 deterministic placeholder PPM cards, silent WAV, manifest, report, and FFmpeg degradation behavior. With a v0.2 config, select placeholder or ComfyUI media plus Mock or Command TTS; generate scene-level SRT from actual audio duration, a contiguous timeline, H.264/AAC MP4, and deterministic QA. Do not claim MiniMax, OpenAI TTS, Volcengine, ElevenLabs, word-level alignment, or generic real-media adapters are implemented.

Agent Request Example

For a request such as:

Turn examples/demo-script.md into a video and run QA.

execute the CLI, run autovideo qa on the build directory, verify the report and manifest, and summarize the actual status, output paths, duration, scene count, provider names, and warnings. Do not infer media quality from prompt text or claim a remote provider was tested when only HTTP mocks ran.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free