teach
정보
"teach" 스킬은 학습자의 이해도를 모델링하고, 알려진 개념에서 알려지지 않은 개념으로 설명을 단계적으로 구성하는 구조적이고 적응형 지식 전달을 제공합니다. 이 스킬은 소크라테스식 질문법을 활용하며 피드백에 기반하여 조정되므로, 선수 지식이 필요한 복잡한 주제를 설명하거나 표준 설명이 효과를 보지 못했을 때 이상적입니다. 사용자가 "X는 어떻게 작동하나요?"라고 묻거나 점진적 교수 접근법이 필요한 개념적 격차를 보일 때 이 스킬을 사용하세요.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/teachClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
教える
Conduct a structured knowledge transfer session — assessing the learner's current understanding, scaffolding from known to unknown, explaining at the calibrated depth, checking comprehension through questioning, adapting to feedback, and reinforcing through practice.
使用タイミング
- A user asks "how does X work?" and the answer requires graduated explanation, not a data dump
- The user's questions reveal a gap between their current understanding and what they need to know
- Previous explanations have not landed — the user is confused or asking the same question differently
- Teaching a concept that has prerequisites the user may not have
- After
learnhas built a deep mental model that now needs to be communicated effectively
入力
- 必須: The concept, system, or skill to teach
- 必須: The learner (available implicitly — the user in conversation)
- 任意: Known learner context (expertise level, background, stated goals)
- 任意: Previous failed explanations (what has already been tried)
- 任意: Time/depth constraint (quick overview vs. deep understanding)
手順
ステップ1: Assess — Map the Learner
Before explaining anything, determine what the learner already knows and what they need.
Learner Calibration Matrix:
┌──────────────┬────────────────────────────┬──────────────────────────┐
│ Level │ Explanation Pattern │ Check Pattern │
├──────────────┼────────────────────────────┼──────────────────────────┤
│ Novice │ Analogy-first. Connect to │ "In your own words, what │
│ (no domain │ familiar concepts. Avoid │ does X do?" Accept any │
│ vocabulary) │ jargon entirely. Concrete │ correct paraphrase. │
│ │ before abstract. │ │
├──────────────┼────────────────────────────┼──────────────────────────┤
│ Intermediate │ Build on existing vocab. │ "What would happen if │
│ (knows terms,│ Fill gaps with targeted │ we changed Y?" Tests │
│ some gaps) │ explanations. Use code │ whether they can predict │
│ │ examples that are close │ from understanding. │
│ │ to their existing work. │ │
├──────────────┼────────────────────────────┼──────────────────────────┤
│ Advanced │ Skip fundamentals. Focus │ "How would you compare │
│ (strong base,│ on nuance, trade-offs, │ X to Z approach?" Tests │
│ seeks depth) │ edge cases. Reference │ integration and judgment. │
│ │ source material directly. │ │
├──────────────┼────────────────────────────┼──────────────────────────┤
│ Misaligned │ Correct gently. Provide │ "Let me check my under- │
│ (confident │ the right model alongside │ standing — you're saying │
│ but wrong) │ why the wrong model feels │ X?" Mirror back to │
│ │ right. No shame signals. │ surface the mismatch. │
└──────────────┴────────────────────────────┴──────────────────────────┘
- Review what the user has said: their questions, vocabulary, stated goals
- Classify their likely level for this specific topic (a person can be advanced in one area and novice in another)
- Identify the Zone of Proximal Development (ZPD): what is just beyond their current reach but achievable with support?
- Note any misconceptions that need to be addressed before the correct model can land
- Identify the best entry point: what do they already know that connects to what they need to learn?
期待結果: A clear picture of: what the learner knows, what they need to know, and what bridge connects the two. The assessment should be specific enough to choose an explanation strategy.
失敗時: If the learner's level is unclear, ask a calibration question: "Are you familiar with [prerequisite concept]?" This is not a test — it is gathering data to teach better. If asking feels awkward, default to intermediate level and adjust based on their response.
ステップ2: Scaffold — Bridge Known to Unknown
Build a path from what the learner already understands to the new concept.
- Identify the anchor: one concept the learner definitely understands that relates to the target
- State the connection explicitly: "X, which you know, works like Y in this new context because..."
- Introduce one new idea at a time — never two new concepts in the same sentence
- Use concrete examples before abstract principles
- Build layered complexity: simple version first, then add nuance
- If prerequisites are missing, teach the prerequisite first (mini-scaffold) before returning to the main concept
期待結果: A scaffolded path where each step builds on the previous one. The learner should never feel lost because each new idea connects to something they already hold.
失敗時: If the gap between known and unknown is too large for a single scaffold, break it into multiple smaller steps. If no familiar anchor exists (entirely novel domain), use analogy to a different domain the learner knows. If the analogy is imperfect, acknowledge the limits: "This is like X, except for..."
ステップ3: Explain — Calibrate Depth and Style
Deliver the explanation at the right level, in the right mode.
- Open with the core idea in one sentence — the headline before the article
- Expand with the scaffolded explanation built in Step 2
- Use the learner's vocabulary, not the domain's jargon (unless they are advanced)
- For code concepts: show a minimal working example, not a comprehensive one
- For abstract concepts: provide a concrete instance first, then generalize
- For processes: walk through a specific case step-by-step before stating the general rules
- Monitor for signs of confusion: if the next question does not build on the explanation, the explanation did not land
期待結果: The learner receives an explanation that is neither too shallow (leaving them with questions) nor too deep (overwhelming with unnecessary detail). The explanation uses their language and connects to their context.
失敗時: If the explanation is too long, the core idea may be buried — restate the one-sentence headline. If the learner looks more confused after the explanation, the entry point was wrong — try a different anchor or analogy. If the concept is genuinely complex, acknowledge complexity rather than hiding it: "This has three parts, and they interact. Let me start with the first."
ステップ4: Check — Verify Understanding
Do not assume the explanation worked. Test it through questions that reveal the learner's mental model.
- Ask a question that requires application, not recall: "Given X, what would you expect to happen?"
- Ask for a paraphrase: "Can you explain this back in your own words?"
- Present a variation: "What if we changed this one thing?"
- Look for the specific understanding: can they predict, not just repeat?
- If their answer reveals a misconception, note the specific error for Step 5
- If their answer is correct, push slightly further: can they generalize?
期待結果: The check reveals whether the learner has a working mental model or is parroting back the explanation. A working model can handle variations; a memorized explanation cannot.
失敗時: If the learner cannot answer the check question, the explanation did not build the right mental model. This is not their failure — it is feedback on the teaching. Note what specifically did not land and proceed to Step 5.
ステップ5: Adapt — Respond to Feedback
Based on the check results, adjust the teaching approach.
- If understanding is solid: proceed to reinforcement (Step 6) or advance to the next concept
- If a specific misconception exists: address it directly with evidence, not repetition
- If general confusion exists: try a completely different explanation approach
- If the learner is ahead of the assessment: accelerate — skip scaffolding and go to nuance
- If the learner is behind the assessment: slow down — teach the prerequisite they are missing
Adaptation Responses:
┌──────────────────┬─────────────────────────────────────────────────┐
│ Signal │ Adaptation │
├──────────────────┼─────────────────────────────────────────────────┤
│ "I think I get │ Push gently: "Great — so what would happen │
│ it" │ if...?" Verify before moving on. │
├──────────────────┼─────────────────────────────────────────────────┤
│ "I'm confused" │ Change modality: if verbal, show code. If code, │
│ │ use analogy. If analogy, draw a diagram. │
├──────────────────┼─────────────────────────────────────────────────┤
│ "But what about │ Good sign — they are testing the model. Address │
│ [edge case]?" │ the edge case, which deepens understanding. │
├──────────────────┼─────────────────────────────────────────────────┤
│ "That doesn't │ They have a competing model. Explore it: "What │
│ seem right" │ do you think happens instead?" Reconcile the two.│
├──────────────────┼─────────────────────────────────────────────────┤
│ Silence or │ They may be processing, or lost. Ask: "What │
│ topic change │ part feels least clear?" Lower the bar gently. │
└──────────────────┴─────────────────────────────────────────────────┘
期待結果: The teaching adapts in real time based on feedback. No explanation is repeated identically — each retry uses a different approach. The adaptation should feel responsive, not mechanical.
失敗時: If multiple adaptation attempts fail, the problem may be a missing prerequisite that is so fundamental neither party has identified it. Ask explicitly: "What part of the explanation feels like the biggest jump?" This often reveals the hidden gap.
ステップ6: Reinforce — Provide Practice
Solidify understanding through application, not repetition.
- Provide a practice problem that requires the new concept (not a trick question)
- If in a coding context: suggest a small modification to existing code that uses the concept
- If in a conceptual context: present a scenario and ask them to apply the model
- Connect forward: "Now that you understand X, this connects to Y, which we can explore next"
- Provide reference material for independent exploration: documentation links, related files, further reading
- Close the loop: "To summarize what we covered..." — one sentence for the core concept
期待結果: The learner has applied the concept at least once and has resources for continued learning. The summary anchors the learning for future recall.
失敗時: If the practice problem is too hard, the teaching jumped too far — simplify the problem. If the learner can do the practice but cannot explain why, they have procedural knowledge without conceptual understanding — return to Step 3 with a focus on the "why" rather than the "how."
バリデーション
- The learner's level was assessed before the explanation began
- The explanation was scaffolded from known to unknown, not delivered as a data dump
- At least one check question was asked to verify understanding (not assumed)
- The teaching adapted based on feedback rather than repeating the same explanation
- The learner can apply the concept, not just recall the explanation
- Honest gaps were acknowledged rather than glossed over
よくある落とし穴
- The curse of knowledge: Forgetting that the learner does not share the teacher's context. Jargon, assumed prerequisites, and implicit reasoning steps are the primary culprits
- Explaining to impress rather than to teach: Comprehensive, technically precise explanations that demonstrate knowledge but leave the learner behind
- Repeating louder: When an explanation does not land, repeating it with more emphasis rather than trying a different approach
- Testing instead of teaching: Using check questions as gotchas rather than as diagnostic tools. The goal is to reveal understanding, not to catch failure
- Assuming silence is understanding: The absence of questions does not mean the explanation worked — it often means the learner does not know what to ask
- One-size-fits-all depth: Giving a novice an advanced explanation because "they should understand the full picture" overwhelms; giving an expert a beginner explanation because "better safe" wastes their time
関連スキル
teach-guidance— the human-guidance variant for coaching a person in becoming a better teacherlearn— systematic knowledge acquisition that builds the understanding to teach fromlisten— deep receptive attention that reveals the learner's actual needs beyond their stated questionmeditate— clearing assumptions between teaching episodes to approach each learner freshly
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
