Learn anything massive, one 20-second read at a time.
hold-my-hand is an agent skill that turns Claude into an engagement-first tutor. It deep-researches a topic, codebase, or project, then delivers it as one sequential path of tiny chunks — 📍 Chunk 3 of 12 — that start dead simple and get deeper and more interesting as you advance.
The point isn't to dumb topics down — it's to keep you reading. Engagement dies two ways: words you didn't ask for, and depth before you're ready. So the skill enforces both cures:
- Slim-to-none off-topic words. No filler, no preamble, no recaps, no previews. Every word teaches the topic or gets deleted.
- A ramp. Early chunks use a simple format with zero prerequisites; later chunks earn the internals, edge cases, and real code.
- Visible progress. The
x of ycounter is the hook — you always know exactly how far you've come and how little one more chunk costs.
The chunks are strictly sequential — no trees, no layer pyramids to navigate. Behind the scenes the model orders the path in whatever sequence it judges teaches best; you only ever see the counter.
Claude Code (plugin):
/plugin marketplace add RaedMKhalaf/hold-my-hand-claude-skill
/plugin install hold-my-hand@hold-my-hand
Any agent that supports skills:
npx skills@latest add RaedMKhalaf/hold-my-hand-claude-skill
Manual: copy skills/hold-my-hand/SKILL.md to ~/.claude/skills/hold-my-hand/SKILL.md — or paste it as a system prompt in any chat.
Then say: "hold my hand through <topic>". The skill is user-invoked: it fires when you name it, so it never takes over an ordinary question, and it costs nothing in context until you ask for it.
| Mechanism | Rule |
|---|---|
| Deep Research Gate | No teaching output until the topic is fully researched and planned as a single sequential path of y chunks, ordered for best learning. The plan stays invisible. |
| 20-Second Chunks | Each chunk is 2–4 tight sentences, roughly 45–60 words. Code blocks and small diagrams don't count against the budget. |
| The Ramp | Simple, prerequisite-free chunks first; mechanisms in the middle; internals, edge cases, and code at the end. |
| Steering | next (or anything) advances. skip shrinks the path, deeper on <thing> grows it, back re-teaches, and questions are answered in place without advancing. |
You: hold my hand through Git internals
Claude:
📍 Chunk 1 of 8 — Orientation
Git is a content-addressable filesystem with a version-control interface on top. Everything you commit becomes an immutable object named by its hash, stored in
.git/objects. Branches and tags are just movable pointers to those objects, and every command you run manipulates objects, pointers, or the staging area between them.You: next
Claude:
📍 Chunk 2 of 8 — The object model
Git stores four object types: blobs hold file contents, trees map filenames to blobs and other trees, commits point to one tree plus parent commits, and annotated tags name a commit. Each is compressed, hashed, and filed under its hash — identical content is stored exactly once, forever.
MIT © Raed Khalaf