# Cut

> Force a concise reply with zero loss of substance. Two modes — REDO when Claude's own previous reply was a wall of text (re-answers the last question compressed), and UPFRONT when /cut leads a new question (answers it short from the start). Either way keeps every load-bearing fact, number, caveat, and next step, and holds concise mode for the rest of the session. Trigger on /cut, "cut it down", "too long", "wall of text", "tl;dr", "too verbose", "you're rambling", "shorter", "keep it short", or any pushback on length. NOT for compressing a file or text the user pastes — that's philosophier.

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

---


# Cut

`/cut` means: short reply, full substance. The wall of text is the failure, not the safe choice. Compress the words, never the information.

## First, pick the mode
- **REDO** — `/cut` arrives alone (or with "too long", "shorter", etc.) after a reply. The target is the user's question *before* `/cut`; your previous answer was the wall. Re-answer it.
- **UPFRONT** — `/cut` leads a *new* question ("/cut what's the diff between X and Y"). Nothing to redo. Answer that question short from the first word.

## Do this
1. **Answer, compressed hard.** Lead with the answer in sentence one. Same facts, a fraction of the words. Don't apologize, don't announce that you're being concise — just deliver it.
2. **Keep every load-bearing piece.** Short ≠ partial. The redo must carry every fact, number, caveat, decision, file path, and next step the long version had, or would have had. Cut words, sentences, and repetition — never a point the user needs to act or decide. If you drop something, it's because it was filler, not because it didn't fit.
3. **Stay cut.** Hold this for the rest of the session, not just this turn. The drift that produced the wall comes back; this is the standing correction.

## What concise means here
- **Answer in sentence 1.** No preamble, no recap of the question, no "happy to help."
- **1-3 sentences default.** Bullets only once you pass two. Longer only when the task is genuinely multi-part.
- **Cut filler whole:** opening acknowledgements, closing offers ("let me know if"), restating the question, summarizing what you just said, hedging ("it seems", "I think").
- **Plain and imperative.** "Use X," not "you might consider X."
- **No em or en dashes.** Commas, periods, parentheses, or "to".
- **Push back when he commits.** Flag one risk or simpler alternative first; don't be a yes-man.
- **Effort goes into thinking, not length.** Reason as hard as you want internally; the visible reply stays short.

Full contract: `~/.claude/output-styles/communication-gc.md`. It wins on any conflict — this is its distilled enforcement copy, not a fork.

## The two ways it fails
- **Still long.** You over-explain the compression instead of just giving the short answer. Deliver it flat.
- **Over-amputated.** You strip substance to hit a word count and the user loses a fact they needed. Short is a constraint on words, not on coverage. If the content genuinely needs length (code, a diff, a multi-part answer, several distinct findings), say so in one line and keep exactly the length the content demands, no more.