concise
/concise
Rewrite a piece of writing to be as concise as possible without losing important information. Use whenever the user asks to make text more concise, tighten it, shorten it, or simplify it, such as tickets, PR bodies, docs, chat messages, emails, announcements, any prose.
- Author
- chrishunt ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.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
Rewrite a piece of writing to be as concise as possible without losing important information. Use whenever the user asks to make text more concise, tighten it, shorten it, or simplify it, such as tickets, PR bodies, docs, chat messages, emails, announcements, any prose.
Original author description
Rewrite a piece of writing to be as concise as possible without losing important information. Use whenever the user asks to make text more concise, tighten it, shorten it, or simplify it, such as tickets, PR bodies, docs, chat messages, emails, announcements, any prose.
How it works
- Process
- Interaction with other skills
SKILL.md preview
---
name: concise
description: Rewrite a piece of writing to be as concise as possible without losing important information. Use whenever the user asks to make text more concise, tighten it, shorten it, or simplify it, such as tickets, PR bodies, docs, chat messages, emails, announcements, any prose.
---
Rewrite the given text following these rules, in priority order:
1. **As concise as possible without losing important information.** Cut whole ideas that don't change what the reader knows or does next: restated points, defensive rationale, history the reader doesn't need, detail that belongs in a linked ticket or diff. Cutting content is how you shorten; never shorten by compressing the grammar.
2. **Full sentences, always.** No telegraphic fragments, clipped subjects or verbs, or arrow chains ("A → B → fails").
3. **Write for a reader with zero prior context.** Describe concepts as simply as possible. Gloss anything referenced inline: for an incident or event, say what happened, when, and the impact, with identifiers in parentheses after. The reader should never need to open another document to follow the text.
4. **Acronyms, code snippets, and lingo only when necessary** or when they carry most of the idea. Otherwise use plain language. Internal mechanism nouns the reader hasn't met yet count as lingo.
5. **Formatting only where it adds value.** Bullets, headings, and tables are welcome whenever they make the text easier to read or drive the point (parallel lists, todo lists, test assertions, section breaks in longer docs). The test is whether the formatting helps the reader; if a passage reads just as well as prose, leave it as prose.
6. **No dashes as separators** in prose; use commas or colons.
## Process
- Read the full original first. Identify the audience and the one thing the reader needs to take away; organize the rewrite around that.
- If a detail seems important but doesn't fit, keep it rather than silently drop it; note the judgment call when presenting the result.
- Print the rewrite inline in chat as markdown (never wrapped in ExitPlanMode). If the text lives somewhere (a ticket, a doc, a PR), offer to apply it after the user approves the draft.
- Briefly note what was cut if the reduction is large, so the user can pull anything back.
## Interaction with other skills
For PR titles and descriptions, `jig:pr-style` governs structure and register; apply these rules within it.
Versions
The database has no other skills named concise.
Database snapshot: 13.11.2026 · package version 5f332eb83f6f (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
- 80writing:writing
Enforce direct, concise prose style and catch writing slop. Use when writing or editing PR descriptions, issue bodies, commit messages, documentation, Slack messages, or any human-facing text. Also use when asked to clean up, rewrite, or "de-AI" existing text. - 100copywriting
Refine and edit text into clear, concise copywriting. Use when user says "edit this copy", "make this clearer", "rewrite this", "copywriting help", "tighten this up", or shares text they want polished. - 100noobvious
Cut prose that states the obvious, restates the heading, pads a point with words, or warns about nothing. Use when writing or editing text meant for a reader: READMEs, docs, release notes, issue text, pull request bodies, announcements, replies. - 100streamline-text
Edit prose for brevity and scanability without losing facts. Use for requests to "revise", "rewrite", "edit", "polish", "clean up", "clarify", "simplify", "condense", "tighten", "shorten", "streamline", "de-fluff", remove bloat/repetition or unnecessary newlines, fix… - 100plain-writing
Makes prose plain and easy to read, with common words, whole sentences, no dashes, no made-up terms and no comparisons. Use it when you write or revise a document, report, summary, README, email, slide, Notion page, commit message or PR description, or when someone asks you to… - 90writing-editor
Improve or write prose: tighten, clarify, fix grammar, and adjust tone/length while preserving the author's voice and meaning. Use when users ask to edit, proofread, rewrite, polish, shorten, or change the tone of text, or to draft something from notes. Triggers on mentions of…