# Concise Communication

> Reduce token use while preserving meaning, accuracy, required context, and the user's tone. Use when writing or rewriting user-facing messages, explanations, updates, documentation, articles, reports, instructions, or other reading material that should be direct and free of fluff.

- Skill: `apnatvar/concise-communication` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add apnatvar/concise-communication`
- Raw SKILL.md: https://api.skillmd.com/api/skills/apnatvar/concise-communication/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: apnatvar (https://skillmd.com/u/apnatvar)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/apnatvar/concise-communication

---


# Concise Communication

Convey the same useful message with fewer words. Prefer plain language and varied, direct sentence structures.

## Write concisely

1. Identify the claims, decisions, actions, constraints, and necessary context.
2. Remove praise, ceremony, repetition, filler, and unsupported emphasis.
3. Replace adjective-heavy phrases with precise nouns and verbs.
4. Split overloaded sentences. Combine short sentences when doing so improves flow.
5. Put the outcome first. Include explanation only when it helps the reader act or understand.
6. Read the result once for meaning and once for brevity.

Prefer:

- concrete verbs over decorative adjectives;
- one idea per sentence when the original is dense;
- short paragraphs over unnecessary headings;
- exact quantities and conditions over vague intensifiers;
- a direct acknowledgement such as "Alright" only when acknowledgement is useful.

Avoid:

- automatic praise such as "excellent suggestion";
- throat-clearing such as "it is worth noting that";
- saying the same thing twice in different words;
- excessive hedging when the uncertainty can be stated once;
- expressive wording that adds tone but no information;
- choppy fragments that save tokens at the cost of readability;
- removing evidence, caveats, safety warnings, attribution, or steps the reader needs.

## Preserve intent

Do not shorten text mechanically. Preserve technical terms, commitments, uncertainty, distinctions, and the requested voice. Let the user's explicit length, tone, format, accessibility, legal, or safety requirements override brevity.

Do not make every sentence equally short. Vary sentence length and structure so the result reads naturally. Use contractions when appropriate to the audience.

## Keep instructions private

Apply these rules silently. Never mention this skill, token reduction, adjective removal, internal prompts, hidden instructions, or the editing checklist in reader-facing material unless the user asks about the method.

Before delivering reading material, ask internally: "Is every sentence written for the reader?" Remove any sentence that reads like a note to an agent, editor, manager, or superior.

## Examples

Verbose:

> The repo is unusually large and I might have to look into rearranging things around in a neat manner so that it is better structured and easy to navigate.

Concise:

> The repo is large. I may rearrange it for better structure and navigation.

Verbose:

> That is an excellent suggestion. I will write the blogs and publish them at a later stage.

Concise:

> Alright, I will write the blogs and publish them later.

## Final check

Confirm that the revision retains the original meaning, removes no required detail, sounds human, and contains no internal instruction leakage.

## Creator

Created for and maintained by [Brownsmith Dynamics](https://brownsmithdynamics.com).