Captions logo

Captions

Community
appariciojunior
captions

Clean, readable burned-in style subtitles from the verbatim transcript - stutters and fillers removed, spoken slang written correctly, one short line at a time, names checked, every line read by Claude before import into DaVinci Resolve. Use for "subtitles", "captions", "legendas", or when the creator reports wrong words in the captions.

Overview

Publisherappariciojunior
Repositoryvideo-editor-skills
Skill namecaptions
Stars
360
Forks
50
Bundled files
Instructions only
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 appariciojunior on GitHub. Read the source before you install it.

Installation

Install the Captions 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/appariciojunior/video-editor-skills/tree/main/skills/captions
  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/appariciojunior/video-editor-skills.git /tmp/video-editor-skills
mkdir -p .claude/skills
cp -r /tmp/video-editor-skills/skills/captions .claude/skills/captions
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Captions 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 Captions 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 Captions 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.

Captions

Goal: people watching on mute can follow; the captions are just there, never in the way.

Source

The verbatim transcript mapped onto the current timeline (follow the creator's trims), not Resolve's own auto-captions (a second, less accurate transcription). Drop words on B-roll (radio lyrics, background talk).

Clean, not verbatim

Captions show what they mean, written correctly:

  1. Stutters: "pro-product" → "product", "da-da," → "da,".
  2. Cut-off words: "es--", "A--" → gone.
  3. Filler sounds: drawn-out "uuum", "hããã", "ééé" → gone. Careful with real words that look like fillers ("um" = "a" in Portuguese, "é" = "is").
  4. Self-corrections: "get a, an appointment" → "get an appointment".
  5. Spoken short forms → correct written forms, if the creator asks. Brazilian Portuguese example: cê/cês → você/vocês, tá → está, tô → estou, tava → estava, tamo → estamos, vamo → vamos, pra/pro → para/para o, né → não é, "o que que" → "o que", "por que que" → "por que", "tu consegue" → "você consegue"; "tão" → "estão" only before a verb in -ndo ("tão bonito" stays). Keep expressions and swear words (fix grammar, not voice). Keep capital letters at sentence starts when you shorten.
  6. Names and spellings checked on the web (transcripts garble product names), and the creator's own name exactly as they write it.
  7. Don't reveal what the creator wants kept secret (a place, a company) even if they say it.

Keep two lists: global rules (word map + phrases) in config, per-video fixes in caption_fixes.json. Apply phrase fixes after the word map.

Lines

  • One line, max 42 characters; a sentence's last word may stretch it to ~50 rather than sit alone.
  • New cue at a pause ≥ 0.6 s, at sentence ends (if the line is already substantial), or after 3.2 s.
  • Min 0.9 s on screen, end 0.25 s after the last word, never overlapping the next.
  • A lone small word after a pause ("que", "vai", "not") joins the next line. Single-word cues are fine only when they stand alone ("Calm down.", "Bye.").
  • First cue starts at 00:00:00,000 (Resolve's import shifts everything relative to the first cue).
  • Write a new file name per version (captions_v3.srt).

Read every cue

Print every line and actually read it before handing it over. Grep for leftover short forms, double punctuation (",,"), lowercase after a full stop, words lost by your own filters. Fix rules, regenerate, read again.

Into Resolve

The creator imports with File > Import > Subtitle (the API places subtitles after the timeline end; a workaround crashed Resolve). Delete the old subtitle clips but keep the track so its style stays.

Style

Record the creator's style once (font, size, position, shadow) from their timeline and save it in config as the house style, e.g. a light sans at size 68, centred ~11% up from the bottom, soft drop shadow. Overlays must stay out of that band (see motion-overlays).

Frequently asked questions

What does the Captions AI skill do?

Clean, readable burned-in style subtitles from the verbatim transcript - stutters and fillers removed, spoken slang written correctly, one short line at a time, names checked, every line read by Claude before import into DaVinci Resolve. Use for "subtitles", "captions", "legendas", or when the creator reports wrong words in the captions.

Why use Captions on TypingMind?

Because you install it once and use it with any model. Captions 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 Captions in TypingMind?

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

Which AI models can use Captions?

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 Captions?

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

Is the Captions AI skill free?

It is published on GitHub by appariciojunior. Check the repository for licensing terms. 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 👇