Agent skill

Video Craft

by Orkas-AI in Orkas-AI/Orkas-VideoStudio

The craft standard that makes a video GOOD, not just rendered — hooks, story pacing, visual hierarchy, type & safe zones, motion/easing, captions, audio mix, platform conventions, shot language…

MITAuto-check passedMedia & Creative

Install Video Craft

skills CLI
$ npx skills add Orkas-AI/Orkas-VideoStudio --skill video-craft -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Orkas-AI/Orkas-VideoStudio video-craft --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Orkas-AI/Orkas-VideoStudio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills/video-craft .claude/skills/video-craft && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
video-craft
GitHub stars
499
Token cost
~3.3k tokens
SKILL.md length
1,801 words
Files
3 (incl. references)
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

The craft standard that makes a video GOOD, not just rendered — hooks, story pacing, visual hierarchy, type & safe zones, motion/easing, captions, audio mix, platform conventions, shot language…

  • Works in 12 steps: The opening (hook) → Story structure → Pacing & timing → …
  • Before scripting/storyboarding/composing/generating/editing on EVERY line
  • SKILL.md covers 1. The opening (hook), 2. Story structure, 3. Pacing & timing and 4. Visual design, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Video Craft is an agent skill from Orkas-AI/Orkas-VideoStudio. The craft standard that makes a video GOOD, not just rendered — hooks, story pacing, visual hierarchy, type & safe zones, motion/easing, captions, audio mix, platform conventions, shot language, generation-prompt writing, and a pre-publish review. Trigger before scripting/storyboarding/composing/generating/editing on EVERY line, and again as the final review; do NOT trigger for tool mechanics (use the matching stage skill).

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/ecommerce.md` and `references/reference-recreation.md`).

It sits in Media & Creative, covering Type safety, AI video generation and Transcription. The repository describes itself as: Turn your coding agent into a video studio: describe a video in plain language, and your agent writes the timeline and produces the file. The licence is MIT.

When your agent uses it

  • Before scripting/storyboarding/composing/generating/editing on EVERY line
  • Again as the final review
  • Do NOT trigger for tool mechanics (use the matching stage skill)

Example prompts

  • “/video-craft”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. The opening (hook)
  2. Story structure
  3. Pacing & timing
  4. Visual design
  5. Motion & animation
  6. Captions / on-screen text
  7. Audio
  8. Platform & format
  9. Per-line craft — see the matching stage skill
  10. Shot & camera language (generation / cinematic)
  11. Generation-prompt writing
  12. Pre-publish review pass

What it can do on your machine

Read from SKILL.md and the folder at commit c0c3c3e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Video Craft loads about 3.3k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 1,801 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Orkas-AI/Orkas-VideoStudio at commit c0c3c3e, republished under its MIT licence (© Orkas-AI). 1,801 words, ~3,256 tokens.

Download SKILL.mdSave it as .claude/skills/video-craft/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
video-craft
description
The craft standard that makes a video GOOD, not just rendered — hooks, story pacing, visual hierarchy, type & safe zones, motion/easing, captions, audio mix, platform conventions, shot language, generation-prompt writing, and a pre-publish review. Trigger before scripting/storyboarding/composing/generating/editing on EVERY line, and again as the final review; do NOT trigger for tool mechanics (use the matching stage skill).

video-craft

The difference between a video that merely renders and one that's actually good. Apply these standards while scripting, storyboarding, composing, generating, and editing — and run the self-check before publishing. These are general production-craft norms; the exact numbers are starting points, adjust to the brief.

For reference-led local work, read reference-led reconstruction. For product listing or sales creative, also read ecommerce videos. Apply the production-method boundary from video-router first: one direct model video skips local creative/mastering review, while any local caption, overlay, audio, join, deterministic edit, or HTML layer receives the applicable review below.

1. The opening (hook)

  • The first 1–3 seconds decide whether anyone keeps watching. Frame 1 must already carry motion or a text hook — no blank intro, no logo sting, no slow build.
  • Strong hook shapes: a sharp question, a counter-intuitive claim, the promised outcome ("by the end you'll…"), the stakes, or showing the finished result first ("here's what we'll build").
  • On muted autoplay the on-screen text is the hook — assume no sound for the first beat.
  • Weak → strong: ✗ "In this video we'll look at caching." (slow build, no stakes) → ✓ frame 1, bold on-screen text "Your API is slow. One line fixes it." (stakes + promised outcome, readable muted).

2. Story structure

  • Arc: hook → tension/gap → core idea(s) → proof/example → payoff/close (+ optional CTA). Land the first real payoff early; viewers drop off fast before they get value.
  • One new idea per ~30–45 s of explainer. A 3-min video carries 4–6 ideas, no more. Cut "interesting but irrelevant" — it actively lowers comprehension.
  • Connect beats with "but" / "therefore", not "and then" — force logical (not just sequential) progression.
  • For teaching: show the naive idea, let it half-work, then break it and introduce the one key insight — people remember what they feel they discovered. Surfacing a common misconception first, then correcting it, beats stating the right answer cold.
  • Narration cadence: explainer ~150–160 wpm, social/short ~180–200 wpm, cinematic ~140–150 wpm. Leave a 1–3 s silence after a big reveal; avoid dead air > ~1.5 s between sentences.

3. Pacing & timing

  • Shot/scene holds by format: explainer ~4–8 s, short-form social ~1–3 s, cinematic/contemplative ~10–20 s. Don't hold the same length three times running — vary it.
  • Cutting energy: rapid (15–30 cuts/min) = urgency; moderate (8–15) = standard teaching; slow (3–6) = documentary calm.
  • A visual or audio pattern interrupt every ~20–30 s (short-form) / ~45–90 s (long-form) to re-grab attention.
  • Completion drops with length (15 s clips finish far more often than 60 s) — keep it as short as the message allows; don't pad.
  • Build animation timing to the narration words, not arbitrary beats. Hold a fully-built scene/chart ≥ 2–3 s before moving on.

4. Visual design

  • Composition: rule-of-thirds for key elements; center for stable establishing frames. One clear focal point per frame.
  • Palette: ≤ 3–5 colors on screen at once. Background is the least-saturated; foreground (largest, most saturated, central) reads first.
  • Typography: 1–2 font families total. At 1080p, titles ~60–90 px, body ~40–60 px, never below ~40 px; title at least ~50% larger than body. Max ~2 lines, ~32–42 chars/line.
  • Safe zones: keep text inside ~80% of the frame (~192 px margin at 1080p). For vertical, keep essential content out of the bottom ~300 px (platform UI sits there) and away from the very top.
  • Contrast ≥ 4.5:1 for any text (white-on-dark is safest). Use brightness/saturation, not red-green, to distinguish elements.
  • Consistency is a feeling of quality: one color grade/LUT, one type system, 2–3 transition types — for the whole video.

5. Motion & animation

  • Never linear easing — it reads robotic. Default ease-in-out for moves, ease-out for entrances (settle in), ease-in for exits (accelerate away). Vary easing; don't repeat one three times.
  • Restraint: one main element moves at a time; stagger multi-element reveals by ~100–200 ms. A "static" shot means truly zero motion/zoom — if it moves, name the move.
  • Weak → strong: ✗ four cards fly in together, linear, all 0.3 s → ✓ stagger them ~120 ms, ease-out, each settling before the next starts (one focal point at a time).
  • Entrances ~0.3–0.5 s then hold for readable dwell; exits ~0.5–1 s. Optional small overshoot (~10–15%, settle in a few frames) adds life for playful pieces.
  • Kinetic type: reveal text to a readable dwell (~3 s per ~60 chars); word-by-word reveal synced to narration boosts attention.
  • Transitions carry meaning: hard cut = same topic/new angle (most invisible, most professional); crossfade = gentle topic change; wipe/slide = sequential steps; zoom in/out = into detail / out to context. Pick a small set and keep them consistent.

6. Captions / on-screen text

  • Most social viewing is muted — captions are mandatory and are part of the pacing, not an afterthought.
  • Bold sans-serif, ≥ ~42 px, ≤ ~2 lines, ≤ ~32–42 chars/line, with a dark stroke or semi-opaque backing for legibility on any footage.
  • Don't scroll text off before it can be read (~3 s per ~60 chars). Word-by-word highlighting in sync with the voice reads best.
  • Lower-thirds: speaker name bold + role lighter; enter ~1–2 s, hold a few seconds, exit fast; never cover eyes/mouth.
  • Don't make the viewer read on-screen text AND listen to different words at once.

7. Audio

  • Pick music by energy: calm ~60–80 BPM, standard explainer ~90–110, upbeat ~110–130, high-energy ~120–140+. Use instrumental under narration (lyrics fight the voice); avoid big crescendos that bury speech.
  • Levels: narration peaks loudest; duck music ~18–20 dB below speech; SFX between. Master around −14 LUFS, true-peak ≤ ~−1 dB; never clip 0 dB.
  • SFX land ~10–20 ms before the visual change they accent (ears lead eyes). Keep stacked SFX in different frequency bands.
  • Silence is a tool — drop music for a few seconds at a major reveal; let the moment land.

8. Platform & format

  • Aspect: 9:16 (TikTok/Reels/Shorts), 16:9 (YouTube/web), 1:1 when speaker+context both matter, cinematic letterbox only when the look serves it. Don't center-crop a wide shot and call it vertical — reframe properly or downgrade to 1:1 honestly.
  • Get past the 3-second threshold: hook in frame 1, change something every 1–3 s in short-form, captions always.
  • The first frame is the thumbnail/promise—design it deliberately as a cover, not an accidental pre-animation state. It needs a readable promise plus concrete signals of the actual subject/result; match what the video delivers and pay it off quickly.
  • Match length to platform norms; the algorithm rewards watch-time/completion, not raw length.
Show full SKILL.md (779 more words)Show less

9. Per-line craft — see the matching stage skill

The cross-cutting craft above (§1–§8, §10–§11) applies to every line. The line-specific director judgment lives with each line's mechanics in its stage skill — read the one for the line you locked:

  • Explainer / animation → stage-compose (compose line).
  • Talking-head, cinematic → stage-generate (generation line).
  • Social clip, podcast-repurpose, screen-demo, localization, documentary-montage → stage-edit (editing line).
  • A finished video woven from the user's material + framing / voice / motion (more than one line) → stage-plan + stage-assemble (AUTO end-to-end line) — the cross-source editorial judgment: deciding the spine source-agnostic, assigning each beat the right source, and engineering continuity across the seams.

If a piece layers lines (e.g. compose captions over generated footage), read both and apply the primary (locked) line's judgment first.

10. Shot & camera language (generation / cinematic)

  • Move through shot sizes for flow: wide (establish) → medium (develop) → close (emotion); avoid jumping wide-to-close without an intermediate.
  • Design each shot as a first frame → last frame; the motion bridges them. Each frame is a static snapshot, never an action in progress ("sitting, leaning forward", not "about to stand up"); the last frame is the logical result of the first frame + the motion. Big composition changes need an explicit camera move; small changes (expression, slight pose) stay in one framing.
  • Reuse camera positions; only introduce a new one when size/angle/focus genuinely changes. Keep relative positions stable across cuts (if a subject was left, keep them left); for two people talking, an over-the-shoulder pair plus a wider two-shot keeps geography clear.
  • Keep narrative/teaching shots steady and deliberate; reserve handheld / fast cuts / rapid zoom for action.

11. Generation-prompt writing

  • Describe by concrete visual features, never by abstractions: "forest-green canvas jacket, short curly black hair" — not "professional, friendly". Adjectives like "warm" or "premium" don't constrain pixels; show them through appearance, light, and posture. Name the visual cause of a feeling, not the feeling ("wide aerial pull-back, lone figure against the rising sun", not "epic"); if you can't picture a specific photograph from the words, neither can the model.
  • Weak → strong: ✗ "a professional, friendly host in a modern office" → ✓ "woman, mid-30s, short black bob, charcoal blazer over white tee; sunlit open-plan office; soft window key from camera-left." Every adjective replaced by something the renderer can actually draw.
  • Specify lighting + color temperature + style (soft daylight / harsh noon / warm key; realistic vs cinematic) to anchor tone across shots.
  • For a shot, include shot size, (optional) lens feel (24/50/85 mm), camera move, and which reference image governs which element ("face from ref A, environment from ref B"). See stage-consistency for the character-bible + reference-selection method.

12. Pre-publish review pass

This is a review, not a checkbox sweep — read the draft as a skeptic hunting for what's wrong. Every issue you raise must name where and the concrete fix (change what, to what); if you can't name a fix, it isn't a finding yet — mark it "verify" and go look, don't leave a vague worry. Tag each finding:

  • blocker — ship-stopping (unreadable text, wrong aspect, missing hook, identity break, clipping audio). Fix before the final render.
  • fix — clearly hurts quality but not ship-stopping; fix unless out of scope.
  • polish — nice-to-have; note and move on.
Slideshow-risk gate (run before the high-quality render)

The most common failure of generated/composed video is that it quietly degrades into a slideshow — stills with captions, no real motion or intent. Score the draft 0 (clean) / 1 (some) / 2 (bad) on each; treat any 2, or an overall "this reads as a slideshow", as a blocker:

  • Dead motion — shots sit still: no camera move, build, or designed motion where the format wants it.
  • Repetition — same shot size / scene type / transition ≥ 3 in a row.
  • Decoration — motion or effects that carry no meaning (movement for its own sake).
  • Promise drift — a motion/cinematic brief silently delivered as static cards (see the routing lock).
  • Text crutch — walls of on-screen text doing the job the visuals should be doing.
Then confirm (each line = where a finding hides)
  • Readable — text ≥ the legibility floor (~40 px at 1080p, scaled to the canvas) and ≥ 4.5:1 contrast; captions synced; nothing covers the face/critical content; readable at phone size.
  • Timed — hook lands in the first seconds; first payoff early; pattern interrupt on cadence; each scene held long enough to read; narration wpm fits the format.
  • On message — the core point is actually stated; visuals reinforce (not fight) the narration; no padding/dead time; exact text correct (no hallucinated stats).
  • Consistent — one grade, one type system, a small transition set; subject identity preserved across cuts.
  • Audio — speech clear and loudest; music ducked; SFX slightly lead the cut; ~−14 LUFS integrated, true-peak ≤ ~−1 dBTP, no clipping/pops; silences intentional.
  • Platform — text in safe zones; correct aspect; length in range; first frame matches the promise.

© Orkas-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in packages/skills/video-craft of Orkas-AI/Orkas-VideoStudio.

  • SKILL.md
  • references/ecommerce.md
  • references/reference-recreation.md

Open the folder on GitHubat commit c0c3c3e

Compare with similar skills

Video Craft next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Video Craft compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Video Craft this skillOrkas-AI/Orkas-VideoStudio499—~3.3kAutomated safety check: PassMIT
Clean Cuthassancs91/claude-youtube-editor328—~4.3kAutomated safety check: NotesMIT
Video Productionffroliva/gflow-cli278—~7kAutomated safety check: PassMIT
AI Video Scriptzrt-ai-lab/opencode-skills287—~1.7kAutomated safety check: PassNone
Videodb Skillssickn33/agentic-awesome-skills47k2 repos~939Automated safety check: PassMIT
Venice Videonexu-io/open-design100k—~255Automated safety check: PassApache-2.0

Similar skills

  • Clean Cut

    hassancs91/claude-youtube-editor

    Step 1 of the AI Video Editor pipeline — turn raw talking-head footage into a clean master cut.

    328 GitHub stars~4.3k tokensUpdated 1 mo ago
    Media & CreativeAuto-check: notes
  • Video Production

    ffroliva/gflow-cli

    A skill your agent uses when the user wants a finished video out of gflow rather than a single clip — a scripted scene, a talking-head or dialogue piece, an explainer, a product montage, a story…

    278 GitHub stars~7k tokensUpdated today
    Media & CreativeAuto-check passed
  • AI Video Script

    zrt-ai-lab/opencode-skills

    A skill your agent uses when a request asks for a Chinese-first AI video script with shot plans, image prompts, narration, subtitles, or handoff contracts for scene generation, image generation…

    287 GitHub stars~1.7k tokensUpdated 2 mo ago
    Media & CreativeAuto-check passed
  • Videodb Skills

    sickn33/agentic-awesome-skills

    Upload, stream, search, edit, transcribe, and generate AI video and audio using the VideoDB SDK.

    47k GitHub starsUsed in 2 repos~939 tokens
    Media & CreativeAuto-check passed
  • Venice Video

    nexu-io/open-design

    Video generation and transcription workflows via the Venice.ai API.

    100k GitHub stars~255 tokensUpdated yesterday
    Media & CreativeAuto-check passed
  • Pollinations

    sundial-org/awesome-openclaw-skills

    Pollinations.ai API for AI generation - text, images, videos, audio, and analysis.

    663 GitHub stars~1.7k tokensUpdated 7 mo ago
    Media & CreativeAuto-check passed

More from Orkas-AI/Orkas-VideoStudio

All 14 skills in this repo
  • Gate Control

    Orkas-AI/Orkas-VideoStudio

    Canonical VideoStudio review authorization and state-transition policy.

    499 GitHub stars~2.7k tokensUpdated 19 days ago
    Auto-check passed
  • Stage Compose

    Orkas-AI/Orkas-VideoStudio

    Authoring knowledge for Orkas/OVS HTML video compositions -- write an index.html, drive animation from a paused timeline, declare canvas + duration, then run the VideoStudio draft gate to render an…

    499 GitHub stars~4.2k tokensUpdated 19 days ago
    Auto-check passed
  • Stage Edit

    Orkas-AI/Orkas-VideoStudio

    Intelligent editing of real user-supplied footage—understand it with transcript/inspected-frame/scene/silence/quality evidence, then choose deterministic timeline operations or a constrained…

    499 GitHub stars~2.4k tokensUpdated 19 days ago
    Auto-check passed
  • Stage Consistency

    Orkas-AI/Orkas-VideoStudio

    Multi-shot narrative & character consistency — a character bible with a locked front-portrait anchor, view-matched reference selection, recent-frame carry-forward, Cameo (a user photo as the lead)…

    499 GitHub stars~1.8k tokensUpdated 19 days ago
    Auto-check passed
  • Stage Plan

    Orkas-AI/Orkas-VideoStudio

    The "ingest + plan" half of end-to-end video orchestration — ingest the user's material from evidence, then decompose intent into ONE cross-modal EDL (plan.json: edit/generate/compose/provided…

    499 GitHub stars~4k tokensUpdated 19 days ago
    Auto-check passed
  • Frontend Design

    Orkas-AI/Orkas-VideoStudio

    Aesthetic direction for OrkasVideoStudio HTML and motion-graphics compositions.

    499 GitHub stars~4.3k tokensUpdated 19 days ago
    Auto-check passed

Questions about Video Craft

What does Video Craft do?

The craft standard that makes a video GOOD, not just rendered — hooks, story pacing, visual hierarchy, type & safe zones, motion/easing, captions, audio mix, platform conventions, shot language…. Video Craft is an agent skill from Orkas-AI/Orkas-VideoStudio. The craft standard that makes a video GOOD, not just rendered — hooks, story pacing, visual hierarchy, type & safe zones, motion/easing, captions, audio mix, platform conventions, shot language, generation-prompt writing, and a pre-publish review.

When should I use Video Craft?

Video Craft fits situations like: before scripting/storyboarding/composing/generating/editing on EVERY line; again as the final review; do NOT trigger for tool mechanics (use the matching stage skill).

How do I install Video Craft in Claude Code?

Run `npx skills add Orkas-AI/Orkas-VideoStudio --skill video-craft -a claude-code`. Or copy the skill folder (packages/skills/video-craft in Orkas-AI/Orkas-VideoStudio) into .claude/skills/video-craft in your project. Claude Code loads it when a task matches its description.

How do I install Video Craft in Codex?

Run `npx skills add Orkas-AI/Orkas-VideoStudio --skill video-craft -a codex`. Or copy the skill folder (packages/skills/video-craft in Orkas-AI/Orkas-VideoStudio) into .agents/skills/video-craft in your project. Codex loads it when a task matches its description.

Can I use Video Craft in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Orkas-AI/Orkas-VideoStudio --skill video-craft -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/video-craft, .gemini/skills/video-craft, .github/skills/video-craft and .opencode/skills/video-craft in your project.

What does Video Craft need to run?

SKILL.md names no scripts, command-line tools or credentials: Video Craft is instructions for the agent only.

Does Video Craft access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Video Craft safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Video Craft use?

Video Craft is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Video Craft use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 928 tokens, read only when the agent opens those files.

What are the alternatives to Video Craft?

Skills that share tags, products or a category with Video Craft: Clean Cut (hassancs91/claude-youtube-editor, 328 stars), Video Production (ffroliva/gflow-cli, 278 stars), AI Video Script (zrt-ai-lab/opencode-skills, 287 stars) and Videodb Skills (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Video Craft?

Orkas-AI (a GitHub user) maintains it in Orkas-AI/Orkas-VideoStudio, which has 499 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 22, 2026.

Source: Orkas-AI/Orkas-VideoStudio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.