Stick Figure logo

Stick Figure

Community
artemnovitckii
stick-figure

Makes a code-animated stick-figure explainer reel (9:16, 30 to 45 s) from a question or topic. A bright cartoon world with thick outlines, stick people with big white heads and faces, constant camera motion, whip transitions, 1 to 2 word captions, a playful underscore and cartoon sound effects, all generated in code and timed to the voiceover word by word. Use when the user runs /stick-figure or asks for a stick-figure, stickman or cartoon "what if" explainer.

Overview

Publisherartemnovitckii
Repositoryclaude-animation-skills
Skill namestick-figure
Stars
147
Forks
21
Bundled files
22
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 22 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by artemnovitckii on GitHub. Read the source before you install it.

Installation

Install the Stick Figure AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/artemnovitckii/claude-animation-skills/tree/main/skills/stick-figure
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/artemnovitckii/claude-animation-skills.git /tmp/claude-animation-skills
mkdir -p .claude/skills
cp -r /tmp/claude-animation-skills/skills/stick-figure .claude/skills/stick-figure
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Stick Figure in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Stick Figure on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Stick Figure is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/stick-figure

┌──────────────────────┐
│   ☀      ☁           │  bright sky, sea, props drawn in code
│      ◯   ◯           │  stick people with big white heads, expressive faces
│     /|\ /|\          │
│     / \ / \  🛢       │
│     eye patch        │  1-2 word captions, lowercase, ~70% down
└──────────────────────┘

A worked example comes with it: engine/template is a finished 37 s reel, "What if pirate eye patches had nothing to do with missing eyes?"

First use

This skill's folder is the "Base directory" Claude Code shows when it loads it.

bash
SKILL_DIR="<base directory of this skill>"
ENGINE="$SKILL_DIR/engine"
KIT=$(python3 -c 'import os,sys;print(os.path.realpath(os.path.join(sys.argv[1],"..","..","kit")))' "$SKILL_DIR")
[ -x "$KIT/.venv/bin/python" ] && [ -d "$KIT/models" ] || bash "$KIT/setup.sh" --voice   # ~1 GB of voice models, once
PY="$KIT/.venv/bin/python"; export NODE_PATH="$KIT/node_modules"

Needs ffmpeg, Node and Python 3.9+. To see the example: cp -r "$ENGINE/template" ~/reels/pirate && bash "$ENGINE/make.sh" ~/reels/pirate.

How it fits together

A reel is one folder:

  • script.json: the voiceover, one sentence per entry.
  • captions.json: optional text swaps for captions ({"twenty five": "25"}).
  • web/shots.js: the shot list. Each shot is SHOTS.push({start, end, tr, draw(ctx, lt, t)}) in seconds of the voiceover; lt is time inside the shot, tr is the transition out ('whip' or 'cut').
  • web/lib.js (easing, keyframes kf, shapes, text), web/chars.js (the stick rig drawStick, hats, faces, arm IK, the eye patch), web/env.js (sky, clouds, sea, ships, deck, barrels, cannon, lantern, below deck), web/main.js (whip blur, vignette, grain, captions). Add new props to env.js or a new env2.js (list it in web/index.html).
  • audio.py: music and SFX, all synthesised in code and placed in voiceover seconds.

make.sh makes the voice, aligns every word (audio/words_new.json), mixes the sound, renders the shots in parallel and writes <folder>/<folder name>.mp4.

Timing: audio/words_ref.json is the voice the shots were timed against. When the voice changes but the words don't, make.sh warps the shots onto the new take, so a new recording needs no edits. If the script changes, delete audio/words_ref.json (the next take becomes the reference) and re-time shots.js.

Steps

  1. Script. About 110 to 120 words for 38 to 40 seconds, one idea per sentence: a "what if" hook, the common belief, a turn on "But", examples that build, one shot that shows the mechanism, and a payoff that answers the hook. Show it to the user before animating.
  2. Facts. Check every claim with sources. Hedge theories ("scientists think").
  3. Folder. cp -r "$ENGINE/template" <reel>, then empty its audio/ and replace script.json (and captions.json).
  4. Voice. In the folder: "$PY" "$ENGINE/tools/tts_kokoro.py" (free) or the user's own recording, or ElevenLabs with ELEVENLABS_API_KEY ("$PY" "$ENGINE/tools/tts_elevenlabs.py" audio/vo_el.mp3). Put the take at audio/vo.wav, then "$PY" "$ENGINE/tools/align.py" audio/vo.wav and read the word times in audio/words_new.json.
  5. Shots. Rewrite web/shots.js: about 10 to 12 setups, most 2 to 4 s, the explainer shot longer. A new idea gets a new setup. Start the hook in action on frame 1. Keep faces and key props out of the caption band (y about 1250 to 1420) and inside Instagram's safe area (x 100 to 980, y 220 to 1500).
  6. Stills. From the folder: node "$ENGINE/tools/render.js" stills 1.5,4.2,9.0 writes stills/. Look at the busiest moments and fix them before a full render.
  7. Sound. Edit the cues in audio.py against the word times.
  8. Build. bash "$ENGINE/make.sh" <reel> (keeps audio/vo.wav; pass kokoro, elevenlabs or a file to replace it). WORKERS=8 on a machine with more cores. AUDIO_ONLY=1 remixes the sound without re-rendering.
  9. Hand over <reel>/<name>.mp4.

Style

  • Captions: Poppins Bold, white with a dark outline, 1 to 2 words, lowercase, no punctuation (capText() in main.js does it; digits and % stay). No em dashes anywhere on screen.
  • Bright saturated palette, ink outlines (#221c22), soft contact shadows, slow push-ins with handheld drift, whip transitions with motion blur. An impact is a burst, a shake and a flash.
  • SFX sit under the voice (gain about 0.38). The music is a quiet plucked underscore, ducked under the voice, never a loud loop at the start.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Stick Figure AI skill do?

Makes a code-animated stick-figure explainer reel (9:16, 30 to 45 s) from a question or topic. A bright cartoon world with thick outlines, stick people with big white heads and faces, constant camera motion, whip transitions, 1 to 2 word captions, a playful underscore and cartoon sound effects, all generated in code and timed to the voiceover word by word. Use when the user runs /stick-figure or asks for a stick-figure, stickman or cartoon "what if" explainer.

Why use Stick Figure on TypingMind?

Because you install it once and use it with any model. Stick Figure is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Stick Figure in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/artemnovitckii/claude-animation-skills/tree/main/skills/stick-figure. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Stick Figure?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Stick Figure?

As many as you like. As long as a model supports skills, you can use Stick Figure with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Stick Figure AI skill free?

It is published on GitHub by artemnovitckii. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇