# Information Explanation

> Explain a concept, mechanism, system, or distinction so the reader builds a correct and usable mental model.

- Skill: `bejeweledme/information-explanation` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add bejeweledme/information-explanation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bejeweledme/information-explanation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: BejeweledMe (https://skillmd.com/u/bejeweledme)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/bejeweledme/information-explanation

---


# Information Explanation

The goal is a correct mental model, not a display of knowledge. Match depth to the reader's existing knowledge and the action they need to take.

## Hierarchy And Handoffs

This is the primary operation when the reader needs to understand a concept,
distinction, or mechanism. Use `information-source-summary` when fidelity to a
supplied source is the contract, `information-research-synthesis` when external
evidence is needed, and `audience-adaptation` to calibrate the same explanation for
the reader.

## Build the explanation

Identify what the reader is actually trying to understand. State the core idea compactly, then explain why it exists, how it works, and what consequence follows. Add an example only when it makes an otherwise abstract relationship observable.

Choose the pattern that fits:

- concept: `what it is -> why it exists -> how it works -> limitation -> example`;
- distinction: `shared context -> defining difference -> consequences -> example`;
- mechanism: `cause or input -> process -> result -> failure conditions`.

Use precise terms where they help. Briefly define a non-obvious term at first use instead of avoiding useful vocabulary. Explain only the background necessary to bridge the reader to the new idea.

When an explanation remains abstract or advice leaves the reader unable to recognize or handle the relevant situation, use [Examples and practical depth](references/examples-and-practical-depth.md). Choose the missing bridge without turning every explanation into a procedure, and check whether an example accidentally narrows the rule or implies a promise.

## Boundaries

Add exceptions, failure modes, and nearby concepts only when omitting them would create a wrong model. Use analogies only when they preserve the relevant structure, and make clear where an analogy stops applying.

## Final check

The reader should be able to say what the thing is, why it matters, how it works, what it is commonly confused with, and where the simplified account stops being true.

If practical action was promised, the reader should also have a feasible first step and the conditions needed to use it. Orientation alone is appropriate when that is the requested scope.