nexu-io/openmotion / library/skills/openmotion-presenter-story
openmotion-presenter-story
VerifiedOpenMotion — Adapt presenter-led videos using reusable motion design recipes for listicles, workflow demonstrations and product walkthroughs. Use with the creator's own footage and measured speech timing to combine spoken storytelling, captions, screen recordings and motion.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| agents/openai.yaml | config | 56 B |
| assets/ali-abdaal-workflow-reference.mp4 | binary | 133 B |
| assets/ali-abdaal-workflow-result.mp4 | binary | 133 B |
| assets/careerwithriya-reference.mp4 | binary | 132 B |
| assets/careerwithriya-result.mp4 | binary | 133 B |
| assets/john-tagudin-capso-reference.mp4 | binary | 133 B |
| assets/john-tagudin-capso-result.mp4 | binary | 133 B |
| references/presenter-listicle/MOTION_DESIGN.md | markdown | 3.2 KB |
| references/product-walkthrough/MOTION_DESIGN.md | markdown | 3.1 KB |
| references/workflow-demo/MOTION_DESIGN.md | markdown | 3.2 KB |
references/workflow-demo/MOTION_DESIGN.md
View on GitHub# Workflow demonstration — MOTION_DESIGN.md
**Status:** reusable design recipe; no executable template or OpenMotion-generated comparison yet.
## Reference and creative intent
[5 tools I use every day — Ali Abdaal](../../assets/ali-abdaal-workflow-reference.mp4), catalog ID `hf-reference-aroll-ali-abdaal-workflow`, alternates a desk-side presenter with tool and document visuals. Its [upstream remix](../../assets/ali-abdaal-workflow-result.mp4) uses another presenter and a different design-workspace story. These are attributed catalog demonstrations, not results produced by this recipe.
Let the viewer understand both the person and the workflow: show the speaker for intent, the screen for evidence, and a short motion card for the takeaway. Each insert should answer the sentence immediately around it.
## Keep / replace
| Keep as a design principle | Replace for this episode |
| --- | --- |
| Presenter → tool detail → presenter cadence | Creator, workflow, narration and tool footage |
| Quiet captions and restrained emphasis | Actual words, logo, colors and screenshots |
| Clean transition from face to full-screen evidence | Insert content and its required reading time |
| Consistent card treatment and visual hierarchy | Brand assets and screen framing |
## Editing and motion
Build the spoken explanation first. Map every retained range from source in/out to output time; derive caption and insert positions from that map. A screen recording may cover an edit while the voice continues, but it must illustrate the retained thought. Keep full-screen inserts long enough to understand one action or one document excerpt. Use the presenter's return to separate sections instead of adding an unrelated transition at every cut.
Give each insert one focal target. A small zoom, cursor highlight or framed screenshot can direct attention; preserve the rest of the screen when it provides context. Avoid turning static screenshots into fake working UI. When reframing a landscape screen inside a vertical video, test text readability and choose a useful detail or picture-in-picture layout rather than squeezing the entire desktop into a narrow strip.
## Input contract and a new brief
Use the creator's presenter take, actual screen recording or screenshots, an intended sequence of steps, target format and measured speech timing. Existing material takes priority over generating replacements. Voice and background music are independent tracks; do not change speech speed merely to fit a reference's length.
> Turn my recording into a 45-second explanation of how I plan a newsletter. Use my Notion capture and draft screenshots. Keep my voice, show each screen when I discuss it, add quiet captions, and return to my face for the conclusion. Preserve the reference's pacing while fitting my actual words.
## Review and community handoff
Watch with sound to check whether the visuals demonstrate the spoken claim, captions survive the cut map, inserts remain legible and the presenter returns naturally. Compare equivalent beats, not arbitrary adjacent frames. A shared package needs the accepted source project, content slots, motion rules, an edit map, permitted example assets and its own real comparison.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |