editorial
Skill4 starsChanged 9 days agoMITView on GitHub
Editorial — Magazine-style kinetic captions synced to a voice-over, with masthead, section counter and tags. Renders a video with the rudywizz-motion engine. Use when the user asks for this look by name.
- Installs packages
8 other projects use a version of this.
Adopted by
Most recently taken up by
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- futhr/futhrtheir own version, first seen Oct 27, 2026
- zdresearch/p3ntheir own version, first seen Oct 25, 2026
- x77jh8gvrn-alt/staqd-skillstheir own version, first seen Oct 20, 2026
- lachinovedhem/standards-mcptheir own version, first seen Oct 11, 2026
- SkotAlexsander/skillstheir own version, first seen Sep 16, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- bergside/awesome-design-skills★ 2.9ksame name
- zdresearch/p3n★ 5same name
- SkotAlexsander/skills★ 1same name
- futhr/futhr★ 0same name
- hemal08ce094/DesignSkillsSwiftUI★ 0same name
- lachinovedhem/standards-mcp★ 0same name
- matheusflorindo32/apex-elite-framework★ 0same name
- x77jh8gvrn-alt/staqd-skills★ 0same name
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 repository43 other files it gives its agents.
- bar-chartSkill
- beat-cutSkill
- captionsSkill
- card-carouselSkill
- chat-storySkill
- countdownSkill
- cta-followSkill
- cube-spinSkill
- doodle-storySkill
- extrude-3dSkill
- glitch-titleSkill
- halftone-pressSkill
- highlight-quoteSkill
- history-titleSkill
- history-videoSkill
- inflateSkill
- ink-bleedSkill
- led-marqueeSkill
- lower-thirdSkill
- lyric-videoSkill
- map-routeSkill
- murmurationSkill
- neon-signSkill
- odometerSkill
- orbit-ringSkill
- parchment-letterSkill
- particle-sphereSkill
- pixel-questSkill
- presenterSkill
- receiptSkill
- reelSkill
- retro-gridSkill
- roomSkill
- rudywizz-motionSkill
- scrambleSkill
- signal-tuneSkill
- split-flapSkill
- story-3dSkill
- text-tunnelSkill
- ticker-rowsSkill
- typewriterSkill
- vhs-memorySkill
- word-stackSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read $RM/SKILL.md once for setup, the workflow (check stills → render → verify) and the full catalogue.
- Very specific: line 20
Put the user's text in single quotes (write '\'' for an apostrophe inside it) so the shell never interprets it.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Editorial
Magazine-style kinetic captions synced to a voice-over, with masthead, section counter and tags.
Find the engine (the sibling rudywizz-motion skill folder) and a temp folder both bash and Node agree on:
RM="${CLAUDE_SKILL_DIR}/../rudywizz-motion"
[ -f "$RM/engine/cli.mjs" ] || RM=$(ls -dt "${CLAUDE_PLUGIN_ROOT}/skills/rudywizz-motion" ~/.claude/plugins/cache/*/rudywizz-motion/*/skills/rudywizz-motion ~/.claude/skills/rudywizz-motion .claude/skills/rudywizz-motion 2>/dev/null | head -1)
TMP=$(node -p "require('os').tmpdir()")
(cd "$RM" && node -e "require.resolve('playwright')" 2>/dev/null) || (cd "$RM" && npm install --no-audit --no-fund) # first run onlyRead $RM/SKILL.md once for setup, the workflow (check stills → render → verify) and the full catalogue.
Put the user's text in single quotes (write '\'' for an apostrophe inside it) so the shell never interprets it.
Render (the user's text — $ARGUMENTS — goes in --text; default "Every word lands on time. / Captions that read like a magazine."):
node "$RM/engine/cli.mjs" still editorial --text '<text>' --at 4 --size 540 --out "$TMP/editorial-check.png" # look at it first
node "$RM/engine/cli.mjs" render editorial --text '<text>' --out editorial.mp4Options (--set key=value, JSON values allowed):
lines— Timed lines: [{ who, at, text, voice }]. word = hero word (otherwise the longest word is). The voice file times the words and is played (see mixVoices)text— Without lines: phrases separated by " / " shown one after anothermasthead— Masthead text (top left); "" hides the mastheadsections— Section counter: [{ at, title }] → "03 / 11 TITLE" top righttags— Labels: [{ from, to, text, label }] e.g. { label: "STYLE", text: "neon-sign" }zones— Caption position over time: [{ at, pos: top | middle | bottom }]pos— Default caption positionaccent— Hero word colourmixVoices— false when the scene already plays the voicesspeakers— Show the speaker tag above each phrase
Combine freely with --camera, --grade, --bloom, --leak, --film, --format 1:1|4:5|16:9, --audio, --alpha --out x.mov.
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.

