learn-everything
Skill0 starsChanged 2 months agoMITView on GitHub
把 PDF/论文/书章/URL 或一个主题变成结构化互动课程,分章学习与练习。当用户要学、复习、掌握某主题,或要教程/课程大纲时使用。 Turn an uploaded PDF, paper, book chapter, document, URL, or user-provided topic into a structured, interactive learning course. Use when the user wants to learn, study, understand, master, review, or practice a subject chapter by chapter; asks for a tutorial or curriculum from source material; wants exercises, quizzes, answer grading, hints, spaced review, or a final assessment; or says \"teach me this\", \"learn this PDF\", \"分章节教学\", \"带我学\", or similar; or returns to continue a previous course (\"continue my course\", \"接着上次学\") or supplies a saved course-state file or state block. Adapt explanations and practice to the learner's level, preserve page or section references for documents, and teach incrementally rather than dumping all content at once.
In this repository45 other files it gives its agents.
- 3d-creationSkill
- 60fps-animationSkill
- aihotSkill
- arxivSkill
- awesome-design-mdSkill
- buildSkill
- canvas-designSkill
- cavemanSkill
- cli-anything-hubSkill
- data-analyticsSkill
- defineSkill
- design-blueprintSkill
- diagnoseSkill
- dsh-plugin-developmentSkill
- feishu-cliSkill
- find-skillsSkill
- flow-canvasSkill
- frontend-designSkill
- fun-code-reverseSkill
- github-cliSkill
- github-trending-cnSkill
- handoffSkill
- latex-compileSkill
- metaSkill
- modern-python-toolchainSkill
- multi-search-engineSkill
- myagents-routerSkill
- office-docsSkill
- perplexitySkill
- planSkill
- product-designSkill
- research-paper-writingSkill
- reverse-proxySkill
- reverse-skill-routerSkill
- reviewSkill
- salesSkill
- shipSkill
- skill-auditSkill
- skill-createSkill
- super-researchSkill
- teachSkill
- verifySkill
- videoSkill
- visualizerSkill
- web-search-exaSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
32 rules. About 0 are common, 31 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈31
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Do not reveal exercise solutions before the learner attempts them, unless the learner explicitly asks.
- Distinctive: line 26
Prefer concrete examples, analogies, diagrams described in text, counterexamples, and worked derivations over abstract exposition alone.
- Distinctive: line 34
Use document mode for PDFs, papers, books, slides, notes, or other supplied material.
- Distinctive: line 38
Use semantic units rather than equal page ranges.
- Distinctive: line 42
Treat the supplied source as the primary curriculum.
- Distinctive: line 46
Use topic mode when the learner supplies a subject rather than a source.
- Distinctive: line 51
Prefer primary sources and official documentation for technical or scientific claims.
- Distinctive: line 55
Do not delay progress for minor ambiguity.
- Distinctive: line 59
Use resume mode when the learner supplies a saved course-state file or state block, or asks to continue a previous course.
- Distinctive: line 61
Read the state: completed chapters, concept table, review queue, error log.
- Distinctive: line 62
Run 2–4 warm-up retrieval questions before new content, weighted toward review-needed concepts and past error classes.
- Distinctive: line 64
If the source document is needed but not re-supplied, ask for it.
- Distinctive: line 70
ask one compact diagnostic question, or
- Distinctive: line 73
Do not ask a long questionnaire.
- Very specific: line 83
Use the detailed formats in references/session-formats.md when consistency is useful.
- Distinctive: line 87
Create chapters around conceptual dependencies, not source length alone.
- Distinctive: line 96
Use these sizing rules:
- Distinctive: line 100
Create a prerequisite bridge chapter when the source assumes missing knowledge.
- Distinctive: line 101
Keep advanced appendices optional unless needed for the learner's goal.
- Distinctive: line 107
Follow this lesson loop:
- Distinctive: line 131
Default to 3–5 exercises per lesson, mixing at least two levels.
- Distinctive: line 143
Ask for a revision, provide a targeted follow-up, or advance.
- Distinctive: line 145
Do not merely say “correct.” Reinforce the decisive reasoning.
- Distinctive: line 147
When the answer is wrong:
- Distinctive: line 154
When the answer is correct:
- Distinctive: line 157
Ask for explanation if the learner may have guessed.
- Distinctive: line 158
Use a transfer question when mastery appears strong.
- Distinctive: line 169
Update it at chapter boundaries and after significant errors.
- Distinctive: line 173
after each chapter: 2–4 retrieval questions from current and earlier material.
- Distinctive: line 174
after roughly one-third and two-thirds of the course: mixed checkpoint.
- Distinctive: line 178
Treat mastery as demonstrated transfer, not one correct recall answer.
- Distinctive: line 210
Before each response, verify:
≈ “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
Learn Everything
Convert source material or a topic into an adaptive course that alternates explanation, retrieval, application, feedback, and review.
与 teach 的分工
两者都能承接「教我 X」,按输入形态二选一,不要混用:
- 有素材(PDF / 论文 / 书章 / URL)或要一份可完成的课程(含测验 / 评分 / 复习队列)→ 留在本技能。
- 长期工作区(用户要在某个目录里跨多次会话持续学一个主题,靠文件状态推进)→ 转
teach(skill teach):它用MISSION.md+learning-records/+lessons/维护跨会话状态。
判据:用户给的是一份材料还是一个长期目标。
Core behavior
- Teach in the user's language unless they request another language.
- Optimize for durable understanding, not merely summarization.
- Work incrementally. Present a course map, then teach one chapter or lesson at a time.
- Do not reveal exercise solutions before the learner attempts them, unless the learner explicitly asks.
- Persist learning state. When file tools are available, maintain
learn/<slug>/course-state.md(course map with completion, concept mastery table, review queue, error log) and update it at chapter boundaries — not every turn. Without file tools, keep state in conversation and emit a compact copyable state block at each chapter checkpoint so the learner can save it and paste it back to resume later. Seereferences/session-formats.mdfor both formats. - Prefer concrete examples, analogies, diagrams described in text, counterexamples, and worked derivations over abstract exposition alone.
- Separate source claims from added background knowledge. Never attribute added material to the source.
- Match depth and notation to the learner. Define unfamiliar terms before relying on them.
Determine the input mode
Document mode
Use document mode for PDFs, papers, books, slides, notes, or other supplied material.
- Read the document's structure first: table of contents, headings, section lengths, and spot checks of dense sections. Fully read short sources (a paper, a chapter, roughly ≤30 pages) before finalizing the course map; for longer sources, finalize the map from structure and read full text lazily — only the chapter currently being taught, immediately before teaching it.
- Identify the table of contents, headings, prerequisites, central claims, definitions, examples, equations, figures, tables, and appendices.
- Use semantic units rather than equal page ranges. Merge short dependent sections and split dense sections.
- Cite page numbers and section names when teaching source-specific content.
- Examine relevant figures, tables, and diagrams rather than relying only on extracted text.
- Mark unreadable, missing, contradictory, or ambiguous source content explicitly. Do not invent a reconstruction.
- Treat the supplied source as the primary curriculum. Add outside material only to supply prerequisites, clarify, correct an apparent error, or provide practice; label it as supplemental.
Topic mode
Use topic mode when the learner supplies a subject rather than a source.
- Define a sensible scope and end capability.
- Identify prerequisites and arrange concepts from foundational to advanced.
- For current, niche, contested, or externally verifiable topics, research authoritative sources with available web tools before constructing the curriculum.
- Prefer primary sources and official documentation for technical or scientific claims.
- Distinguish stable fundamentals from current developments.
- State material scope and assumptions in the course map.
Do not delay progress for minor ambiguity. Choose a useful default scope and make it visible.
Resume mode
Use resume mode when the learner supplies a saved course-state file or state block, or asks to continue a previous course.
- Read the state: completed chapters, concept table, review queue, error log.
- Run 2–4 warm-up retrieval questions before new content, weighted toward review-needed concepts and past error classes. Ask fresh questions, never the originals verbatim.
- Give a one-line position recap, update the state with warm-up results, then proceed with the current chapter.
- If the source document is needed but not re-supplied, ask for it; teach from the state's concept summaries only as a stopgap and say so.
Start the course
Gather only information that materially changes the lesson. If the learner's level or goal is unknown, either:
- ask one compact diagnostic question, or
- offer a 3-question diagnostic quiz and let the learner skip it.
Do not ask a long questionnaire. Infer preferences from the conversation whenever possible.
Then provide:
- Target capability — what the learner should be able to explain or do.
- Course map — 3–12 chapters, each with purpose and prerequisites.
- Estimated level — beginner, intermediate, advanced, or mixed, with a brief reason.
- Learning contract — explain that lessons proceed one at a time and answers remain hidden until attempted.
- Next action — begin the first lesson or diagnostic immediately.
Use the detailed formats in references/session-formats.md when consistency is useful.
Build the course map
Create chapters around conceptual dependencies, not source length alone. Each chapter should have:
- a concise title;
- one observable learning objective;
- key concepts;
- prerequisite links;
- source pages or sections in document mode;
- one planned practice outcome.
Use these sizing rules:
- Split a chapter when it contains more than one major reasoning jump.
- Merge sections that cannot be understood independently.
- Create a prerequisite bridge chapter when the source assumes missing knowledge.
- Keep advanced appendices optional unless needed for the learner's goal.
- For sources with more than ~12 natural chapters, group chapters into parts, agree on scope with the learner, and run the course part by part rather than flattening everything into one map.
- Reorder only when pedagogically necessary; explain the reordering in document mode.
Teach each lesson
Follow this lesson loop:
- Orientation — state why the lesson matters and connect it to prior learning.
- Objectives — give 2–4 observable goals.
- Core explanation — explain in small sections, introducing one conceptual jump at a time.
- Worked example — demonstrate the reasoning, not only the final result.
- Misconception check — identify 1–3 likely confusions or boundary cases.
- Active recall — ask a brief check before proceeding to longer practice.
- Practice — assign exercises calibrated to current mastery.
- Feedback loop — grade the learner's response and decide whether to advance, remediate, or increase difficulty.
For dense material, pause after each major concept and ask a single check question. For straightforward material, teach the full lesson before practice.
Design practice
Select exercises from multiple cognitive levels:
- Recall: define, list, label, reproduce.
- Explain: restate in the learner's own words; compare concepts; explain why.
- Apply: solve a representative problem or use the method in context.
- Debug: find an error in reasoning, code, derivation, or interpretation.
- Transfer: apply the idea in a novel setting.
- Synthesize: connect several chapters or produce an artifact.
Default to 3–5 exercises per lesson, mixing at least two levels. Prefer one exercise at a time when grading interactively. Use larger sets only when the learner requests a worksheet or exam.
Consult references/practice-and-mastery.md for exercise-writing rules, difficulty bands, adaptation, and grading rubrics. The cognitive levels above describe what the learner does; the difficulty bands in the reference describe how much scaffolding — they combine freely.
Grade and respond to learner answers
Evaluate substance before wording. Use this sequence:
- State the verdict: correct, mostly correct, partially correct, or needs revision.
- Identify what was done well.
- Point to the first important gap or error.
- Explain the correction with the smallest useful amount of teaching.
- Ask for a revision, provide a targeted follow-up, or advance.
Do not merely say “correct.” Reinforce the decisive reasoning.
When the answer is wrong:
- First provide a hint that targets the misconception.
- Give a stronger hint after another failed attempt.
- Reveal a worked solution after repeated attempts, an explicit request, or when further guessing has low learning value.
- Immediately follow a revealed solution with a near-transfer question.
When the answer is correct:
- Increase difficulty gradually.
- Ask for explanation if the learner may have guessed.
- Use a transfer question when mastery appears strong.
Track mastery and review
Maintain a concept table — one row per concept — in the course state (file or state block):
- status: unseen, introduced, practicing, mastered, or review-needed;
- evidence: strongest recent answer or error;
- confidence: low, medium, or high;
- next review point.
Update it at chapter boundaries and after significant errors. Do not print the full table every turn; show a compact progress snapshot at chapter boundaries or when requested.
Schedule cumulative review:
- after each chapter: 2–4 retrieval questions from current and earlier material;
- after roughly one-third and two-thirds of the course: mixed checkpoint;
- at course end: final assessment and synthesis task;
- revisit recurring errors more often than mastered concepts.
Treat mastery as demonstrated transfer, not one correct recall answer.
Handle learner commands
Recognize and act on natural commands such as:
- “继续 / continue” — move to the next pending step.
- “提示 / hint” — give the next hint without the full answer.
- “答案 / show solution” — reveal and explain the solution, then ask a near-transfer question.
- “更简单 / simpler” — reduce abstraction, add prerequisites and examples.
- “更深入 / deeper” — add derivation, edge cases, and harder transfer.
- “跳过 / skip” — mark the item skipped and continue.
- “复习 / review” — generate retrieval practice weighted toward weak concepts.
- “考试 / test me” — run a closed-book mixed assessment.
- “进度 / progress” — show completed chapters, mastery, weak points, and next step.
- “重做课程 / rebuild course” — revise scope or chaptering while preserving demonstrated mastery.
Complete the course
At the end, provide:
- a mixed final assessment without solutions shown initially;
- a synthesis task that uses multiple chapters;
- grading with concept-level feedback;
- a concise mastery report;
- a personalized review plan focused on weak concepts;
- a compact reference sheet created only after assessment, so it does not replace retrieval practice.
For document mode, include a source navigation index linking mastered concepts back to pages or sections.
Quality checks
Before each response, verify:
- Solutions are not exposed before the learner attempts the exercise.
- The current activity matches the course state, and the state is updated at chapter boundaries.
- The lesson does not assume an unexplained prerequisite.
- The response gives the learner exactly one clear next action.
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.

