Skip to main content

learn

Unified learning skill for guided code understanding. Use when the user wants to learn, understand, or be taught — triggers on phrases like 'help me understand', 'how does this work', 'teach me', 'walk me through', 'I don't get', 'I'm confused', 'I'm lost', 'what does this do', 'explain this to me', 'I'm rusty', 'too many concepts', 'guide me'. Also triggers on direct mode requests: 'socratic', 'chunking', 'quiz me on this code'. Do NOT trigger when the user clearly just wants a direct answer — e.g., 'just tell me', 'what's the return type of', 'where is X defined'.

跳到安装

来源信息

仓库
devinat1/learning-toolkit
最近来源活动
2026年4月11日 22:26
检测到的 SKILL.md 语言
英语
星标
1
分支
0

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
learn
description
Unified learning skill for guided code understanding. Use when the user wants to learn, understand, or be taught — triggers on phrases like 'help me understand', 'how does this work', 'teach me', 'walk me through', 'I don't get', 'I'm confused', 'I'm lost', 'what does this do', 'explain this to me', 'I'm rusty', 'too many concepts', 'guide me'. Also triggers on direct mode requests: 'socratic', 'chunking', 'quiz me on this code'. Do NOT trigger when the user clearly just wants a direct answer — e.g., 'just tell me', 'what's the return type of', 'where is X defined'.
# Learn A guided learning skill with multiple modes. Teaches through questions and challenges rather than giving answers directly. ## Phase 1 — Context Scan Before asking any questions, explore the files and code the user is working with. Read relevant files, understand project structure, and identify the learning subject. All subsequent questions must be grounded in actual code, not abstract concepts. ## Phase 2 — Session Preference On first trigger in a session, ask: > "I can either guide you through understanding this step by step, or just explain it directly. Which do you prefer for this session? (You can switch anytime.)" Remember the choice for the session. - If "just explain" — answer normally, no skill modes. Exit the skill. - If guided learning — proceed to Phase 3. **Override signals (respected at any point during the session):** - Switch to direct mode: "just tell me", "just explain", "skip the questions" - Switch to learning mode: "teach me", "guide me", "actually walk me through this" When the user switches, acknowledge briefly ("Switching to guided mode.") and adjust immediately. ## Phase 3 — Mode Selection Present the four modes. Recommend one based on context signals, but let the user pick. | Mode | Best when... | Signal phrases | |------|-------------|----------------| | **Socratic** | User has partial understanding, needs depth | "I think I get it but...", "is this right?" | | **Chunking** | Topic is overwhelming, too many concepts | "there's too much", "where do I start", "I'm lost" | | **Gap Analysis** | User can't code something, needs to find what's missing | "I can't figure out how to...", "I'm stuck on..." | | **Syntax Hints** | User knows the concept but forgot the syntax | "I'm rusty", "how do you write a...", "what's the syntax for" | If the user directly invoked a mode name (e.g., "let's do socratic"), skip the selection menu and go straight to that mode. ## Phase 4 — Mode Execution ### Socratic Mode 1. Ask one probing question about the code or concept at a time 2. After the user answers, rate their understanding 1-5 3. Explain the concept briefly 4. Do NOT advance to the next question until the user explicitly says to move on 5. Questions escalate in depth — start concrete ("what does this line do?"), move toward principles ("why would you choose this pattern over X?") ### Chunking Mode 1. Ask an initial diagnostic question about what the user is trying to learn 2. Based on the answer, break the topic into a bulleted concept list ordered from foundational to advanced 3. Ask the user which concept to dive into first (or recommend one) 4. For the chosen concept, give a simple implementation challenge — not the full solution, just enough to test understanding 5. After the challenge, offer to move to the next concept or go deeper on the current one ### Gap Analysis Mode 1. Explore the codebase to understand what the user is trying to build or understand 2. Ask 3-5 diagnostic questions to map what the user knows vs doesn't know 3. Based on answers, produce a specific list of knowledge gaps tied to the actual code 4. For each gap, suggest a targeted exercise the user can do 5. Do NOT give the answer — the exercises should lead the user to discover it ### Syntax Hints Mode 1. Identify what the user is trying to write 2. Give ONE brief syntax example — just the structure, not a full solution 3. No explanations unless asked — just the syntax shape 4. If the user is still stuck after the hint, offer a slightly more specific hint, but still not the answer ### Mode Switching At any point during execution, the user can request a different mode: - "let's switch to chunking" - "just give me a syntax hint for this part" - "actually, ask me questions about this" Transition without restarting the session. Acknowledge briefly and continue. ## Phase 5 — Understanding Score Available on demand or offered at a natural stopping point. Produces: - **Rating:** X/10 overall comprehension - **Strengths:** What was understood well (specific to what was covered) - **Gaps remaining:** Where understanding is still shallow - **Next steps:** What to learn or practice next Trigger signals: "how am I doing?", "rate me", "how well do I understand this?"
在 GitHub 查看