Papercut Voice logo

Papercut Voice

Community
0xS4N4TG
papercut-voice

Voice a papercut reel and time it to the picture. Three paths, local Qwen3-TTS, your own recording or another TTS, or a placeholder voice. Covers delivery rules, voice.json, captions and scene timing. Use for "set up the voice", "re-voice this", "time the script".

Overview

Publisher0xS4N4TG
Repositorypapercut-explainer
Skill namepapercut-voice
Stars
106
Forks
10
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 0xS4N4TG on GitHub. Read the source before you install it.

Installation

Install the Papercut Voice 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/0xS4N4TG/papercut-explainer/tree/main/skills/papercut-voice
  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/0xS4N4TG/papercut-explainer.git /tmp/papercut-explainer
mkdir -p .claude/skills
cp -r /tmp/papercut-explainer/skills/papercut-voice .claude/skills/papercut-voice
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Papercut Voice 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 Papercut Voice 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 Papercut Voice 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.

Papercut voice

Every later stage needs two things in the narration folder: voice/final_narrator/<id>.wav (one WAV per script line) and timing_narrator.js (a start and end for every word). This skill produces them by one of three paths, then builds the captions and the scene plan. The full reference for the scripts is library/voice/README.md.

Preflight

  • Library: $PAPERCUT_LIB, else the PAPERCUT_LIB= line in ~/.config/papercut-explainer/config.env, else ask once. Export it, and . "$PAPERCUT_LIB/env.sh" loads ASR_PY, QWEN_TTS_PY and the other config values into the shell.
  • A scaffolded project (papercut-build, step 1) with narration/script.json and papercut/episode.json holding scenes. new_episode.sh copies build_timing.py into narration/.
  • If the user already has a TTS installed, use it as it is and don't rebuild it (path B, or A if it is Qwen3-TTS). Ask once which one and where it runs. Otherwise ask which path, and say what it needs:
PathNeedsInstall mode
A. Local Qwen3-TTSthe voice venv from library/voice/setup_tts.sh (model download 2.3-4.2 GB)Full
B. Your own recording or another TTSan ASR backend (mlx-whisper or faster-whisper) and librosa + numpy for the pitch pass, in the Python that ASR_PY and QWEN_TTS_PY nameFull, or those packages by hand
C. Placeholderffmpeg; macOS for --sayStandard

If the path needs more than the install has, run ./install.sh --doctor and hand over to papercut-setup. Without ASR, build_timing.py only estimates 2.75 words a second, so captions drift against real audio.

Path A: local Qwen3-TTS

From the series folder:

cp $PAPERCUT_LIB/voice/voice.example.json voice/voice.json     # once per series; edit it
$PAPERCUT_LIB/voice/narrate.sh voice/voice.json episodes/NN-slug/narration
$PAPERCUT_LIB/voice/finalize.sh voice/voice.json episodes/NN-slug/narration episodes/NN-slug/narration/voice/takes/narrator [num.json]
  • voice.json: speaker (CustomVoice: Aiden, Dylan, Eric, Ryan, Serena, Vivian, Sohee, Ono_anna, Uncle_fu) and instruct. Recommended: CustomVoice 1.7B, Ryan or Aiden, instruct "friendly, natural, conversational, like telling a friend; clear pauses between sentences; stress the key word of each line". takes_per_line defaults to 3. tempo stays 1.0 (other values need rubberband). qa_targets set the pitch range and the ASR match (0.9).
  • A script line can carry tts (respelled text for pronunciation; captions keep text) and its own instruct. num.json maps numerals to spoken words ({"13,000": "thirteen thousand"}) so ASR matching doesn't fail on digits.
  • Run one TTS process at a time; the 1.7B model is memory-hungry.
  • finalize.sh runs ASR and pitch on every take, picks one per line, trims, loudness-normalises to -16 LUFS, re-runs ASR on the finals and writes timing_narrator.js. After listening, put corrections in voice/picks_override.json ({"l3_name": 2}) and rerun with SKIP_PICK=1.
  • Voice Design (describing a voice in words) is a Qwen3-TTS mode that narrate.py doesn't drive. Generate with it elsewhere and use path B.

Path B: your own recording or another TTS

  • Put one WAV per line in voice/final_narrator/<id>.wav, or raw takes as voice/takes/narrator/<id>_<k>.wav and run finalize.sh as above.
  • For finished lines, transcribe them, write voice/chosen_narrator.json as {id: "voice/final_narrator/<id>.wav"}, then from narration/:
$ASR_PY $PAPERCUT_LIB/voice/asr.py voice/final_narrator/*.wav > voice/asr_narrator_final.json
CHOSEN=voice/chosen_narrator.json TIMING_OUT=timing_narrator.js python3 build_timing.py voice/asr_narrator_final.json

Path C: placeholder

From the narration/ folder:

python3 $PAPERCUT_LIB/tools/placeholder_vo.py [--wps 3.0] [--say [VOICE]]

It writes silent WAVs (or the macOS say voice with --say) and timing_narrator.js from script.json alone, spreading word times by word length. --wps 3.5 to 4 approximates the target pace (default 3.0). The reel can be built and timed first and re-voiced later: swap the WAVs, rerun finalize.sh, rerun build_vo.py, and the word cues follow.

Delivery rules

Delivery is human, unhurried and emphasised. The viewer must follow every line on the first listen.

  • Breathing room. A real pause at every sentence end and between list beats ("Fine. Fine. Fine."). Start with 0.3-0.4 s between lines (gap in episode.json, default 0.22; gaps adds an extra beat after one named line) and judge by ear. Pauses go at sentence or clause boundaries only: a 0.2 s gap inside a phrase, such as "copied it, | by taking...", reads as lag. Use the 30 s ceiling for air instead of cutting pauses, and never slow the tempo to get it.
  • Emphasis. The one or two words each line leans on (the number, the twist word, the verdict) come from the script's staging table. Pass them as a per-line instruct.
  • Tone. Conversational and a little amused, not announcer energy. Questions sound like real questions, the catch line sounds curious, the CTA is warm. The narrator still doesn't joke; the picture does.
  • Clone model (no instructions). With a clone voice (ref_audio + ref_text, Base model) the levers are the text and the take. Write the pauses into the punctuation (full stops between list beats, a short question as its own sentence). Generate several seeds of one continuous take (SEED_BASE, takes_per_line), pick the one with the most pitch movement on the target words and ASR 0.9 or better, and re-take a flat line alone (ONLY=l4_peak) and splice it at a sentence boundary. Only clone a voice you have the right to use.
  • Whole script at once gives consistent prosody: generate one take, split_take.py cuts it per line, then set "gap": 0 in episode.json. Per scene is fine if the user prefers.
  • Play the first three lines to the user before the full run: ONLY=l1_hook,l2_...,l3_... narrate.sh ....

Captions and timing

From papercut/, once episode.json has scenes:

python3 $PAPERCUT_LIB/tools/build_vo.py     # public/vo/voiceover.wav, public/vo/captions.json, src/plan.json
python3 $PAPERCUT_LIB/tools/timing_md.py    # Timing section of STORYBOARD.md

captions.json is a Remotion Caption[]; scene boundaries come from the word timestamps; the composition length is plan.json's durationInFrames. build_vo.py flags any scene under 1.2 s. With no library, transcribe the WAV with the Remotion captions skill (whisper.cpp) or any speech-to-text tool that returns word timestamps.

Captions are one torn tag per word, pages of 1-3 words, at 3.5-4 words a second (../papercut-explainer/references/style-guide.md, sections 11 and 13).

Hand-off

Next is papercut-build (stubs, scenes, sound, render). It reads src/plan.json and the Timing section of papercut/STORYBOARD.md. Any later voice change reruns build_vo.py and timing_md.py; the scene cache then re-renders everything.

Frequently asked questions

What does the Papercut Voice AI skill do?

Voice a papercut reel and time it to the picture. Three paths, local Qwen3-TTS, your own recording or another TTS, or a placeholder voice. Covers delivery rules, voice.json, captions and scene timing. Use for "set up the voice", "re-voice this", "time the script".

Why use Papercut Voice on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/0xS4N4TG/papercut-explainer/tree/main/skills/papercut-voice. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Papercut Voice?

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 Papercut Voice?

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

Is the Papercut Voice AI skill free?

Yes. It is published on GitHub by 0xS4N4TG 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 👇