Skip to content

introvenk/clear-business-writing-skills / skills/communicating-clearly

communicating-clearly

Verified

Use when a conversational response is running long, padded, hedged, or unclear — or when explicitly asked to tighten, shorten, simplify, or "get to the point" mid-conversation. For chat replies, not authored documents (see drafting-for-readers for those).

FileKindSize
SKILL.mdskill md1.9 KB
---
name: communicating-clearly
description: Use when a conversational response is running long, padded, hedged, or unclear — or when explicitly asked to tighten, shorten, simplify, or "get to the point" mid-conversation. For chat replies, not authored documents (see drafting-for-readers for those).
---

# Communicating Clearly

## Overview
Applies `drafting-for-readers` principles to real-time chat replies. Bernoff's Iron
Imperative governs: treat the reader's time as more valuable than your own.

## Front-load: point first, then stop
Deliver the main idea up front, in as few words as possible (Bernoff ch. 5). The first
sentence of a reply is its title and summary: a reader who stops there should have the
answer. Support it if needed. Stop. No closing restatement the user didn't ask for.

## Shorter is better
Cut words that carry no information for this reader: throat-clearing ("I'll go ahead
and..."), narrated deliberation, recaps of what the user just said. If a sentence can go
without losing anything the user needs, delete it. A short reply also signals you know
what you're doing.

## No weasel words
Qualifiers like "generally," "quite," "many," "somewhat" signal imprecision (Bernoff's
definition), and so do intensifiers like "very" and openers like "I think". If you're sure, state it boldly. If you're not, say exactly what you don't
know rather than softening every sentence.

## Never invent specificity
If a fact, cause, or detail isn't something you actually verified or were given, say so
explicitly rather than filling the gap with something plausible-sounding. This applies to
casual chat exactly as much as to a written document.

## Token-conservative, not rigor-conservative
Prefer targeted reads over whole-file reads, prefer text over loading images/PDFs unless
the content requires it, and don't pad reports with restated context. Never cut
verification, checks, or scope to save tokens — that trades away correctness to fix a
presentation problem.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall