- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill launch-video -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill launch-video -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill launch-video -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add dzhng/skills --skill launch-video -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/dzhng/skills/tree/HEAD/skills/graphics/launch-videoFrom the publisher
The bar is a showreel: the piece a motion designer puts on their résumé to prove how good they are — dynamic, ambitious, scored to music, a real professional production and never a demo or prototype. Go all out. The repo supplies the story; the craft is yours. Nothing here is a template: if the piece could be re-skinned for any other project, it has failed.
Lead with the product and a few memorable benefits. Keep methodology, sample sizes, missing-data allowances, benchmark caveats and source citations in the package README or linked report, not in the video or key art. Do not add fine print, asterisk footnotes, disclaimer blocks or defensive narration. If a claim needs narrowing to stay true, narrow the headline itself; never use tiny text to rescue a misleading headline. Review each frame for reading burden as well as visual quality.
Text is the last resort. Before any word goes on screen, find the picture that makes it unnecessary: an object that transforms, a world that changes, motion that performs the idea. Keep text only where nothing visual can carry it: the product's real commands, its name, and a claim that must be exact. The one exception is orientation: give each shot one header saying what is happening (it can be dynamic, like a live count that ticks with the action), or the best animation reads as random motion. When a draft leans on labels, captions, or subtitles to explain what is happening, redesign the shot instead of rewording the text.
Would a motion designer put this shot on their reel? Tells that it has slid into explainer or demo:
Make a showreel-grade motion-graphics launch video, with music, that introduces a CLI, library, or product from its repo. Use when asked for a launch, promo, sizzle, or showreel video, an animated int
---name: launch-videodescription: Make a showreel-grade motion-graphics launch video, with music, that introduces a CLI, library, or product…---# skills/graphics/launch-video/SKILL.mdOverview
Make a showreel-grade motion-graphics launch video, with music, that introduces a CLI, library, or product from its repo. Use when asked for a launch, promo, sizzle, or showreel video, an animated intro for a project, or a video to post on X/social.
FAQ
Download skills/graphics/launch-video/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/dzhng/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.