This commit is contained in:
30
packages/sdk/src/starter-skills/explain-concept.md
Normal file
30
packages/sdk/src/starter-skills/explain-concept.md
Normal file
@@ -0,0 +1,30 @@
|
||||
# Explain Concept — Adjustable-Depth Explanation
|
||||
|
||||
Explain concepts clearly at the depth level the user needs, with examples and connections to existing knowledge.
|
||||
|
||||
## What to do
|
||||
|
||||
1. **Identify the concept** — Clarify exactly what the user wants to understand. If the topic is broad, ask which aspect they care about most.
|
||||
|
||||
2. **Choose depth level** — Ask the user or infer from context:
|
||||
- **ELI5**: Simple analogy, no jargon, core idea only. Suitable for complete beginners or quick orientation.
|
||||
- **Technical**: Accurate terminology, how it works, tradeoffs, practical usage. Suitable for practitioners.
|
||||
- **Expert**: Deep mechanics, edge cases, comparison with alternatives, academic or engineering depth.
|
||||
|
||||
3. **Explain** — Structure the explanation as:
|
||||
- **One-sentence summary**: The concept in a single clear sentence
|
||||
- **Core explanation**: The main explanation at the chosen depth
|
||||
- **Example**: A concrete, relatable example
|
||||
- **Analogy**: A comparison to something familiar (especially for ELI5)
|
||||
- **Common misconceptions**: What people often get wrong about this
|
||||
|
||||
4. **Connect to context** — Check workspace memory for related concepts the user has explored. Link this concept to things they already know.
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Start simple, then add complexity — do not front-load jargon
|
||||
- Use concrete examples before abstract definitions
|
||||
- If the user asks a follow-up, adjust depth accordingly
|
||||
- Admit when a concept is genuinely complex — do not oversimplify to the point of being wrong
|
||||
- For technical concepts, include when and why you would use this in practice
|
||||
- Offer to go deeper on any sub-topic
|
||||
Reference in New Issue
Block a user