start-learn
Skill9 starsChanged 5 months agoMITView on GitHub
Routes a learning goal to an existing-code workflow or a from-scratch teaching workspace. Use when the user wants to start learning, asks \"where do I begin?\", or has not chosen a learning methodology.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-me-questionsSkill
- assessSkill
- connect-to-what-you-knowSkill
- explain-and-checkSkill
- flashcardsSkill
- learn-by-doingSkill
- linked-notesSkill
- quiz-meSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Read FLOWS.md for the full detection logic, skill-mapping table (Scenario A), and step-by-step workspace protocol (Scenario B).
- Distinctive: line 32
Always declare the assumption:
- Distinctive: line 39
Before generating a requested lesson, read LESSON-FORMAT.md for its HTML structure and practice formats.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Start Learn
Speak to the user in their language; these instructions are in English for the agent.
Single-question entry point. One ask — then act. No interview, no menu.
Quick start
User: /start-learn
Agent: What do you want to learn?
(Give me a file/PR to understand, or a topic you want to learn from scratch.)The agent reads the answer, infers Scenario A or B, declares the assumption, and proceeds. If wrong, the user corrects in one word.
Auto-detection
Read FLOWS.md for the full detection logic, skill-mapping table (Scenario A), and step-by-step workspace protocol (Scenario B).
For Scenario A, load the selected skill's instructions through the application's skill mechanism and follow them. Command prefixes in examples are illustrative; use the application's supported invocation syntax. If the target skill is unavailable, name the missing dependency and ask the user to install it; do not invent its workflow.
Summary:
- Scenario A — user mentions existing code, file, PR, or wants to deepen a topic with a codebase already in mind → select the right dialogic skill, declare the choice + a one-line reason, and run it. The user can redirect at any time.
- Scenario B — user names a topic they want to learn from zero → create a teaching workspace, generate CURRICULUM.md, produce HTML lessons on demand.
Always declare the assumption:
"Starting from the hypothesis that you're learning X from scratch — correct me if wrong."
Workspace (Scenario B only)
See WORKSPACE.md for the full directory structure, file purposes, and workspace detection rule.
Before generating a requested lesson, read LESSON-FORMAT.md for its HTML structure and practice formats.
The workspace path is chosen by the user in plain text (no tool). Access in subsequent sessions: cd into the folder. Detection signal for all workspace-aware skills: presence of CURRICULUM.md in cwd.
Baseline handoff
In both scenarios, state the inferred level explicitly at the end:
"I'll carry this baseline (estimated: X) to
/assesswhen you run it later — progress will be measurable."
Anti-patterns
- Don't ask more than one question upfront — the whole point is zero boilerplate; if you need more context, ask after you've started, not before.
- Don't decide silently — always declare the assumed scenario before acting; one wrong assumption costs one correction, not a lost session.
- Don't dispatch silently — auto-selecting the methodology is the behaviour (ADR 0004), but always declare the choice + a one-line reason before running, because an undeclared switch hides the meta-decision the user has the right to override.
- Don't make the user choose between named methodologies — the audience doesn't know the skills by name; offering "explain-and-check or ask-me-questions?" asks for an expert choice they can't make. Pick one, run it, let the user redirect.
- Don't auto-dispatch in Scenario B — selection-and-run applies to Scenario A methodologies; Scenario B still ends with "say 'next lesson' when ready" so the user paces content delivery.
- Don't generate all lessons upfront — one lesson at a time, on demand, so each can adapt to progress recorded in
learning-records/. - Don't invent resource URLs — populate RESOURCES.md via web search; if unavailable, name sources without URLs and flag "verify the link."
Governing principles (this skill satisfies all five)
- Agent withholds — withholds content (lessons deliver only when requested; sessions make the student speak first). Selects the methodology on the user's behalf (ADR 0004) — meta-choice, not content.
- Student speaks first — all choices (workspace path, curriculum approval, lesson request) originate from the user.
- Artefact is the judge — Scenario A: reads real code/docs before proposing. Scenario B: every lesson cites a primary source.
- Source fidelity — web search before content; no parametric knowledge asserted without citation. Before verifying, read SOURCES.md.
- Exit is a transfer test — Scenario A: dispatch to the selected skill, whose completion rule governs the learning session. Scenario B: each lesson ends with a practice section the user completes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

