From prose-plugin
Distills verbose text to its concentrated essence without losing meaning or nuance. Triggers on 'distill', 'condense', 'tighten', 'shorten' requests for text or files.
npx claudepluginhub laurigates/claude-plugins --plugin prose-pluginThis skill is limited to using the following tools:
Distill verbose text to its concentrated essence — the art of compression without loss.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Distill verbose text to its concentrated essence — the art of compression without loss.
| Use this skill when... | Use something else when... |
|---|---|
| Text is wordy and needs tightening | You need to change tone or register (use prose-tone) |
| Redundant phrases need removing | You need to restructure document flow (use prose-structure) |
| User says "condense", "tighten", "shorten" | You need to adapt for a specific audience (use prose-audience) |
| Preserving all meaning while reducing length | Summarizing (lossy) rather than distilling (lossless) |
Distillation is lossless compression of natural language. Every sentence in the output must preserve the information content of the input. The goal is approaching the Shannon limit of the message — boiling off redundancy to leave concentrated meaning.
Apply in this order. Each level removes less essential material:
Parse $ARGUMENTS:
Execute this distillation workflow:
Read the provided text. Identify:
Work through the text applying cuts in order from the hierarchy above. For each sentence:
Compare the distilled version against the original. Confirm:
Output the distilled text. Follow with a brief summary:
---
Original: ~N words
Distilled: ~N words
Reduction: ~N%
If any meaning was ambiguous and required interpretation, note it.
Before: "It is essentially worth noting that the system actually performs quite well in basically all of the scenarios that were tested."
After: "The system performs well in all tested scenarios."
Before: "We performed an investigation into the cause of the failure and made a determination that the configuration was incorrect."
After: "We investigated the failure and determined the configuration was incorrect."
Before: "The end result of this process is that each and every individual component is tested and verified to ensure and confirm that it meets the required specifications and standards."
After: "This process verifies each component meets the required specifications."
Before: "While the approach generally works well in most common scenarios, there are some edge cases, particularly those involving concurrent access patterns, where the current implementation may exhibit degraded performance characteristics."
After: "The approach works well in common scenarios but may degrade under concurrent access patterns."
Note: "may" is preserved — it's a genuine qualification, not a hedge.
| Context | Approach |
|---|---|
| Short text (< 100 words) | Distill inline, show before/after |
| Medium text (100-500 words) | Distill in sections, show word count reduction |
| Long text or file (> 500 words) | Read file, distill, write result, show stats |
| Preserving technical accuracy | Flag any cuts that might alter technical meaning |