Avenox Video logo

Avenox Video

Community
avenoxai
avenox-video

Avenox Studio — local-first YouTube video production pipeline (ROUTER, read first). Use for ANY request to edit, cut, produce, assemble, caption, score, or render a long-form video, or to make motion graphics for one. Wraps open-source tooling (auto-editor, mlx-whisper, MLT/melt, ffmpeg) plus HyperFrames for animated graphics. Triggers: "edit this video", "cut the recording", "make graphics", "extract captions", "render the final", a job name, or anything about the video pipeline. The human is director/quality gate; the agent is the operator.

Overview

Publisheravenoxai
Repositoryavenoxskills
Skill nameavenox-video
Stars
105
Forks
6
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by avenoxai on GitHub. Read the source before you install it.

Installation

Install the Avenox Video AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/avenoxai/avenoxskills/tree/main/skills/avenox-video
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/avenoxai/avenoxskills.git /tmp/avenoxskills
mkdir -p .claude/skills
cp -r /tmp/avenoxskills/skills/avenox-video .claude/skills/avenox-video
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Avenox Video in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Avenox Video on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Avenox Video is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Avenox Studio — operator router

The fast operator guide for a local-first, agent-operated video pipeline. Everything runs on your own machine: no cloud editor, no upload-to-render.

The human directs and approves quality; the agent runs the pipeline.

Setup

bash
export STUDIO_JOBS="$HOME/video/projects"   # heavy media lives here
export STUDIO_ROOT="/path/to/this/repo"     # scripts, templates, brand

Requirements: macOS (hardware encode via h264_videotoolbox; Apple Silicon for mlx-whisper), ffmpeg, python3, melt/MLT, Node (for HyperFrames). Most of this works on Linux with libx264 and a CUDA whisper build substituted in.

Operating principles

  1. Media discipline. Heavy media NEVER in a cloud-synced folder — sync will thrash on multi-GB intermediates and can corrupt in-flight writes. Jobs live in $STUDIO_JOBS/<job>/ (raw/ cut/ graphics/ audio/ outputs/). Your notes system holds only the brain: this system, the brand spec, edit.json plans.
  2. Director loop. Produce a preview (graphics stills + a fast draft render) → send for notes → only then final render. Never ship a final without sign-off. This is the single most important rule; an agent that renders finals unreviewed will burn hours on a rejected cut.
  3. Brand is a hard constraint, not a suggestion. Read brand/frame.md before making any graphic. Define it once and lock it. (The reference implementation is deliberately anti-"AI slop": premium editorial, warm paper
    • ink + a single accent, no neon/gradient/glassmorphism/3D-gloss.)
  4. Format: YouTube 16:9 1080p60. Preset in brand/presets/youtube-16x9.json.
  5. Finishing is hybrid. Auto-generate the draft; the same .mlt opens in Kdenlive or Shotcut for hand-finishing. Don't try to automate taste.
  6. Transcription defaults to LOCAL mlx-whisper with whisper-large-v3-turbo — fast, free, and strong on non-English audio. Note that most LLM-routing proxies expose no whisper endpoint; if you go remote, use a dedicated speech API.

Scripts (scripts/)

ScriptDoes
autocut.sh IN.mp4 [balanced|aggressive|conservative]silence-cut → _cut.xml (Premiere) or --export variants
transcribe.py IN.mp4 PREFIX→ transcript/PREFIX_timed.json + _narration.txt
mltgen.py edit.json out.mlt --base <job-dir>edit-list → MLT project (Kdenlive/Shotcut/melt)
vrender.sh project.mlt out.mp4 [fast|quality]render (fast = HW draft, quality = CRF18 master)
grabshot.shclipboard screenshot → disk
slides2png.shlegacy static slides — prefer HyperFrames
remove-silence.pystandalone silence pass

The 7 steps

  1. Intake — copy raw → $STUDIO_JOBS/<job>/raw/. Confirm the brief and which segments actually matter.
  2. Rough cut — autocut.sh raw.mov balanced → cut/screen_cut.mp4; transcribe.py for the script. Full recipe → avenox-roughcut skill.
  3. Graphics — HyperFrames. Route via the hyperframes skill → usually motion-graphics (short beats), faceless-explainer (concept stretches), or general-video. Read brand/frame.md first; render animated MP4s into graphics/. Full recipe → avenox-graphics skill.
  4. Assemble — write edit.json (template in templates/edit.json) mixing cut/*.mp4 + graphics/*.mp4 + music → mltgen.py edit.json project.mlt --base <job-dir>.
  5. Captions — transcribe.py → .srt; apply brand/caption-corrections.json (copy it from caption-corrections.example.json — a find/replace map for terms your ASR reliably mangles). Ship as YouTube CC, not burned-in.
  6. Music — bed under everything, sidechain-duck under voice, target ~-14 LUFS. Track attribution in CREDITS.md.
  7. Export — vrender.sh project.mlt draft.mp4 fast → director review → vrender.sh … final.mp4 quality → prune scratch files.

Graphics quality bar

HyperFrames clips must obey brand/frame.md. Prefer type-driven, restrained, weighty motion. If a beat doesn't need motion, a clean static frame is fine — don't animate for the sake of animating.

Reference

  • Rough cut: avenox-roughcut · Graphics: avenox-graphics
  • HyperFrames skills: hyperframes (router), hyperframes-cli, hyperframes-animation, hyperframes-creative, motion-graphics, faceless-explainer, general-video
  • Brand spec: brand/frame.md (fill in from brand/frame.template.md)

Frequently asked questions

What does the Avenox Video AI skill do?

Avenox Studio — local-first YouTube video production pipeline (ROUTER, read first). Use for ANY request to edit, cut, produce, assemble, caption, score, or render a long-form video, or to make motion graphics for one. Wraps open-source tooling (auto-editor, mlx-whisper, MLT/melt, ffmpeg) plus HyperFrames for animated graphics. Triggers: "edit this video", "cut the recording", "make graphics", "extract captions", "render the final", a job name, or anything about the video pipeline. The human is director/quality gate; the agent is the operator.

Why use Avenox Video on TypingMind?

Because you install it once and use it with any model. Avenox Video is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Avenox Video in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/avenoxai/avenoxskills/tree/main/skills/avenox-video. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Avenox Video?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Avenox Video?

As many as you like. As long as a model supports skills, you can use Avenox Video with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Avenox Video AI skill free?

Yes. It is published on GitHub by avenoxai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇