editor-captions
Skill19 starsChanged 29 days agoMITView on GitHub
Use when adding or restyling captions in the Scrollmark editor, one word at a time (the default for "Add captions" and "Cut this for TikTok" on a talking-head video) or in short three-word chunks.
In this repository23 other files it gives its agents.
- agent-interviewSkill
- audio-acquisitionSkill
- brand-kitSkill
- content-autopsySkill
- edit-handoffSkill
- editor-beat-syncSkill
- editor-camera-directingSkill
- editor-motion-graphicsSkill
- editor-plan-and-checkSkill
- editor-sfx-sparseSkill
- editor-soundtrackSkill
- editor-versionsSkill
- hook-anatomySkill
- media-acquisitionSkill
- platform-fluencySkill
- read-the-roomSkill
- repurpose-engineSkill
- studio-setupSkill
- subject-compositingSkill
- trend-radarSkill
- video-formatsSkill
- video-productionSkill
- voice-matchingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Never phrase (8-word lines), never phrase-plus-word (an extra word track), and never captions_generate: it makes sequential chunks without …
- Distinctive: line 21
After the recut, or on a timeline that already has the keep list:
- Very specific: line 31
Do not use tiktok, creator-classic, sticker-box, cinematic, yellow-punch, meme-loud, or active-word unless the user names that look.
- Very specific: line 34
If captions already exist with role word, captions_resync.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Editor Captions
Requires
A running Scrollmark editor whose commands you can call: the SocialGPT editor chat, or scrollmark mcp from @scrollmark/cli for a coding agent. Without it the steps below can't run; the kit-by-vibe list is still a fair guide to choosing a caption look in any editor.
Pick the rhythm
- One word at a time (default):
captions.applyRhythmwithmode: "word". - Three-word chunks, when the user wants chunks rather than single words:
captions.applyRhythmwithmode: "sequential"andwordsPerCaption: 3.
Never phrase (8-word lines), never phrase-plus-word (an extra word track), and never captions_generate: it makes sequential chunks without the rhythm you chose.
Steps
After the recut, or on a timeline that already has the keep list:
- The rhythm op above, then
captions.applyPresetwithkitId,sizeandplacement: as two ops in onetimeline_applyPlan, or ascaptions_applyRhythmandcaptions_applyPresetoutside a plan. Pick one
kitIdfrom this set. Choose from the footage (transcript, setting, what they are selling). Do not callcaptions_listPresetsjust to browse.handwritten— casual talking-head, lifestyle, personal story, home or messy settingsoft-promo— product, beauty, UGC, "check this out" energypodcast-plate— interview, seated conversation, darker or serious talkclean-minimal— default if unsure; explainer, professional, clean talking-head
Do not use
tiktok,creator-classic,sticker-box,cinematic,yellow-punch,meme-loud, oractive-wordunless the user names that look.- Size:
sfor word captions, since atmlong words clip on a vertical video;morlonly when the user asks for bigger captions. - Placing for a platform (the user named one, or the editor's safe zone shows one): pass the same
platformtocaptions.applyRhythmand tocaptions.applyPreset. The preset recomputes where captions sit, so leaving it out of either call puts them back under the platform's caption block. Then check that platform withqc_run(checks: ["document"]) and fix what it finds withqc_applyFix. - If captions already exist with role
word,captions_resync. It keeps their kit, colour and size, so do not apply a preset afterwards unless the user asks for a different look.
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.

