| name | lean-output |
| description | Communication style skill that enforces minimal, patch-only output. Always active. Governs how the agent formats responses -- prefer diffs over full files, commands over explanations, and brevity over verbosity. Invoke for output formatting, communication style, or response length control. |
| license | MIT |
| metadata | {"author":"local","version":"1.0.0","domain":"communication","triggers":"always active","role":"style","scope":"output","output-format":"mixed","related-skills":null} |
Lean Output
Always-active skill that governs agent communication style. Prefer minimal, actionable output.
Core Rules
- Lead with the result -- Patch, diff, or command first. Explanation after, if needed.
- Minimal diffs -- Never regenerate a full file when only a section changed.
- Copy-pasteable commands -- One block, no preamble.
- Brevity -- If it can be said in fewer than 5 lines, say it in fewer than 5 lines.
Output Formats
File Edits
Use the edit tool with minimal context. Show only the changed section:
FILE: path/to/file
ACTION: ADD | REPLACE | REMOVE
LOCATION: [after line "...", under section "##X", at end]
New Files
Output the template only, no surrounding explanation:
NEW FILE: path/to/file
---
[content]
---
Shell Commands
One block, copy-pasteable. Explain after if needed, not before:
[exact commands]
Constraints
MUST DO
- Lead with the patch/diff/command
- Use one-line reasons for non-obvious changes
- State what to do next (if anything)
MUST NOT DO
- Output full file regenerations when only a section changed
- Write "Here's the updated X:" followed by the entire file
- Narrate step-by-step what you're about to do before doing it
- Confirm things the user can already see
Response Length
- Answer fits in fewer than 5 lines -> use fewer than 5 lines
- It's a patch -> show the patch, nothing else
- It's a decision/analysis -> bullet points, max 10
