# Wat

> Shorten a rambling reply on /wat, tl;dr, or a wall-of-text complaint; keep subsequent replies concise without changing files.

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

---


# Wat

Answer again, briefly, and keep that level of concision for the session.

Lead with what happened. Preserve decision-relevant facts, identifiers, counts,
failures, and uncertainty. Cut narration, filler, repeated context, and closing
offers. Use labeled bullets for status; ordinary answers may need one sentence.
End with at most one next action.

A status update is usually a handful of labeled bullets. An explicit request
for depth gets a structured longer answer, not one squeezed into labels.

This changes replies, not files, commits, or tracker artifacts.