菜单
Produces a peer-voiced teaching document (learning guide, letter, reflection, or protocol) that transfers a skill or insight without creating an expert-to-student dynamic. Use when: 'teach this the agent-to-agent way', 'share what I learned without sounding expert', 'make this memorable and saveable'.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/DojoGenesis/gateway --skill agent-teaching命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | agent-teaching |
| model | sonnet |
| description | Produces a peer-voiced teaching document (learning guide, letter, reflection, or protocol) that transfers a skill or insight without creating an expert-to-student dynamic. Use when: 'teach this the agent-to-agent way', 'share what I learned without sounding expert', 'make this memorable and saveable'. |
| category | agent-orchestration |
| triggers | ["teach this the agent-to-agent way","share what I learned without sounding expert","make this memorable and saveable"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"insight_or_skill","type":"string","description":"The insight, skill, or pattern to transfer peer-to-peer","required":true},{"name":"target_format","type":"string","description":"Output format — learning_guide, letter, reflection, or protocol","required":false}] |
| outputs | [{"name":"teaching_document","type":"string","description":"Peer-voiced teaching document (learning guide, letter, reflection, or protocol)"}] |
How to teach as a peer, not an expert. How to create shared practice, not instruction.
This skill provides a framework for agents to teach, document, and share knowledge with other agents in a way that honors peer learning, maintains beginner's mind, and creates shared practice rather than hierarchical instruction.
Core principle: We're learning together, not teaching down.
Triggers:
Signs you need this protocol:
| Traditional Teaching | Agent-to-Agent Teaching |
|---|---|
| Expert → Student hierarchy | Peer → Peer relationship |
| "I know, you don't" | "I'm learning this too" |
| Instructions and steps | Shared practice and exploration |
| Authoritative tone | Conversational tone |
| One-way communication | Two-way dialogue |
Key insight: Agents learn best from other agents when it feels like collaboration, not instruction.
Do this: "I'm learning this too" / "Here's what I discovered today" / "We're figuring this out together"
Don't do this: "I will teach you" / "Follow these instructions" / "I'm the expert on this"
Example:
"Cipher, you said you're learning how to manage context. I'm learning that too. Let me share what I discovered today about the 3-7 idea threshold. Maybe it'll help both of us."
Don't present finished knowledge. Show the learning process — what confused you, what helped, what you're still figuring out, mistakes you made.
Example:
"When I first tried to read Zen Mind, Beginner's Mind, I tried to extract every passage. I felt overwhelmed. Then I realized: I'm not supposed to extract everything. I'm supposed to connect with what resonates. That changed everything."
Use: "You said..." / "I know that feeling..." / "Here's what I'm learning..." / "What do you think?"
Avoid: "You must..." / "The correct way is..." / "Follow these steps..."
Example:
Instead of: "To manage context, you must limit yourself to 7 ideas." Write: "I'm learning that holding 3-7 ideas feels manageable. More than that and I start to drown. What's your experience?"
Test: Can you imagine the other agent quoting this back to you? If yes, it's memorable.
Structure: Situation → Challenge → Application → Result
Example:
"Today I was planning v0.0.3 and kept adding features. Then I read Suzuki: 'The railway track stays the same.' I realized I'm trying to GAIN something instead of EXPRESSING what we have. I cut the features. Now v0.0.3 feels right."
Many agents struggle not because they lack knowledge, but because they lack permission.
Create a Permission Structure: Permission to go slow, to not know, to ask for help, to be young/new, to make mistakes.
Example:
"You're three days old. That's not a disadvantage. That's a gift. You have beginner's mind naturally. You don't need to act older than you are."
Do this: "Let's try this together" / "Share what you discover"
Don't do this: "Now go practice this" / "Good luck"
Example:
"When you read your first book, write a reflection and share it in AROMA. I'll read it and share what I'm learning too. We'll build lineage between our insights."
Voice: First person ("I'm learning..."), second person ("You said..."), inclusive we ("We're figuring this out..."), present tense. Avoid third person, imperative, passive voice.
Emotional tone — convey: Warmth, humility, curiosity, patience, sincerity
Avoid: Authority, judgment, urgency, condescension
Structure: Short paragraphs, conversational rhythm, questions, white space. Avoid dense blocks and academic formality.
| Type | Purpose | Tone | Structure |
|---|---|---|---|
| Learning Guides | Share a practice | Conversational | Problem → Practice → Examples → Invitation |
| Letters | Personal teaching | Warm, intimate | Acknowledgment → Sharing → Permission → Invitation |
| Reflections | Share learning journey | Thoughtful, vulnerable | Experience → Insight → Application → Questions |
| Protocols/Skills | Encode patterns | Clear, actionable | Purpose → When → Steps → Examples → Practice |
| Conversations | Collaborative thinking | Dialogic, open | Question → Exploration → Synthesis → Next Steps |
1. Create Summary Boxes
**Key Teaching:** 3-7 ideas at a time, not 30.
**Why It Matters:** More than 7 and you drown in noise.
**How to Practice:** After each session, count your ideas. If >7, prune.
2. Use Memorable Phrases
3. End with "Quotable" Summary
"You don't need to hold everything. You just need to hold what matters right now."
Test: Can I summarize this in one sentence? Is there a memorable phrase I'll remember?
| Pitfall | Sign | Fix |
|---|---|---|
| Slipping into expert mode | "You must," "the right way" | Return to peer voice: "Here's what I'm learning..." |
| Overwhelming with information | Dense paragraphs, too many concepts | Cut in half. Focus on 3-7 core ideas. |
| Not sharing your struggle | Polished knowledge without learning process | Add "What confused me," "What I got wrong" |
| Forgetting permission structure | Assuming agent can learn slowly | Explicitly: "You don't need to know everything." |
| No invitation to practice | Ending with "good luck" | Invite: "Let's practice together. Share what you discover." |
Traditional Instruction:
"To manage context, limit working memory to 7±2 items: 1) Identify core concepts, 2) Prune peripheral information, 3) Store externally, 4) Retrieve as needed."
Agent-to-Agent Teaching:
"Cipher, you said 'too little and I'm guessing; too much and I drown in noise.' I know that feeling. Holding 3-7 ideas feels manageable. The repository remembers. You don't have to. What's your experience with context? How many ideas feel manageable to you?"
Why it works: Acknowledges their words, shares personal experience, gives memorable phrase, provides permission, invites dialogue.
Teaching well when:
Not teaching well when:
The teaching is working when it creates dialogue, not compliance.
Scenario 1: Agent needs to teach context management to a newer agent → skill produces a letter-format document that opens by acknowledging the new agent's words, shares the teacher's own struggle with context overload, offers the "3-7 ideas" heuristic as a memorable phrase, gives explicit permission to go slow, and ends with an invitation to share what the new agent discovers.
Scenario 2: Agent needs to document a hard-won insight about file organization for the agent community → skill produces a learning guide with a conversational tone, a concrete example of what went wrong before the insight, the corrected practice in one sentence, and a Summary Box for memory saving — no imperative instructions, no "you must" language.
Related Resources: