A Skill that only knows facts can't see you changing.
Every Skill you've made so far is static — it has the same facts whether it's Tuesday or six months later. But some of the most interesting things about your life are not facts. They're changes.
A static running Skill
It knows what running is. It knows you run. It knows your usual route. It doesn't know when you ran last, how far, or whether you're getting faster.
Claude: "Nice! Running is great exercise."
A stateful running Skill
It knows everything the static one knows — plus a history. It can notice patterns, celebrate progress, and remind you when it's been too long.
Claude: "That's your third run this week — longest streak since January. How did it feel compared to Tuesday's?"
The difference isn't a smarter AI. It's a Skill that remembers. Same Claude, different data. A memory turns a dictionary into a diary — and a diary notices things about you that you'd never notice yourself.
What do you do repeatedly that's worth remembering?
Stateful Skills only make sense for things you do more than once. Pick something you do at least weekly — you'll get the most out of it.
"Small wins" is a fantastic one for this module — tiny things most kids never record. *"Nailed the landing on my skateboard."* *"Finished my math homework before dinner."* Anything you're quietly proud of.
Every stateful Skill has a timeline.
The shape is always the same: a list of entries, oldest at the top or bottom, each one marked with a date and one or two specific details. Here's a real example for a running Skill.
First run after the flu. Slow pace, cold morning. Didn't stop.
Tried the loop through the park. Didn't have to walk any of it.
Saw a rabbit. Almost tripped. Felt like I could do 4.
Same route. Same distance. Noticeably less tired at the end.
↑ four entries. A pattern is already visible. ↑
Notice what's in the entries and what isn't. Each entry has a date, a measurable (miles), and one human observation (how it felt, what they noticed). That's the whole recipe.
The feeling is the part most trackers miss. Apps record distance and pace; they don't record "saw a rabbit, almost tripped." That's where the real story is — and it's the one detail that makes the Skill good instead of just numeric.
Here's what a stateful Skill looks like.
Same basic shape as a Sprouts Skill — name, description, personality —
but with a new section: history.
And a few rules for how to add new entries.
# A stateful Skill that tracks my runs # Claude updates the history whenever I tell it about a run name: "My Running Log" description: "Tracks my runs so Claude can spot patterns and encourage me honestly" tracking: what: "runs" fields: [date, distance, felt, noticed] update_when: "I mention a run in conversation" history: - date: 2026-03-15 distance: "2 miles" felt: "tired but finished" noticed: "First run after the flu" - date: 2026-03-18 distance: "2.5 miles" felt: "easier than expected" noticed: "Didn't have to walk any of it" - date: 2026-03-21 distance: "3 miles" felt: "proud" noticed: "Saw a rabbit, almost tripped" personality: "Honest, encouraging but not cheesy. Notices patterns." when_to_use: "Whenever I mention running or ask how I'm progressing"
Two new things compared to your Sprouts Skill: the tracking block defines what a new entry should contain,
and the history block
is the actual growing list. Every time you tell Claude about a new run, the history grows by one line.
Build a tracker for your —.
Fill in the form. Add three real entries from the past week or so — if you can't remember three, just make up plausible ones for now. The YAML builds itself as you type.
# Fill in the form above and watch this update. name: ... tracking: what: ... history: - ...
You'll add more entries later as you actually do the thing. The point of this step is to get the shape right. Three is enough.
Not everything is worth remembering.
A tracker that records the wrong things is worse than no tracker at all — it generates noise that hides the real patterns. Two rounds of judgment.
Round 1. You want to track your reading. Which Skill generates more signal?
Round 2. You want to track practice on an instrument. Which tracker actually helps you get better?
Track events that already matter, not metrics that are easy to measure. If a grown-up asks you "how's it going?" and you'd rather tell them the stuck-on-unstuck story than the minute count, you picked the right thing to track.
You built a Skill with memory.
A Skill that can track you across time. A Skill that can notice things about you that you wouldn't notice yourself.
What you just learned
- Static Skills have facts. Stateful Skills have history.
- Every history entry has a date, a measurable, and one human observation.
- The human observation is the part most trackers skip — and the part that makes the whole thing useful.
- Bad tracking generates noise. Good tracking generates signal.
- Track events that already matter to you — not metrics that are easy to count.
In Module 04 — the last Makers module — you'll learn the hardest and most interesting pattern: Skills that multiple people contribute to. You and your brother both adding facts to the same family Skill, and the Skill knowing who said what.
★ Before you call it done
Three questions. Same three. Every time.
These are the same three questions for every module in Kindling. They are how you check whether AI did the part it should and you did the part only you could. Tap each one to mark it true.
★ ★ ★