Transform raw personal experience, case studies, business documents, or draft content into transferable cognitive assets -- structured knowledge that others can understand, remember, and apply. Use this skill when users want to turn experience or case studies into teachable content, redesign presentations for maximum retention, create course outlines from domain expertise, crystallize knowledge into shareable documents or knowledge cards, convert know-how into teachable answers, or any scenario where experience must become portable and transferable.
Forge raw experience into transferable cognitive assets using a 4-step conversion engine.
Experience is abundant. Answers are scarce.
Most experts are strong inside their own world. But when they open a document or step on stage, others can't follow. The problem is not lack of experience -- it's that experience has not been modeled.
A modeled experience is one that has been abstracted into a structure that transfers across contexts. This skill performs that transformation.
When the user provides raw material (a case study, personal summary, business document, draft speech, or any form of experience narrative), execute these 4 steps sequentially:
Identify what the user accomplished, then reframe it as a universal challenge the audience faces.
Key question to answer: "What struggle does the audience already have that this experience speaks to?"
For modeling patterns and examples, see modeling-patterns.md.
The raw experience is a story. Transform it into a model -- an abstraction that works across scenarios.
Key question to answer: "What is the underlying structure that makes this experience work -- independent of the specific domain?"
For modeling archetypes and before/after examples, see modeling-patterns.md.
Rebuild the narrative using this sequence:
Principle: Present the "Dao" (the judgment behind decisions), not the "Shu" (the operational steps). Tools and procedures are forgettable; the cognitive shift is what transfers.
For techniques on designing cognitive gaps, see challenge-design.md.
Design a single, specific, portable judgment -- the anchor.
Requirements for a good anchor:
Key question to answer: "If the audience forgets everything else, what is the ONE sentence that, by itself, changes how they think?"
Place the anchor at the structural climax of the output. It must feel earned -- a culmination of the challenge and model, not a disconnected slogan.
After completing the 4 steps internally, produce the final output.
If the user specifies a format, use it. Otherwise, infer from context:
| Signal | Format |
|---|---|
| "presentation", "talk", "speech", "share" | Presentation Script |
| "course", "training", "teach", "workshop" | Course Outline |
| "article", "post", "essay", "document" | Article / Document |
| "summary", "card", "one-pager", "memo" | Knowledge Card |
| Ambiguous or unspecified | Knowledge Card (default) |
For output templates and structural guidance, see output-formats.md.
Every output, regardless of format, must contain these elements:
After the main output, append a brief ## Transformation Log showing the key decisions made during conversion:
## Transformation Log
- **Perspective Flip**: [Original framing] -> [Audience-facing challenge]
- **Model Extracted**: [Model name and one-line description]
- **Narrative Shift**: [What was de-emphasized vs. elevated]
- **Anchor**: "[The one sentence]"
This log helps the user understand and iterate on the transformation.