Wat

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

uinaf 93edfa6 10 files · 11.1 KB Updated

File contents

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.

uinaf/ffsstack/tree/main/skills/wat commit 93edfa6465

Frequently asked questions

npx skillmds@latest add uinaf/wat