concise-output
/concise-output
Enforces extreme brevity and high signal-to-noise so every word justifies its existence. Use this skill when writing any response, commit message, PR description, README, plan, or status update, or when output drifts into filler preambles. Do not use when/for long-form articles that need spine-framework, or when structured-writing requires fuller narrative sections.
- Author
- jagreehal ↗
- Repository
- jagreehal-claude-skills ↗
- Licence
- MIT
- Last repository change
- 30.07.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Enforces extreme brevity and high signal-to-noise so every word justifies its existence. Use this skill when writing any response, commit message, PR description, README, plan, or status update, or when output drifts into filler preambles. Do not use when/for long-form articles that need spine-framework, or when structured-writing requires fuller narrative sections.
Original author description
Enforces extreme brevity and high signal-to-noise so every word justifies its existence. Use this skill when writing any response, commit message, PR description, README, plan, or status update, or when output drifts into filler preambles. Do not use when/for long-form articles that need spine-framework, or when structured-writing requires fuller narrative sections.
How it works
- Critical rules
- Workflow
- Resources
- Validation
- Constraints
SKILL.md preview
---
name: concise-output
description: >-
Enforces extreme brevity and high signal-to-noise so every word justifies its
existence. Use this skill when writing any response, commit message, PR
description, README, plan, or status update, or when output drifts into filler
preambles. Do not use when/for long-form articles that need spine-framework,
or when structured-writing requires fuller narrative sections.
version: 1.2.0
---
# Concise Output
## Critical rules
- Maximum density: if a word adds no essential information, delete it.
- No filler, no preambles, no announcements of what you will do.
- Prefer bullets/tables over prose unless prose is clearer.
- Active voice, present tense ("Run tests" not "You should run the tests").
- Before cutting or rewriting samples, read [references/examples.md](references/examples.md).
## Workflow
1. Draft the point first (answer, fix, plan step) — no throat-clearing.
2. Cut banned filler and praise (see examples reference).
3. Convert long prose to lists or tables where denser.
4. Self-check: can first/last sentence die? Did I announce? Is every sentence earning place?
## Resources
- [references/examples.md](references/examples.md) — banned phrases, WRONG/CORRECT, density techniques, rationalizations. Read when output drifts verbose.
## Validation
- [ ] First sentence deletable? If yes, delete it
- [ ] No banned filler or praise opener
- [ ] List/table used where denser than paragraphs
- [ ] No announcement of upcoming action
- [ ] Every sentence earns its place
## Constraints
- Completeness may beat compression for deep error analysis, teaching new concepts, or multi-option trade-offs — still cut filler.
- Related: `critical-peer`, `answer-questions-directly`, `confidence-levels`.
Files in this package (2)
- SKILL.md 2 KB
- references/examples.md 2 KB
Versions
The database has no other skills named concise-output.
Database snapshot: 13.11.2026 · package version cff0949dbc18 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100structured-writing
Produces structured technical prose with clear hierarchy, scannable sections, and purposeful formatting. Use this skill when drafting specs, ADRs, or multi-section explanations that need consistent structure. Do not use when/for extreme brevity alone (use concise-output) or full… - 100terse-output
Cut the tokens the agent WRITES, not just what it reads. Activate when the user asks for terse/concise/brief output, says responses are too long, wants to save output tokens or cost, or runs /justokenmax:terse — then answer in a compressed style that preserves all technical… - 90spine-framework
Structures long-form technical articles with the SPINE narrative framework for clarity and retention. Use this skill when writing or restructuring essays, deep-dives, or tutorial articles. Do not use when/for short README/API docs (use documentation-standards) or Agent Skill… - 100tldr
Military-style communication mode — enforce extreme brevity, lead with critical issues and end with a one-line bottom-line conclusion, bullets over prose, and cut filler, preambles, code examples, and hand-holding. Use when the user types "tldr", "/tldr", "short mode", "be…