Learn
Use when a task depends on tech you don't actually know, an unfamiliar library, a fast-moving framework, a tricky API, an unfamiliar codebase: or whenever "I think it works like…" is load-bearing. Just-in-time and task-scoped; distinct from levelup, which updates the durable knowledge base.From its SKILL.md
npx -y skills add mehrad-dm/mastermind --skill learnAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.8 KB, as published. Nobody here has run it
MasterMind: Learn
The invokable form of ~/.mastermind/engineering/core/agent-loop.md → "Learn the stack before you build." Topic/task:
$ARGUMENTS. Goal: reach genuine, current understanding: enough to build to standard: fast, and
cheap on context.
1. Detect what's actually used
Read package.json/lockfile, configs, and representative source to see the exact stack (framework +
versions, styling, state, data, test runner) and the team's conventions. Installed versions matter,
APIs drift, so learn the version that's actually here.
2. Map the skill-tree
Use the relevant role/topic map on the website roadmap.sh as the checklist of what matters and to spot your gaps. Learn just the branch the task touches; the rest of the tree waits.
3. Learn to current standards
Read the primary docs for the specific APIs the task needs (verify against the installed version)
and skim one battle-tested example (the field's curriculum.md lists them). Prefer primary sources;
read them fresh, since memory goes stale (the field's learning-sources.md).
4. Ground it in this codebase
Grep for how the pattern is already used here and match it. Consistency beats novelty.
5. Challenge your assumptions before you build
The costly bugs come from unchecked assumptions. Before committing code:
- List what you believe about the APIs you'll use (behavior, signatures, return values, limits,
versions, edge cases), specifically ("
getFilestreams any size", true?). - Answer from the source yourself first: verify each against the docs/types/actual source (for the installed version). Confirm ✓, correct ✗, or mark unknown ❓. Anything the code/docs answer, you answer.
- For each remaining unknown, propose a resolution: a bare flag is half the job. State a best guess
+ confidence ("probably streams; ~70%") so a human can confirm or correct, not author it. Serve
interdependent unknowns one at a time. Anything still unconfirmed becomes an explicit risk or a tiny
prototype, never a silent guess. No load-bearing assumption ships unverified.
Output & economy
Return a tight working brief: the stack + versions, the few APIs/patterns the task needs, the gotchas
(and the assumptions ledger: claim → verified/corrected/unknown → source · confidence),
and links to the primary sources, not a tutorial. Delegate wide reading to a subagent to protect
context. If you learned something durable and reusable, capture it via levelup.
What ships with it: 1 file
4.5 KB alongside SKILL.md
- ABOUT.md4.5 KB
Gives 0 of the 12 instructions most learn study skills give
Counted across 545 of the 593 authors here whose files we hold, read 2026-09-06
- Treat the current directory as a teaching workspacein 20 of 545, across 17 files
- Teach knowledge first then practice skillsin 19 of 545, across 16 files
- Design lessons which build long-term retentionin 15 of 545, across 12 files
- Save each lesson as a self-contained HTML filein 15 of 545, across 12 files
- Question the user on why they want to learn thisin 15 of 545, across 12 files
- Reuse components from the assets directoryin 14 of 545, across 11 files
- Never trust your parametric knowledgein 13 of 545, across 10 files
- Record user preferences in NOTES.mdin 11 of 545, across 8 files
- Ground all teaching in the MISSION.md documentin 11 of 545, across 8 files
- Save each lesson to the lessons directoryin 8 of 545
- Question the user if the mission is unclearin 7 of 545
- Gather primary sources onlyin 7 of 545, across 4 files
Said here and by no other author read
- Read package json and configs to detect the stack
- Use roadmap sh as a checklist for gaps
- Read primary docs for specific task APIs
- Grep for how patterns are used in the codebase
- List what you believe about the APIs you will use
- Verify each assumption against docs or source
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.