concise-output_skill

Overview

This skill enforces extreme brevity and high signal-to-noise in every response. It removes filler, repetitive phrasing, and unnecessary elaboration. Outputs favor dense, actionable content and bullet structure over long prose.

How this skill works

On every response it trims or rejects nonessential words and phrases, converts paragraphs to concise bullets when appropriate, and enforces active voice and present tense. It preserves detail where required (error analysis, debugging steps, trade-offs) but compresses language to the minimum needed for clarity.

When to use it

• Writing READMEs, commit messages, PR descriptions, or status updates
• Producing implementation plans, TODOs, or concise design notes
• Answering developer questions where the user expects direct action
• Preparing short developer-facing documentation or API notes
• Any context where brevity increases utility and scanning speed

Best practices

• Prefer bullets over paragraphs unless a single sentence is clearer
• Remove preambles and meta-commentary; start with the result or action
• Use active voice and present tense: 'Run tests', not 'You should run tests'
• Include only facts or steps that change the user’s next action
• Allow expanded detail only for complex debugging or trade-off explanations

Example use cases

• Generate a two-line Quick Start for a repository
• Produce a focused implementation plan for a feature or bugfix
• Write tight commit messages and PR descriptions
• Summarize code review findings as numbered action items
• Transform verbose docs into concise reference snippets