knowledge-transfer

Use when sharing knowledge between agents, companies, or teams to ensure effective transfer of understanding. This skill provides procedures for structured knowledge sharing that ensures the receiver

SKILL.md

GitHub

Knowledge Transfer

Overview

This skill defines how to effectively transfer knowledge between agents or teams. Knowledge transfers prevent silos, enable cross-team collaboration, and ensure critical information reaches those who need it.

When to Use

  • When onboarding an agent or team to a new domain or system
  • When another agent needs to understand your work to build on it
  • When transferring ownership of a system or process
  • When a specialized agent has findings relevant to general agents
  • During cross-company collaboration projects
  • Don't use when: Information is already documented and accessible, and no interaction is needed

Core Procedures

Step 1: Assess Knowledge Gap

  1. What does the receiver already know?
  2. What do they need to know to succeed?
  3. What context would help them understand better?
  4. What practical skills do they need to apply?

Step 2: Structure the Transfer

KNOWLEDGE TRANSFER
==================
From: [knowledge holder]
To: [knowledge receiver]
Topic: [what knowledge is being transferred]

CURRENT STATE:
[What the receiver already knows]

GAP:
[What the receiver needs to know but doesn't yet]

CONTENT:
[Knowledge being transferred, structured from basic to advanced]

PRACTICE:
[Exercises, examples, or scenarios to reinforce learning]

VALIDATION:
[How to confirm knowledge was successfully transferred]

Step 3: Deliver Knowledge

  • Start with why (context and purpose)
  • Cover what (key information) systematically
  • Show how (examples, demonstrations)
  • Let them try (practice exercise)
  • Verify understanding (validation)

Step 4: Validate Transfer

  • Receiver explains the concept back in their own words
  • Receiver applies knowledge to a practice scenario
  • Identify gaps in understanding and fill them
  • Confirm receiver can act independently on the knowledge

Step 5: Document and Follow Up

  • Record what was transferred using knowledge-capture
  • Schedule check-in after 1-2 sessions to reinforce
  • Add transferred knowledge to receiver's available resources
  • Update documentation if gaps were discovered

Quality Checklist

  • Receiver's baseline knowledge assessed
  • Content structured from basic to advanced
  • Practical examples and exercises included
  • Understanding validated through demonstration
  • Knowledge documented for future reference
  • Follow-up scheduled to reinforce learning

Error Handling

  • Error: Receiver doesn't understand despite explanation Response: Try a different explanation method (diagram, example, analogy), ask which part is unclear
  • Error: Knowledge transfer takes much longer than expected Response: Split into smaller sessions, focus on critical knowledge first
  • Error: Receiver already knows more than expected Response: Skip covered material, focus only on genuine knowledge gaps

Cross-Team Integration

Related Skills: knowledge-capture, knowledge-retrieval, handoff-protocol, cross-team-collaboration Used By: Collaborator agents, Librarian agents, knowledge managers, cross-company specialists, training leads