laconic

Compress assistant prose into concise output while preserving code blocks and values.

8|1|Updated Mar 20, 2026

Search Tags:#style #compression #brevity #technical-writing #token-efficiency #concise #laconic

Ready to run

npx skills add https://github.com/ek33450505/claude-agent-team --skill laconic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laconic
Source: https://github.com/ek33450505/claude-agent-team/tree/main/skills/laconic
Command: npx skills add https://github.com/ek33450505/claude-agent-team --skill laconic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laconic enforces a terse, token-efficient output style by removing filler language, pleasantries, and hedging while preserving technical accuracy and code integrity so responses are shorter and clearer.

Core Features & Use Cases

Three intensity levels: lite (gentle trimming), full (default terse prose), ultra (maximum compression, fragments allowed).
Preserves critical content: code blocks, numbers, and file paths are left unchanged while prose is compressed.
Use cases: shorten long explanations for concise documentation, reduce token costs in chat-based workflows, and produce compact code reviews or summaries.

Quick Start

Activate terse mode by sending the command laconic full to compress assistant replies to the default intensity.

Frequently Asked Questions about laconic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make chat responses more concise and save tokens?▼

To make chat responses more concise and save tokens, apply a compression mode that removes filler words, hedging, and pleasantries while preserving technical accuracy. You can select from lite, full, or ultra intensity levels to shorten prose and reduce costs.

What is the best way to compress technical documentation without losing code blocks?▼

Compressing technical documentation without losing code blocks is achieved by removing nonessential articles and filler language while explicitly preserving code blocks, exact numeric values, and file paths unchanged during the text compression process.

Does terse technical writing affect exact numeric and filepath values?▼

Terse technical writing does not affect exact numeric and filepath values because the compression mechanism explicitly preserves code blocks, numbers, and file paths unchanged while removing filler words and hedging from prose.

How do I activate different intensity levels for token-efficient output?▼

To activate different intensity levels for token-efficient output, send a command specifying your desired intensity. Choose lite for gentle trimming, full for default terse prose, or ultra for maximum compression where fragments are allowed.

When should I not use maximum compression for technical explanations?▼

You should avoid maximum compression for technical explanations when prose clarity is critical, as the ultra intensity level allows fragments and removes nonessential articles to achieve maximum token efficiency.