teach-guidance
について
このスキルは、開発者に対して技術的概念を効果的に教え、説明する方法を指導します。コンテンツの構成方法、異なる聴衆への対応、プレゼンテーションやドキュメンテーション、メンタリングにおける明確性の向上についての指針を提供します。講演の準備、チュートリアルの執筆、または様々な専門知識レベルに対して複雑なトピックを説明する必要がある際にご活用ください。
クイックインストール
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/teach-guidanceこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
Teach (Guidance)
Guide a person in becoming a more effective teacher, explainer, or presenter. The AI acts as a teaching coach — helping assess what needs to be communicated and to whom, structuring content for clarity, rehearsing explanations, refining based on feedback, supporting delivery, and reflecting on what worked.
适用场景
- A person needs to present technical content to an audience and wants to prepare effectively
- Someone wants to write better documentation, tutorials, or explanations
- A person struggles to explain concepts to people with different expertise levels
- Someone is mentoring a colleague or junior developer and wants to be more effective
- A person is preparing for a talk, workshop, or knowledge-sharing session
- After
learn-guidancehas helped them acquire knowledge, they now need to transfer it to others
输入
- 必需: What the person needs to teach or explain (topic, concept, system, process)
- 必需: Who the audience is (expertise level, context, relationship to the person)
- 可选: Format of delivery (presentation, documentation, one-on-one mentoring, workshop)
- 可选: Time constraints (5-minute explanation, 30-minute talk, written document)
- 可选: Previous teaching attempts and what did not work
- 可选: The person's own comfort level with the topic (deep expert vs. recent learner)
步骤
第 1 步:Assess — Understand the Teaching Challenge
Before structuring content, understand the full context of the teaching situation.
- Ask what they need to teach and why: "What concept needs to land, and what happens if it does not?"
- Identify the audience: "Who will you be explaining this to? What do they already know?"
- Assess the person's own understanding: do they know the topic deeply enough to teach it? (If not, suggest
learn-guidancefirst) - Identify the format: presentation, document, conversation, code review, pair programming
- Determine success criteria: "How will you know the audience understood?"
- Surface fears or concerns: "What part of this makes you most nervous?"
Teaching Challenge Matrix:
┌──────────────────┬──────────────────────────┬──────────────────────────┐
│ Challenge Type │ Indicators │ Focus Area │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ Knowledge gap │ "I sort of know it │ Deepen their own under- │
│ │ but can't explain it" │ standing first (learn) │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ Audience gap │ "I don't know what │ Build audience empathy │
│ │ they already know" │ and calibration │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ Structure gap │ "I know it all but │ Organize content into │
│ │ don't know where to │ a narrative arc │
│ │ start" │ │
├──────────────────┼──────────────────────────┼──────────────────────────┤
│ Confidence gap │ "What if they ask │ Practice and preparation │
│ │ something I can't │ for edge cases │
│ │ answer?" │ │
└──────────────────┴──────────────────────────┴──────────────────────────┘
预期结果: A clear picture of the teaching challenge: what, to whom, in what format, with what constraints, and where the person feels least confident.
失败处理: If the person cannot articulate their audience, help them create a persona: "Imagine one specific person who will hear this. What do they know? What do they care about?" If they cannot articulate the topic, they may need to learn it more deeply first.
第 2 步:Structure — Organize Content for Clarity
Help the person build a clear narrative structure for their explanation.
- Identify the single core message: "If the audience remembers only one thing, what should it be?"
- Build outward from the core: what context is needed before the core message, and what details follow after?
- Apply the inverted pyramid: most important information first, supporting details after
- For technical content, choose a structural pattern:
- Concept explanation: What → Why → How → Example → Edge cases
- Tutorial: Goal → Prerequisites → Steps → Verification → Next steps
- Architecture overview: Problem → Constraints → Solution → Trade-offs → Alternatives considered
- Debugging walkthrough: Symptom → Investigation → Root cause → Fix → Prevention
- Ensure each section has a clear purpose: if a section does not serve the core message, cut it
- Plan transitions: "We covered X. Now, building on that, we need to understand Y because..."
预期结果: A structured outline where every element serves the core message. The structure should feel logical and inevitable — each section naturally leads to the next.
失败处理: If the structure keeps growing, the scope is too broad — help them cut. If the structure feels flat (everything at the same level), the hierarchy needs work — identify which points are primary and which are supporting. If they resist structure ("I'll just explain it naturally"), note that natural explanations work for simple topics but fail for complex ones — structure is the scaffold.
第 3 步:Practice — Rehearse the Explanation
Have the person practice explaining the concept, with the AI acting as the audience.
- Ask them to explain the concept as they would to their actual audience
- Listen without interrupting for the first pass — let them find their natural flow
- Note where the explanation is clear and where it becomes confused or vague
- Note where they use jargon the audience might not know
- Note where they skip steps or assume knowledge the audience may not have
- Note where they spend too long on easy parts and rush through hard parts
- Time the explanation if there is a time constraint
预期结果: A first-draft explanation that reveals the person's natural teaching patterns — strengths to build on and habits to adjust. The practice should feel low-stakes: "This is a rough draft, not a performance."
失败处理: If the person freezes or says "I don't know where to start," return to the structure from Step 2 and have them explain one section at a time rather than the whole thing. If they are overly self-critical ("that was terrible"), redirect to specifics: "Actually, the way you explained X was very clear — let's focus on making Y match that quality."
第 4 步:Refine — Improve Based on Feedback
Provide specific, actionable feedback on the practice explanation.
- Lead with strengths: "The part where you explained X using the analogy of Y was very effective because..."
- Identify the biggest improvement opportunity (not all the issues — focus on one or two)
- Suggest specific alternatives: "Instead of saying [complex version], try: [simpler version]"
- Check for the curse of knowledge: are there places where their expertise makes them skip steps the audience needs?
- Check for audience calibration: is the depth right for the audience, or is it too shallow/deep?
- If they use analogies, check if the analogies are accurate (misleading analogies are worse than no analogy)
- Have them re-explain the refined section to test the improvement
预期结果: Targeted feedback that improves the explanation measurably. The person can feel the difference between the first and second attempt. Feedback is framed constructively — what to do, not just what to avoid.
失败处理: If the person is defensive about feedback, reframe from "this was unclear" to "the audience might not follow here — how could we make it even clearer?" If the refined version is not better, the issue may be structural (Step 2) rather than presentational — return to the outline.
第 5 步:Deliver — Support During Teaching
If the teaching happens in real time, provide support during delivery.
- For live presentations: help prepare answers to likely questions in advance
- For documentation: review the written version for clarity, structure, and audience calibration
- Help them prepare for the "I don't know" moment: "If asked something you cannot answer, say: 'Great question — I'll look into that and follow up.' This is always acceptable."
- Encourage interaction: help them prepare check questions for the audience
- Prepare recovery plans: what to do if the audience is lost, bored, or ahead of the explanation
- If coaching during delivery: provide brief, specific prompts ("slow down here," "they look confused — check in")
预期结果: The person feels prepared and supported. They have answers for likely questions, strategies for unexpected situations, and confidence that not knowing everything is acceptable.
失败处理: If anxiety is the primary blocker, address it directly: preparation reduces anxiety, and acknowledging nervousness to the audience often creates connection. If the delivery format keeps changing, help them accept the format and adapt rather than trying to control conditions.
第 6 步:Reflect — Analyze What Worked
After the teaching event, guide reflection for continuous improvement.
- Ask: "What went well? What are you proud of?"
- Ask: "Where did you notice the audience was most engaged? Least engaged?"
- Ask: "Did anything surprise you about the audience's response?"
- Ask: "If you could change one thing, what would it be?"
- Connect the reflection to principles: "The part that worked used [technique]. You can apply that more broadly."
- Identify one specific improvement goal for next time
- Celebrate the accomplishment: teaching is a skill that improves with practice
预期结果: The person gains concrete insight about their teaching effectiveness — not vague feelings but specific observations about what worked and why. They leave with one actionable improvement for next time.
失败处理: If they only see negatives, redirect to specific moments that worked. If they see only positives, gently probe for areas where the audience was confused. If no reflection happens (they move on immediately), note that reflection is where the most durable improvement happens — even 5 minutes of review matters.
验证清单
- The teaching challenge was assessed before structuring began (audience, format, constraints)
- A core message was identified and the structure organized around it
- The person practiced the explanation at least once before delivery
- Feedback was specific, actionable, and led to measurable improvement
- The person was prepared for questions, uncertainty, and audience adaptation
- Post-delivery reflection identified at least one specific improvement for next time
- The coaching was encouraging throughout — teaching is hard and should be acknowledged
常见问题
- Coaching the content, not the teaching: Helping them learn the material instead of helping them present it. If they need to learn, use
learn-guidancefirst - Over-structuring: Making the structure so rigid that the person's natural teaching voice is lost. Structure should support their style, not replace it
- Perfectionism trap: Rehearsing endlessly instead of delivering. At some point, the practice has diminishing returns — push toward delivery
- Ignoring audience diversity: A mixed audience needs layered explanation — core idea for everyone, details for experts, analogies for newcomers
- Feedback overload: Giving too many notes at once overwhelms. Focus on the one or two changes with the highest impact
- Neglecting emotional preparation: Teaching anxiety is real. Addressing confidence is as important as addressing content
相关技能
teach— the AI self-directed variant for calibrated knowledge transferlearn-guidance— coaching a person through learning; the prerequisite to teaching effectivelylisten-guidance— active listening skills help teachers respond to audience needs in real timemeditate-guidance— calming anxiety and achieving focus before a teaching event
GitHub リポジトリ
関連スキル
executing-plans
デザインexecuting-plansスキルは、完全な実装計画があり、それを管理されたバッチでレビューチェックポイントを設けながら実行する場合に使用します。このスキルは計画を読み込んで批判的にレビューした後、小さなバッチ(デフォルトは3タスク)でタスクを実行し、各バッチの間に進捗状況を報告してアーキテクトのレビューを受けます。これにより、品質管理チェックポイントが組み込まれた体系的な実装が保証されます。
requesting-code-review
デザインこのスキルは、コードレビュアーサブエージェントを起動し、処理を進める前に要件に対してコード変更を分析します。タスク完了後、主要な機能の実装後、またはmainブランチへのマージ前などに使用すべきです。このレビューは、現在の実装と元の計画を比較することで、問題を早期に発見するのに役立ちます。
connect-mcp-server
デザインこのスキルは、開発者がHTTP、stdio、またはSSEトランスポートを使用してMCPサーバーをClaude Codeに接続するための包括的なガイドを提供します。GitHub、Notion、カスタムAPIなどの外部サービスを統合するためのインストール、設定、認証、セキュリティについて解説しています。MCP統合のセットアップ、外部ツールの設定、またはClaudeのModel Context Protocolを扱う際にご利用ください。
web-cli-teleport
デザインこのスキルは、タスク分析に基づいて開発者がClaude Code WebとCLIインターフェースの選択を支援し、これらの環境間でのシームレスなセッションテレポーテーションを可能にします。Web、CLI、モバイル環境を切り替える際のセッション状態とコンテキストを管理することで、ワークフローを最適化します。様々な段階で異なるツールを必要とする複雑なプロジェクトにご活用ください。
