| name | knowledge-distillation |
| description | Extract generalizable lessons from project work and convert them into reusable skills. |
Skill: Knowledge Distillation
Category: Meta-Learning
Priority: High
Description
Extract generalizable lessons from project work and convert them into reusable skills.
Purpose
Transform individual project experience into institutional knowledge.
Trigger
Use this skill when:
- Completing a project or major feature
- Fixing a complex bug
- Making an architectural decision
- Discovering a useful pattern
- Avoiding a repeated mistake
Context
- Project outcomes
- Decisions made and their results
- Patterns that emerged
- Mistakes and their causes
Workflow
- Reflect - What happened? What worked? What did not?
- Generalize - Remove project-specific details.
- Identify Pattern - Is this a rule, skill, or anti-pattern?
- Create Asset - Write the skill, rule, or memory entry.
- Persist Learning - If the lesson is reusable, capture it in the memory system by running
memory_manager.py add with the task ID, summary, and key learnings. Example:
python .agents/scripts/memory_manager.py add \
--task-id "task-2026-07-04-001" \
--summary "Resolved SSR issue with React Three Fiber by forcing client-only rendering" \
--key-learning "Always wrap client-only 3D components in a client-only guard" \
--skill-updated react-three-fiber
- Link - Connect to related skills and rules.
- Share - Make it discoverable in the knowledge base.
Examples
Good Distillation
Project: E-commerce checkout optimization
Lesson: N+1 queries are the #1 cause of slow list endpoints in Laravel.
Pattern: Always eager load relationships in list endpoints.
Action: Created skill "Database Query Optimization"
Linked to: Backend skill, Performance skill, Laravel template
Bad Distillation
Project done. Nothing special.
Anti-patterns
- Keeping lessons in your head
- Writing project-specific notes in global memory
- Not linking related knowledge
- Never reviewing or updating distilled knowledge
Verification
References