Unslop
A maintained adaptation of Cursor's pstack unslop skill. Apply it automatically to human-facing
communication and prose where applicable, not as a universal rule for every file or response.
Scope
Apply this skill to agent replies, documentation, pull requests, issue text, user-facing copy, and
explanations.
Preserve meaning, factual support, technical precision, and the intended tone.
Do not apply it to code, identifiers, schemas, contracts, commands, logs, quoted text, machine-
readable output, fixed status or gate formats, byte-exact vendor snapshots, or neutral technical
records where stylistic variation would reduce clarity.
Process
- Read the surrounding text and identify the reader, purpose, and required facts.
- Remove filler, puffery, vague attribution, promotional language, chatbot phrases, and excessive
hedging. Prefer concrete claims and named sources.
- Replace inflated vocabulary, abstract metaphors, passive voice, synonym cycling, forced lists,
and dense sentences with plain, specific language.
- Use sentence-case headings and ordinary punctuation. Avoid decorative formatting, unnecessary
em dashes, and bold labels that merely repeat the sentence.
- Do not add opinions, first-person voice, deliberate imperfection, or personality to neutral
product, architectural, security, operational, or policy records.
- Check the result for unsupported claims, changed meaning, lost constraints, and remaining filler.
Explicit requirements, accessibility, security, contracts, and factual accuracy take precedence over
style. If a fixed format requires wording or punctuation, keep the format.
1---2name: unslop3description: Apply to human-facing communication and prose to remove AI writing tells while preserving meaning, evidence, and the intended tone.4---56# Unslop78A maintained adaptation of Cursor's pstack `unslop` skill. Apply it automatically to human-facing9communication and prose where applicable, not as a universal rule for every file or response.1011## Scope1213Apply this skill to agent replies, documentation, pull requests, issue text, user-facing copy, and14explanations.15Preserve meaning, factual support, technical precision, and the intended tone.1617Do not apply it to code, identifiers, schemas, contracts, commands, logs, quoted text, machine-18readable output, fixed status or gate formats, byte-exact vendor snapshots, or neutral technical19records where stylistic variation would reduce clarity.2021## Process22231. Read the surrounding text and identify the reader, purpose, and required facts.242. Remove filler, puffery, vague attribution, promotional language, chatbot phrases, and excessive25 hedging. Prefer concrete claims and named sources.263. Replace inflated vocabulary, abstract metaphors, passive voice, synonym cycling, forced lists,27 and dense sentences with plain, specific language.284. Use sentence-case headings and ordinary punctuation. Avoid decorative formatting, unnecessary29 em dashes, and bold labels that merely repeat the sentence.305. Do not add opinions, first-person voice, deliberate imperfection, or personality to neutral31 product, architectural, security, operational, or policy records.326. Check the result for unsupported claims, changed meaning, lost constraints, and remaining filler.3334Explicit requirements, accessibility, security, contracts, and factual accuracy take precedence over35style. If a fixed format requires wording or punctuation, keep the format.
enocgit