directing-stickman-videos
Turn topics, requirements, articles or scripts into stickman videos. Director mode creates approved storyboards and standalone video prompts; Autopilot mode produces narrated, captioned illustration-and-micro-animation videos through configured generation tools and a local renderer.
Install / Use
npx skills add kaomei/stickman-video-director --skill directing-stickman-videosInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of directing-stickman-videos
directing-stickman-videos scores 87/100 on our quality scale, 2209th of 4,596 Development & Engineering skills we index (top 49%).
Its SKILL.md is 14 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 2,263 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 8 days ago, so directing-stickman-videos is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
directing-stickman-videos compared with similar skills
All 4 of these similar skills score higher than directing-stickman-videos; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| directing-stickman-videos (this skill)by kaomei | 87 | 2.3k | 8d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 101.7k | 3d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 64.2k | 3d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 44.0k | 4d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 31d ago | SKILL.md |
Frequently asked questions
- How do I install directing-stickman-videos?
- Run
npx skills add kaomei/stickman-video-director --skill directing-stickman-videos. The install tabs above show the steps for each supported agent. - Which AI agents does directing-stickman-videos work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is directing-stickman-videos safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is directing-stickman-videos still maintained?
- The repository was last updated 8 days ago, so directing-stickman-videos is actively maintained.
Skill content
View source on GitHubname: directing-stickman-videos description: "Turn topics, requirements, articles or scripts into stickman videos. Director mode creates approved storyboards and standalone video prompts; Autopilot mode produces narrated, captioned illustration-and-micro-animation videos through configured generation tools and a local renderer. Also guide installation handoff, first use and setup of this specific Skill."
Directing Stickman Videos
Two modes, one Skill
Keep the existing installation and name. Route by the requested deliverable:
- A · Director: proposals, storyboards and standalone video-generation prompts. A1/A1.1/A1.2 map to Style 1 light/dark; A2/A2.1/A2.2 to Style 2/2A/2B; A3–A5 to Styles 3–5. Follow the unchanged Director contract below.
- B · Autopilot: a finished local video with narration, captions, meaningful illustrations, local motion and SFX. Read Autopilot, then its selected B-style reference. B1 is 极简手绘风. B styles have their own assets and numbering; do not silently reuse an A-style prompt or sample.
If the mode is ambiguous, ask one short question. Honor previously supplied choices. Do not run Director's ten-second clip rules, no-visible-text rule or Phase B prompt workflow for Autopilot. Autopilot can start with a topic, promotion brief, post, article or story script; it is not story-only. English is the default narration language, but the user's language and voice choices take precedence.
Voice instructions are mode-specific: B uses the selected named TTS voice as provided, with no added voice/style description. Director's detailed frozen voice profiles below and in references/voice-continuity.md apply only to A, not to any B style.
A and B share an installation, not a production contract or style library. All sections from A · Director to the end of this file apply only to A1–A5, including phrases such as "all styles". For B, use only Autopilot's production rules and the selected B-style reference; do not inherit A's setup, approvals, pacing, prompts, voice or visual constraints. Each B style owns its visuals, captions, voice, pacing and SFX; never inherit B1 by default. Preserve A's validated rules when revising B, and vice versa.
First use and next steps
Use one shared guide in the user's requested or current conversation language, falling back to an available host/local language setting when unclear. Keep guidance language separate from video narration/subtitles; do not select it from the README edition.
Read first-use and stage guidance at installation handoff or first use; apply it in both modes. After verifying an installation you perform, show a plain-language quick-start immediately; otherwise on first invocation. Explain outputs, uses, tools, workflow, copyable requests and relevant public GitHub style/sample catalogs with selection by code. Reuse known choices. At substantive stage completions or blockers, distinguish assistant work from user choices; state completed outputs, missing items and the concrete next action. Do not add mandatory approval gates or repeat the welcome every turn.
For optional A character references, follow Optional A character references in that guide; keep validated prompts and voice rules unchanged.
A · Director
Core contract
Turn one source into a confirmed director's proposal and then N standalone prompts for approximately ten-second Gemini Omni Flash clips (where N = target duration in seconds / 10; default 6 clips for 60 seconds). Preserve the source's meaning while structuring it through a high-completion 5-stage emotional narrative arc.
Setup gate
Require these before planning:
- source material
- aspect ratio:
16:9or9:16 - target duration: in multiples of 10 seconds (e.g.
30s,60s,90s,3min,5min; default:60s/ 6 clips if unspecified) - visual style and theme:
Style 1 (Classic Minimalist): light (white background, black figure) or dark (black background, white figure)Style 2 (Modern Beanie Zeke):Style 2A (Modern Studio Tech): pure white high-key studio, subtle light-gray perspective grid, floating cyan/blue glass UIStyle 2B (Cinematic Story): full-color narrative environments, cinematic lighting & depth
Style 3 (Prehistoric Hand-Drawn / Dark Comedy): expressive white filled heads, black stick limbs, animal-hide costumes and earthy prehistoric settings; story-specific castingStyle 4 (Cozy Storytelling / 治愈故事风): expressive minimalist white-filled characters with dark stick limbs in full-color 2D cartoon environments; varied story locations and cinematic shot changesStyle 5 (Historical Cartoon / 历史卡通风): white-filled round heads, simple black oval eyes and thin black stick limbs in era-specific costume, with cel shading and full-color painterly historical settings
If aspect ratio or visual style is missing, ask for all missing items in one concise message and stop. If duration is omitted, default to 60 seconds (6 clips). If a user provides a duration not divisible by 10, round to the nearest 10-second multiple. If a user specifies only light or dark theme, default to Style 1. Never select an aspect ratio or style silently. Do not re-ask choices already supplied.
Urgency, generation cost, client pressure, and requests to "pick normal settings" do not waive this gate.
Workflow
- Read
references/storyboard-template.md,references/style-catalog.mdandreferences/voice-continuity.md. Structure the narrative using the 5-Stage High-Completion Heartbeat Engine (Golden Hook → Disrupting Assumptions → Unveiling Insider Secrets → Ultimate Truth Revelation → Elevation & Interactive Discussion), with timing dynamically scaled to the target duration. Produce Phase A in the user's language, with English VO and a reference translation. - Stop after the director's proposal and request explicit approval.
- If the user changes ratio, duration, style, theme, narration, scene structure, or global direction, recompose Phase A and request approval again.
- Only after approval of the current Phase A, read
references/omni-flash-prompt-contract.mdand produce Phase B. - Use
references/examples.mdonly when a concrete end-to-end example would resolve ambiguity.
Topic approval, schedule pressure, or approval of an older draft is not approval of the current Phase A.
Output rules
For Style 3, read references/prehistoric-dark-comedy.md before planning. Its casting, story rhythm, palette and continuity rules override the generic no-idle, device-count and five-stage discussion-ending rules below. Use setup → escalation → ironic payoff for narrative shorts; do not force a discussion question into a visual punchline. This is a visual storytelling style, not a claim about actual prehistory.
For Style 4, read references/cozy-storytelling.md before planning and prompt assembly. Default each new ten-second segment to a different recognizable story setting, unless the user explicitly requests one location or approves a deliberate return. Preserve characters, drawing grammar, important props, movement direction and narrator—not an identical table or background across the whole video. Name the location cuts and any time jumps in Phase A. This is full-color cartoon storytelling, not a hand-drawn/sketchbook mode and not a claim of photorealistic 3D backgrounds.
For Style 5, read references/historical-cartoon.md before planning and prompt assembly. Keep its drawing grammar fixed while changing the era pack. Confirm story-specific cast cards, setting, palette, props and exact narration in Phase A; repeat the full approved style and visible cast descriptions in every Phase B prompt. Its historical palette, music, physical-action pacing and story ending override generic three-color, mandatory-piano, device-count, no-idle and discussion-ending rules below. Apply the existing shared voice contract; do not apply this style's character rules to Styles 1–4.
- Structure every script using the 5-stage high-completion flow:
- Golden Hook: Instant curiosity trigger via a counter-intuitive question or visual paradox. Timing is flexible based on duration (e.g. within the first 2–5 seconds in short videos, up to 10–15s in long videos); never open with generic platitudes.
- Disrupting Assumptions: State what everyone thinks is true, then shatter it in one sentence to build cognitive conflict.
- Unveiling Insider Secrets: Pull back the curtain on hidden mechanics, counter-intuitive details, or the real obstacle.
- Ultimate Truth Revelation: Deliver the underlying business logic or human psychology truth with maximum cognitive payoff.
- Elevation & High-Engagement Discussion: Conclude with a memorable punchline and an irresistible discussion prompt that sparks debate in the comments.
- Scale English VO word count to approximately 20–25 words per 10-second clip across N clips (e.g. ~60–75 words for 30s / 3 clips, ~120–150 words for 60s / 6 clips, ~360–450 words for 3min / 18 clips, ~600–750 words for 5min / 30 clips).
- Give each clip three timed beats, at least four relevant visual devices, and a visual change every two to three seconds.
- Keep character proportions, line weight, style, and narrator consistent across all clips.
- For Style 1, freeze the concise character anchor from
references/style-catalog.mdand repeat it verbatim in every clip. Keep two arms and two legs, one current pose per limb, stable proportions and uniform medium line weight; a moving arm replaces its previous pose rather than adding another arm. Keep the figure monochrome and saturated accents on props/graphics. Do not replace the anchor with "same character", ellipses, numeric anatomy recipes, skeleton/path instructions or clip-specific appearance descriptions. Occasional simple line expressions are allowed; the head remains hollow. Keep rich actions and effects separate from character design. Treat generated consistency as a visual acceptance check, not a guarantee from repeated text. - For Style 1, limit the video to three saturated accent colors named with ordinary descriptive words (e.g. vivid red, electric blue, warm gold). For light theme, enforce a flat, digitally pure-white canvas with no textures, gradients, or 3D depth.
- For Style 2 (Modern Beanie Zeke), enforce character consistency:
- Clip 1:
A minimalist 2D animated stick figure wearing a bright red beanie (smooth knit, no pom-pom) and a yellow t-shirt, with simple black stick limbs and shorts. Simple black lines, vibrant colors, smooth 2D animation style. - Clips 2–N:
The same minimalist 2D animated stick figure in a bright red beanie and yellow shirt... Simple black lines, vibrant colors, smooth 2D animation style. - No detailed eyes, pupils, or photorealistic features (avoids bug-eye deformation).
- Clip 1:
- For Style 2A (Modern Studio Tech), enforce:
in a modern bright white studio space with subtle light-gray perspective grid lines on the floor plane. High-key studio lighting, clean white negative space, sleek glowing cyan and electric blue glass holographic UI elements.Always include negative constraint:STRICTLY MINIMALIST, NO CIRCUIT BOARD TEXTURES, NO SCI-FI WALL PANELS, NO CRACKED CONCRETE. - For Style 2B (Cinematic Story), specify full-color narrative setting and cinematic lighting while preserving the 2D animated stick-figure character design.
- For Style 4, freeze each approved character's complete anchor and repeat it in every clip where that role appears. Separate static design from first-frame positions, timed prop transfers and final states; changing scene does not reset prop ownership or the narrator. Read its reference for shot variety and visual acceptance checks.
- For all styles, avoid abstract liquid/shape morphing. Drive motion with concrete character actions (leaping, touching glass, drawing luminous line
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
101.7kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
64.2kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
44.0kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
