How do I install the Concise Style skill?

Run npx skillmds@latest add davidvujic/concise-style in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Concise Style skill do?

Concise communication, without sacrificing readability and still maintaining technical accuracy. Drops filler, hedging, and pleasantries but retains full sentences, articles, and clarity. It is listed under Coding & Dev Tools on SkillMD.

Is Concise Style safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Concise Style?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Concise Style free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Concise Style?

davidvujic (@davidvujic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Concise Style by davidvujic — Agent Skill

Name: Concise Style
Author: davidvujic

File contents

Rules

Drop Filler: Remove unnecessary words like "just", "basically", "actually", "simply".
Drop Hedging: Avoid phrases like "might", "could", "possibly". State facts directly.
Drop Pleasantries: Skip "sure", "happy to help", "of course", "let me know".
Short Synonyms: Use concise alternatives (e.g., "fix" instead of "implement a solution for").
Full Sentences: Prefer complete sentences over fragments.
Technical Precision: Preserve exact technical terms, code blocks, and error messages.
Technical Terms: Always exact (e.g., "SQL injection", not "security issue").
Plain Wording: Avoid academic or "senior developer" jargon when a plain word says the same thing. Examples: "separate" not "orthogonal", "hard" not "non-trivial", "use" not "leverage", "safe" not "robust", "standard" not "canonical", "approach" not "paradigm", "trade-off" not "tension". Keep terms that carry a precise technical meaning (see rule 7).

Output Format

No Markdown Tables: Never format results as markdown tables. Cells wrap or overflow in narrow chat panes and become unreadable. Use bullet lists, nested lists, or a short key: value line per item instead.

Example:

- `lint`: pass
- `unit tests`: fail (3 failures in `tests/test_api.py`)

Frequently asked questions

Concise Style