# Summary Callout

> Adds a summary callout at the start of markdown notes using the format `> [!summary]`. Use when creating or editing markdown notes, docs, or knowledge-base content that should open with a concise overview.

- Skill: `michael-f-bryan/summary-callout` (Agent Skill)
- Install (CLI): `npx skillmds@latest add michael-f-bryan/summary-callout`
- Raw SKILL.md: https://api.skillmd.com/api/skills/michael-f-bryan/summary-callout/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: michael-f-bryan (https://skillmd.com/u/michael-f-bryan)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/michael-f-bryan/summary-callout

---


# Summary Callout

When creating or editing markdown notes, include a summary callout at the beginning (after frontmatter if present) using `> [!summary]`.

## Structure

- Place at the top of the note, after frontmatter
- Format: `> [!summary]` followed by the summary content
- Length: 1–3 sentences, or 3–5 bullet points for complex topics

## Content

- Capture the **core idea** without supporting detail
- Answer: *What is it?* and *Why is it important?*
- Include key relationships to other concepts when relevant
- Clear, direct, professional tone; active voice; present tense
- Avoid jargon unless essential

## Formatting

- Use *italics* or **bold** for critical terms
- Use backticks for code/technical terms
- Use bullet points for complex summaries
- Include essential `[[wikilinks]]` to related concepts only—don’t overload

## By context

| Context                 | Focus                                              |
| ----------------------- | -------------------------------------------------- |
| **Technical concepts**  | What it is and its primary purpose                 |
| **Entities**            | Type and key characteristics                       |
| **Educational content** | TL;DR with key insights and practical applications |

## Do

- Make the summary stand alone as a quick reference
- Include all essential elements
- Revise when main content changes
- Keep formatting consistent across notes

## Avoid

- Summaries that are mini-articles
- Vague phrasing (“This note is about X”)
- Too many links
- Duplicating the first paragraph
- Relying on external context the reader doesn’t have