Claude skills by @johannships
I build AI agents for companies and post the setups that work as reels on
@johannships. This repo is the Claude side of that:
the editing skills behind my own videos, the business and writing skills I
use day to day, every skill from my "Claude just killed..." reels, and the
CLAUDE.md my main session runs from. Private details are taken out.
Free and MIT licensed (humanizer keeps its own MIT licence, see the writing folder).
The full pipeline: idea -> script -> record -> "DJI is in" -> edit -> trial post -> scorecard
This is the whole content process I run, one skill per step. Install the eight folders below, record, plug the
camera card in, tell Claude "DJI is in" (any camera card works), and it gets the footage, sorts it, edits it and
posts the trial reels. You approve the ideas, film, and tap "Share to everyone" on the winners.
| # | Step | Skill | What you get | You do |
|---|
| 1 | Idea | reel-ideation | top creators in your niche, their recent virals with proof (likes, views, link, multiple of their own median), your voice-dictation dumps split into numbered ideas | pick the ideas |
| 2 | Script | reel-ideation + script-polish | word-for-word scripts copying a proven format (never its words), 3 hooks of different types each, both CTA endings, a RECORD-SHEET.md | answer the one-word questions |
| 3 | Record | RECORD-SHEET.md | the order to film in, slates to say, checks between setups | film |
| 4 | "DJI is in" | footage-ingest (uses use-local-whisper) | clips copied and size-checked, audio == video on every clip, transcripts, takes matched to scripts, best takes picked, mirror + 30 fps conform, card ejected, TAKE-MAP.md | plug the card in |
| 5 | Edit | edit-style | 1080x1920 reels: face from frame 1, official logos, real UI, captions on every word, no dead air at joins, an Instagram ending and a link-in-bio ending, gates on the final files | look at the contact sheet |
| 6 | Captions | reel-captions | per-platform post text, keyword CTA on Instagram only, bio line elsewhere, checked by a script | nothing |
| 7 | Trial post | trial-post | Instagram Trial Reels + TikTok via the Zernio MCP connector, every safety check, adapter for other schedulers | nothing |
| 8 | Scorecard | reel-scorecard | at 72 h: which hook won each idea, what to graduate, kill or retire | tap "Share to everyone" on the winner |
Install just the pipeline (Claude Code):
git clone https://github.com/jsath/claude-skills.git
for s in social/reel-ideation video/script-polish video/footage-ingest video/use-local-whisper \
video/edit-style video/reel-captions social/trial-post social/reel-scorecard; do
cp -r "claude-skills/skills/$s" ~/.claude/skills/
done
What runs where: steps 1, 2, 6 and 8 work in any chat (Claude.ai or ChatGPT) if you paste links, numbers and
transcripts. Steps 4, 5 and 7 need Claude Code on the computer the card is plugged into: a chat app cannot read a
card, run ffmpeg or Whisper, or call the Zernio connector with the checks around it. Each skill lists its own
requirements and a setup check.
Setting this up for your own channel? Point your AI at this README and ask it to compare your current setup with
the table above, step by step, and install what is missing.
What's inside
What's inside
CLAUDE.md my orchestrator setup, as a template to copy
categories.json which folder each skill lives in (scripts/organize_skills.py reads it)
skills/<category>/<name>/ video, social, writing, business, web, dev
SKILL.md what Claude reads and follows
scripts/ or tools/ the code the skill runs (editing, SEO, security, PDF...)
templates/ starter files the skill copies into your folder
references/ deeper notes the skill loads when it needs them
agents/ reel skills only: one prompt per part, usable as Claude Code subagents
Install
Claude Code (needed for anything that touches video, scripts or a shell):
git clone https://github.com/jsath/claude-skills.git
cp -r claude-skills/skills/video/edit-style ~/.claude/skills/ # one skill
cp -r claude-skills/skills/video/* ~/.claude/skills/ # one category
cp -r claude-skills/skills/*/* ~/.claude/skills/ # or all of them
Copy the skill folders themselves into ~/.claude/skills/, not the category
folders: Claude Code looks for ~/.claude/skills/<name>/SKILL.md.
Use ~/.claude/skills/ for every project or .claude/skills/ for one. Start a
new session and ask for the job; Claude loads the skill when the request
matches its description. For the reel skills, copy agents/*.md into
.claude/agents/ if you want each part to run as its own subagent.
Claude.ai (web, desktop, mobile): zip one skill folder so the zip contains
the folder with SKILL.md inside, turn on code execution in
Settings > Capabilities, then upload it under Customize > Skills (on
Team and Enterprise plans an admin has to allow skills first). Skills marked
"Code" below need Claude Code; a chat cannot open or export video files.
The skills
Six folders, one per kind of job. Every skill keeps its own folder name, so
johann.fyi/go/claude-skills?s=<name> links still land on it.
Video: editing and repurposing (skills/video/)
The pipeline behind my videos runs in this order: footage-ingest ("the card is in": copy, sort, pick takes), use-local-whisper (transcribe), edit-style or longform-edit (edit), reel-captions (post text), thumbnail-generator (cover). Ideas, posting and the scorecard live in the social folder; the whole chain is in "The full pipeline" above.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
