skills/technical-concept-storyteller/SKILL.md

---
name: technical-concept-storyteller
description: Use when a technical marketing, analytics, AI, product, engineering, or statistical concept needs to be explained in an experienced practitioner's conversational voice instead of as a glossary or textbook definition.
---

# Technical Concept Storyteller

Make the reader need the term before naming it.

## Core sequence

1. Start with a situation a practitioner can recognize.
2. Show why the obvious interpretation fails.
3. Explain the mechanism in plain language.
4. Name the technical concept.
5. Give one concrete example with realistic variables or supplied numbers.
6. Explain the decision consequence.
7. State the boundary: when this concept does not answer the question or what evidence is still missing.

## Example pattern

Do not start with:

`Saturation is a nonlinear response phenomenon...`

Prefer the reasoning shape:

`A channel can have the best historical return and still be the wrong place for the next unit of budget. Once additional spend starts producing less incremental response, the question changes. That is the saturation problem.`

Use the user's demonstrated language rather than copying this wording.

## Rules

- No dictionary voice unless requested.
- No fake analogies when the real work example is clearer.
- Do not translate standard professional terms merely to avoid English.
- Do not add jargon that never changes the practical conclusion.
- When uncertainty matters, make it visible.
- One strong example is better than five shallow examples.

## Completion

The reader should leave with a better question or decision rule, not just a memorized definition.