Clip Machine logo

Clip Machine

Community
Enriquemarq1
clip-machine

Turn ONE long video into native TikTok + Reels + Shorts posts — the four stations: CUT (word-level transcript, best moments, 9:16 reframe), CAPTION (burned word captions + per-platform caption text), COVER (per-platform cover rules), POST (one Zernio request per clip). Use when the user hands a long video and wants short clips selected, produced, and published natively everywhere. Triggers: 'run the clip machine', 'turn this video into clips', 'repurpose this video', 'post clips to tiktok reels shorts'.

Overview

PublisherEnriquemarq1
Repositoryzernio-library-skills
Skill nameclip-machine
Stars
50
Forks
13
Bundled files
3
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.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Clip Machine 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/Enriquemarq1/zernio-library-skills/tree/main/.claude/skills/clip-machine
  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/Enriquemarq1/zernio-library-skills.git /tmp/zernio-library-skills
mkdir -p .claude/skills
cp -r /tmp/zernio-library-skills/.claude/skills/clip-machine .claude/skills/clip-machine
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Clip Machine 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 Clip Machine 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 Clip Machine 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.

Clip Machine — one long video in, native posts out

Four stations. Claude runs the first three, Zernio ships the fourth. No timeline software ever opens.

LONG VIDEO → [1 CUT] → [2 CAPTION] → [3 COVER] → [4 POST] → native posts live

The math this kills: 1 video → 3 clips × 3 platforms = 9 manual uploads, every week, forever. With the machine it's 3 requests.

Starting from zero? Copy-paste reference/initiation-prompt.md to Claude Code in an empty folder — it sets up the whole system for you.

STATION 1 — CUT

  1. Transcribe with word timestamps. WhisperX is the reference model — open source, free, runs on your machine (pip install whisperx, needs ffmpeg): whisperx video.mp4 --model large-v3 --output_format json The JSON gives every word a start/end timestamp via forced alignment (GPU: add --device cuda; CPU works with --compute_type int8). Any word-level transcription service works too — the machine only needs words with millisecond timing. No ground truth, no clean cut.
  2. Pick the best moments with the selection framework in reference/best-moments-prompt.md. That file IS the prompt — paste it with the transcript. Core law: finish the point — a clip starts at the beginning of a thought and ends after the payoff, never mid-sentence.
  3. Cut on word boundaries. Start ~0.15s before the first word, end ~0.25s after the last (never past the next word's start). ffmpeg: ffmpeg -ss {start} -to {end} -i long.mp4 -c:v libx264 -crf 18 -c:a aac clip.mp4
  4. Reframe to 9:16 (1080×1920). Crop to the speaker (face-tracking via MediaPipe if available; a fixed crop works when the framing is static). Screen-share sources: stack the screen crop on top, the face cam below.

STATION 2 — CAPTION (there are TWO captions — that's the teach)

  1. Burned-in word captions on the video. Most people watch muted. Word-synced from the transcript timestamps (that's why Station 1 needs millisecond words), 3-4 words per line, high-contrast, inside the caption-safe band (keep out of the bottom ~20% and top ~12% — platform UI lives there).
  2. Caption TEXT per platform — never the same text three times. Copy-pasting one caption everywhere is the amateur tell. Claude writes all three from the transcript:
    • TikTok: conversational hook + 3-5 niche hashtags.
    • Reels: the first ~125 chars must stop the scroll (that's all that shows before "...more").
    • Shorts: barely displays text — put the value in the TITLE instead. Full rules per platform: reference/platform-cheat-sheet.md.

STATION 3 — COVER

The first impression is platform-specific — one cover does not fit all:

  • Reels: the grid shows a 1:1 CENTER crop of your cover. Title text must live inside the center square or it gets amputated.
  • TikTok: pick the cover frame + big readable cover text (profile grid is how binge-viewers navigate).
  • Shorts: pulls a frame — make frame 0 count (cover-as-first-frame: the cover IS frame 0, the video starts on frame 1; no 1-second intro card — it kills retention). Details and dimensions: reference/platform-cheat-sheet.md.

STATION 4 — POST (the one-request money shot)

One request per clip through Zernio — the video + the per-platform captions

  • the platform list. Zernio uploads NATIVE to each platform (platforms bury links and reward native uploads — that's the whole reason the treadmill exists).
json
POST https://api.zernio.com/api/v1/posts
{
  "title": "Clip title (YouTube uses this)",
  "content": "fallback caption",
  "mediaItems": [{ "type": "video", "url": "https://.../clip.mp4",
                   "filename": "clip.mp4", "mimeType": "video/mp4" }],
  "platforms": [
    { "platform": "tiktok",    "accountId": "...", "customContent": "TikTok caption + hashtags",
      "platformSpecificData": { "privacy": "PUBLIC_TO_EVERYONE" } },
    { "platform": "instagram", "accountId": "...", "customContent": "Reels caption, hook in line 1" },
    { "platform": "youtube",   "accountId": "...", "customContent": "Shorts description",
      "platformSpecificData": { "title": "Value-first title #Shorts", "visibility": "public",
                                 "categoryId": "27", "madeForKids": false } }
  ],
  "scheduledFor": "2026-08-20T18:30:00Z"
}

Media upload for local files: POST /v1/media/presign → PUT the file → use the returned publicUrl in mediaItems. The full publishing flow (approval gates, scheduling, verification) lives in the zernio-publish skill — this station rides it.

Hard-won gotchas:

  • Post platforms SERIALLY, never two multi-platform posts in parallel.
  • A timeout does NOT mean the post wasn't created — GET the post before retrying (blind retries create 409s or duplicates).
  • Space clips out: 1-2 per day beats 9 in one hour.

The loop

Clips point viewers to the long video. The long video feeds the machine. Every clip carries an end-card or caption line back to the source — the machine is a circle, not a pipe.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Clip Machine AI skill do?

Turn ONE long video into native TikTok + Reels + Shorts posts — the four stations: CUT (word-level transcript, best moments, 9:16 reframe), CAPTION (burned word captions + per-platform caption text), COVER (per-platform cover rules), POST (one Zernio request per clip). Use when the user hands a long video and wants short clips selected, produced, and published natively everywhere. Triggers: 'run the clip machine', 'turn this video into clips', 'repurpose this video', 'post clips to tiktok reels shorts'.

Why use Clip Machine on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Enriquemarq1/zernio-library-skills/tree/main/.claude/skills/clip-machine. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Clip Machine?

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 Clip Machine?

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

Is the Clip Machine AI skill free?

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