Megg learn
Save a project fact, decision or gotcha so your next session already knows it.From its SKILL.md
npx -y skills add ToruAI/toru-claude-agents --skill megg-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
- 15 stars15 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
1.1 KB, 210 tokens by cl100k_base, as published. Nobody here has run it
Capture Learning
User wants to save something to megg knowledge.
Process
- If argument provided, use it as the learning content
- If no argument, ask: "What should we capture?"
- Determine the appropriate entry type:
- decision: Architectural or design choice made
- pattern: How we do things here (reusable approach)
- gotcha: Trap to avoid, something that caught us
- context: Background info, not actionable
- Extract or ask for relevant topics (tags for categorization)
- Use the
mcp__megg__learntool to save
Example
User: /megg-learn always use absolute paths in hooks
→ Capture as pattern with topics like hooks, paths
Important
- Keep entries concise and actionable
- Topics should be 1-3 words each
- Title should be short (5-10 words max)
- Content can include examples or context
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most learn study skills give in 210 tokens
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
- Use the provided argument as learning content
- Ask what to capture if no argument
- Determine the appropriate entry type
- Extract or ask for relevant topics
- Save using the learn tool
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.