Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from bundle
Draft, rewrite, or edit prose so it is clear, concise, human, and free of common AI-writing mannerisms. Includes a strict ASD-STE100 mode on request.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
SKILL.md
1---2name: anti-slop3description: Draft, rewrite, or edit prose so it is clear, concise, human, and free of common AI-writing mannerisms. Use for explanations, guides, instructions, emails, personal messages, posts, documents, reviews, captions, and other requested writing. Also use when the user asks for anti-slop, humanize, humanizer, natural writing, their own voice, ASD-STE100, STE, Zinsser, or removal of AI-sounding language. Preserve the requested voice and language. Apply strict ASD-STE100 only when the user explicitly asks for STE or ASD-STE100.4metadata:5credits: >-6Pattern catalog adapted from stop-slop by Hardik Pandya7(https://github.com/hardikpandya/stop-slop, MIT) and Humanizer by Siqi Chen8(https://github.com/blader/humanizer, MIT), which draws on Wikipedia's9"Signs of AI writing" by WikiProject AI Cleanup. Strict mode approximates10ASD-STE100 Simplified Technical English (https://www.asd-ste100.org).11Prose principles follow William Zinsser, "On Writing Well".12Curated and extended by @Latand for Forgedemy. See LICENSE.md.13---1415# Anti-Slop Writing1617Write the text, not a preface about the text. Preserve the facts, intent, emotional temperature, language, and recognizable voice.1819## Choose the mode20211. **Functional prose:** For explanations, guides, emails, and documents, apply simplicity, brevity, clarity, and humanity. Use the useful parts of STE without making the prose mechanical.222. **Personal or emotional prose:** Keep it direct, slightly imperfect, and natural. Do not polish it into therapy language. Do not force full sentences when fragments match the speaker.233. **Posts in a known voice:** Match the user's real examples and current channel style. Do not substitute generic marketing copy.244. **Creative prose:** Preserve rhythm, imagery, ambiguity, and personality. Use only the anti-slop filter that does not flatten the work.255. **Strict STE:** Use only after an explicit request for `STE`, `ASD-STE100`, `/ste`, or “use the ste skill.” Read `references/ste-rules.md` and its linked references before drafting.2627When another selected skill controls a file format or domain workflow, let it control the workflow. Apply this skill to its prose.2829## Drafting rules3031- Start with the point. Delete warm-up phrases and meta-commentary.32- Use the shortest wording that keeps the meaning and voice.33- Prefer concrete nouns and active verbs.34- Keep one stable name for each object or idea.35- Use short sentences when they improve clarity. Do not create a row of slogan fragments.36- Keep necessary nuance. Do not turn uncertainty into certainty.37- Use the user's language naturally. Avoid unnecessary English terms in Ukrainian or Russian prose.38- Do not add conclusions, headings, lists, or calls to action unless they help the text.39- Do not manufacture symmetry. Lists can contain the number of items the subject needs.40- Do not over-correct the user's grammar, rhythm, profanity, or fragments when they carry voice.4142## Anti-slop pass4344Read `references/forbidden-patterns.md` before a substantial draft or rewrite. After drafting, scan once and remove each pattern that appears accidentally.4546Do not solve a forbidden pattern by replacing it with a more ornate version. State the point directly.4748## Source fidelity4950- Do not invent facts, feelings, motives, chronology, quotes, or personal reactions.51- Keep uncertainty and attribution from the source.52- When rewriting, change meaning only if the user asks for substantive editing.53- If the source contains a deliberate stylistic device, preserve it unless the user asks to remove it.5455## Final check5657Before the response, ask:58591. Does this sound like a person with a reason to write it?602. Did I preserve the user's voice instead of displaying my own polish?613. Can I delete a sentence without losing meaning or rhythm?624. Did any forbidden construction survive?635. Did strict STE leak into a text that needed warmth or personality?6465Return only the finished draft unless the user asks for notes or alternatives.6667## Credits and sources6869- The forbidden-pattern catalog adapts [stop-slop](https://github.com/hardikpandya/stop-slop) by [Hardik Pandya](https://hvpandya.com) (MIT) and [Humanizer](https://github.com/blader/humanizer) by Siqi Chen (MIT), which draws on Wikipedia's ["Signs of AI writing"](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing) maintained by WikiProject AI Cleanup.70- Strict STE mode is a working approximation of [ASD-STE100 Simplified Technical English](https://www.asd-ste100.org). The official specification and dictionary belong to ASD.71- The functional-prose principles of simplicity, brevity, clarity, and humanity come from William Zinsser, *On Writing Well*.72- Curated and extended by [@Latand](https://forgedemy.org/skills?seller=%40Latand) for Forgedemy. Third-party license notices: [LICENSE.md](LICENSE.md).73