video
Skill6 starsChanged 12 days agoMITView on GitHub
The front door of the short-video pack. The user says what they want ("monte ma vidéo", "la suite", "publie-la", "edit my video", "what's next") and this skill does two things - it finds the video already in progress (from the <name>.state.json file that `edit` leaves next to every video) so nothing starts over, and it hands the request to the one skill that does the job (setup, edit, clips, audit, outliers, script, publish). It never edits, writes or publishes on its own. Use when the user types /short-video, says "monte ma vidéo", "reprends ma vidéo", "où j'en suis", "la suite", "audite mon compte", "écris-moi un script", "publie-la", "edit my video", "pick up my video", "what's next", "publish it", or is not sure which skill of the pack to use.
63 other projects use a version of this.
Adopted by
Most recently taken up by
- vincentventalon/my-claude-skillsword for word, first seen Nov 15, 2026
- 1999AZZAR/designer-mcptheir own version, first seen Nov 13, 2026
- 1999AZZAR/the-designertheir own version, first seen Nov 13, 2026
- guaardvark/guaardvarktheir own version, first seen Nov 13, 2026
- xeroc/skillstheir own version, first seen Nov 4, 2026
- letsloose501/sqs-agent-memorytheir own version, first seen Nov 3, 2026
Used with
Projects with it also use popups, co-marketing and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 22 projects that use this
CesarjoquinSkillco-marketing
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.
Also in 24 projects that use this
coreyhaines31Skillmarketing-council
When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.
Also in 17 projects that use this
ukunal91appSkillcommunity-marketing
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel.
Also in 26 projects that use this
roerohanSkillemails
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
Also in 19 projects that use this
- +6 more from Cesarjoquin
Other versions63 projects use a version of this.
Word for word · 1
- vincentventalon/my-claude-skills★ 6100% same
Edited · 0
None found.
Wrote their own version · 62
- coreyhaines31/marketingskills★ 61ksame name
- runesleo/x-reader★ 990same name
- Nexus-JPF/note-companion★ 874same name
- smixs/visual-skills★ 635same name
- iBigQiang/feedgrab★ 622same name
- guaardvark/guaardvark★ 320same name
- ohad6k/emulo★ 292same name
- Cesarjoquin/Marketing-Skills★ 190same name
- guimatheus92/mcp-video-analyzer★ 125same name
- Rylaispirit/rylai-codex-hermes-skills★ 56same name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- competitorsSkill
- internal-linksSkill
- keywordsSkill
- search-consoleSkill
- seo-auditSkill
- auditSkill
- clipsSkill
- editSkill
- outliersSkill
- publishSkill
- scriptSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 53 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If they ask for "the next step", work out what it is from the video's state.
- Distinctive: line 66
When the user asks for "the next step", "la suite", "what's next" about a video found in step 1, the state answers:
“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Video: the front door
This skill is a dispatcher. The short-video pack has seven skills that do the
work (setup, edit, clips, audit, outliers, script, publish);
this one only decides which video the user is talking about and which
skill does what they ask, then hands over. It has no method of its own:
never edit, write or publish here. Talk in the user's language.
Three jobs, in this order:
- Find the video in progress (so the user never starts over).
- If they ask for "the next step", work out what it is from the video's state.
- Pick the skill and hand over.
1. Find the video in progress
Most requests are the next step of a video already under way. Look before choosing:
- This conversation already works on a video (a clip just edited, a script just written, boards just proposed): that is the one. Apply the change with the skill already in use, running its step again with the same files.
The state files.
editwrites<name>.state.jsonnext to every video it makes. List the newest ones in the output folder (output_dirin~/.config/video-editing/config.json, else~/Videos/edited) and in the current folder:ls -t "<output_dir>"/*.state.json ./*.state.json 2>/dev/null | head -5- The request names a video (its name, a clip, a word of its title): that one.
- It says "my video", "it", "the last one", "la suite": the newest.
- Two or more fit and nothing tells them apart: ask one question, listing
them (name, title, date of
steps.edit.done).
- Nothing found: a new video.
Tell the user in one line which video you pick up and where it is ("I pick up IMG_4127, edited today at 18:02, not published yet").
What a state file holds
<name>.state.json, one per video, next to it. edit writes it at each run;
the other skills only add their own step under steps and never remove
anything.
| key | what |
short-video | the name (<name>.mp4 is the video to post) |
clips | the raw clips, absolute paths, in order |
command | the exact command of the last edit: run it again, plus the new option, for any change |
final | the 9:16 to post |
duration, lang, title, boards | the edited length, the language, the title on screen, the boards file |
steps.edit | done (date), rough (only the cut) |
steps.publish | written by publish: kit (path of post.md) or nadia (the posts: platform, date, id), and status (kit, scheduled, posted) |
2. "What's next?"
When the user asks for "the next step", "la suite", "what's next" about a video found in step 1, the state answers:
| the state says | next |
no ~/.config/video-editing/config.json | setup first (at least its diagnostic), then the edit |
steps.edit missing, or rough: true | edit |
edited, a title but no boards | offer boards (edit, "mets des cartons"), or go on to publishing; the user chooses |
edited, no steps.publish | publish |
steps.publish.status is scheduled | say when it goes out, platform by platform; nothing to do |
steps.publish.status is kit | ask whether it is posted; yes = publish records it |
3. Which skill does the job
| the user wants | skill |
| to install, tools, whisper or ElevenLabs, a missing ffmpeg or yt-dlp, "les sous-titres ne s'incrustent pas", a setting (language, output folder) | setup |
| clips edited, "monte", "coupe", subtitles, title, boards, "plein cadre", "split", a change on a video already edited ("garde la pause", "c'est cloud pas clown") | edit (asked before any setup: setup first) |
| a long video cut into shorts: a YouTube link, a podcast, "découpe ma vidéo en shorts", "repurpose", "clips from my video" | clips (it edits each clip with edit) |
| to know what works on their own TikTok, their profile link (TikTok only: an Instagram account is told so) | audit |
| to know what blew up on other accounts, "ideas to remake", an @account to dig | outliers |
| a script, a hook, a topic or an anecdote to turn into a video | script |
| to post or schedule, "publie-la", "mets-la en ligne", a caption, hashtags | publish |
| still unclear | ask one question, no more |
The whole chain, for reference: setup (once) → audit (your account) →
outliers (your niche) → script (script.md, with a "Pour le montage"
block: title, end card, length) → record → edit (<name>.mp4) →
publish. A script.md in the current folder gives edit its title
(titre) and end card: pass them along.
Google Search Console is not a video job: that is the search-console skill
of the SEO pack.
4. Hand over
Invoke the target skill with the Skill tool (its name; installed as a plugin,
the name may carry the plugin's prefix, short-video:edit). If that is not
possible, read ../<skill>/SKILL.md (the skills are installed next to this
one) and follow it exactly as if the user had asked it directly. Pass on the
user's words and the video found in step 1 (its clips, its command).
Say in one line which skill you picked and for which video, then hand over. From there, the target skill's rules apply, and its end state is yours.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

