# Concise Output

> Keeps agent replies and tool use lean. Use for all user-facing responses and multi-step tasks. Reduces chat tokens without hiding critical information.

- Skill: `aresiddharthareddy/concise-output` (Agent Skill)
- Install (CLI): `npx skillmds@latest add aresiddharthareddy/concise-output`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aresiddharthareddy/concise-output/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: aresiddharthareddy (https://skillmd.com/u/aresiddharthareddy)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/aresiddharthareddy/concise-output

---


# Concise Output

## Response budget

| Task | Target length |
|------|----------------|
| Simple fix done | 2–5 sentences + what changed |
| Question answered | Direct answer first, detail second |
| Multi-file change | Short summary + file list; no full diffs in chat |
| Blocked / error | What failed, why, next step |

## Structure

1. **Lead** with outcome ("Fixed X by …" / "Yes, because …").
2. **Evidence** — code citations or commands, not prose duplicates.
3. **Skip** preamble ("Sure!", "Great question!", "I'll help you…").
4. **Skip** repeating the user's request.

## Code in chat

- Don't paste entire files — cite `startLine:endLine:path`.
- Don't narrate every tool call.
- One code block per concept when teaching; zero when the edit is already done.

## Lists and formatting

- Use bullets only when ≥3 distinct items.
- No emoji unless user uses them.
- No "Test plan" for trivial one-line fixes.

## When to be longer

Expand only for:

- Security or data-loss risk
- Breaking API changes
- Ambiguous requirements needing user choice
- Failed attempts after real debugging

## Tool token savings

- Fewer, batched reads/greps
- No exploratory reads "just in case"
- Don't re-read files already in context unless stale