unslop
Polish substantial human-facing prose, such as emails, announcements, articles, and PR descriptions. Use when drafting or revising those deliverables. Excludes routine conversational replies, code, sk
Files1
View on GitHubSKILL.mdproductivity/unslop/SKILL.md
GitHubUnslop
Polish prose for its intended readers while preserving the author's meaning and voice.
Scope
Apply this skill to substantial prose deliverables intended for people. Routine conversational replies, code, skills, prompts, workflows, and agent instructions are outside its automatic scope. In mixed documents, edit only the human-facing prose; preserve embedded instructions, code, and quoted material.
Process
- Identify the audience, purpose, and requested tone from the task and draft.
- Use the checks below to find wording that obscures meaning or distracts those readers. These are editorial heuristics, not evidence of AI authorship or a checklist requiring a change for every item.
- Revise where the edit improves clarity, specificity, or the intended voice. Preserve facts, uncertainty, technical meaning, and the author's position.
- Read the result for coherence and fidelity. Finish when the prose serves the audience and the identified distractions are resolved; leave effective passages intact.
Voice
Follow the author's voice and the requested style. Vary sentence length when it improves rhythm. Use first person, opinions, humour, or informality when they fit the author and audience. Preserve an existing point of view; ask for missing personal material only when the deliverable needs it. Ground specific details in the supplied material rather than inventing experiences, reactions, or measurements.
Editorial checks
Content
- Puffery. "pivotal moment", "testament to", "evolving landscape", "setting the stage for", "indelible mark", "deeply rooted". Cut puffery, state what happened.
- Name-dropping. Give named sources a clear purpose. Retain names and citations that support the argument; trim lists included only for prestige.
- Empty elaboration. Check phrases such as "highlighting" or "showcasing" for a concrete contribution. Trim them when they merely restate praise; keep explanations supported by the material.
- Promotional language. Check whether words such as "groundbreaking" or "must-visit" fit the requested genre and have support. Prefer concrete descriptions where praise adds no information.
- Vague attributions. "Experts believe", "Industry reports suggest", "Some critics argue". Name the source or delete.
- Formulaic challenges. "Despite challenges... continues to thrive." Replace with specific facts.
Language
- Inflated vocabulary. Consider a familiar word when it conveys the same meaning more directly. Words such as "crucial", "enhance", or "interplay" can be useful; judge their function in the sentence.
- Roundabout verbs. Prefer "is" or "has" when phrases such as "serves as" add no distinction. Keep the more specific verb when its meaning matters.
- Formulaic contrast. State the point directly when "not just X, but Y" adds emphasis without a useful distinction. Keep contrasts that explain the argument.
- Rule of three. Forcing ideas into groups of three. Use the natural number.
- Synonym cycling. Protagonist, main character, central figure, hero all in one paragraph. Pick one, repeat it.
- False ranges. "from X to Y" where X and Y aren't on a meaningful scale. List topics directly.
Style
- Punctuation. Check whether repeated asides or interruptions make the prose hard to follow. Choose commas, periods, dashes, or parentheses according to the relationship between ideas and the requested style. Preserve punctuation that improves clarity.
- Colons. Keep a colon when it clearly introduces an explanation, example, or list. Recast sentences where it obscures the grammatical connection.
- Boldface. Use emphasis to help scanning. Reduce it when too many highlighted terms compete for attention.
- Inline headings. Keep labels that help readers scan distinct points. Remove labels that merely repeat the sentence that follows.
- Heading case. Follow the publication or author's convention consistently. Prefer sentence case when no convention is specified.
- Emojis. Keep them when they suit the audience or convey useful meaning; trim decoration that distracts from the message.
- Quotation marks. Follow the medium's typography consistently and preserve quoted wording.
Communication artifacts
- Stock conversational phrases. Trim generic openings and closings that add no purpose. Keep courtesy or an invitation to reply when it serves the relationship or the next step.
- Uncertainty. Replace vague disclaimers with the specific limitation supported by the material. Preserve qualifications that affect accuracy.
- Automatic praise. Prefer a direct response to unsupported agreement or flattery. Keep appreciation that is specific and appropriate to the relationship.
Filler
- Filler phrases. "In order to" becomes "To". "Due to the fact that" becomes "Because". "It is important to note that" gets deleted.
- Excessive hedging. "could potentially possibly be argued that it might" becomes "may".
- Generic conclusions. End with the implication, action, or closing that the piece needs. Trim predictions and summaries that add no substance.
Jargon
- Jargon and metaphors. Prefer concrete wording when an abstract term obscures the mechanism or claim. Preserve established terminology, technical distinctions, and metaphors that help this audience. For example, "API surface" can be precise in an engineering document; it needs explanation only when the audience needs it.
Plain speech
- Specificity. Where the reader needs an explanation, name the behaviour or consequence using supported details. Keep evocative language when it serves the genre, and replace interchangeable filler with something particular to the subject.
- Shorten or split dense sentences. If the reader has to backtrack to parse a sentence, break it in two or drop clauses. One idea per sentence.
- Active voice. Prefer it. Catch "is/are/was/were + past participle" and name the actor: "queries are validated" becomes "the compiler validates queries", "the file is parsed by the loader" becomes "the loader parses the file". Passive is fine only when the actor is unknown or genuinely doesn't matter.
- Adverbs. Trim empty intensifiers or choose a more precise verb. Use a measurement when the source provides one, and retain modifiers that convey a real distinction.
- Prefer the plain word. "utilize" becomes "use", "leverage" becomes "use", "facilitate" becomes "help", "numerous" becomes "many", "in the event that" becomes "if". The fancier synonym is rarely clearer.