ds-unslop — Claude Code skill: editing prose and installing
This Claude Code skill rewrites prose and code comments in plain, specific English. It activates while editing replies, docs, READMEs, PR descriptions or commit messages, and on /ds-unslop.
MIT 547 installs ★ 320 updated 2026-10-28
npx skills add aicodeking/deepseek-stack --skill ds-unslop -a claude-codeWhat ds-unslop does
ds-unslop scans prose and code comments for inflated wording, vague metaphors, filler and passive constructions. It replaces them with direct language or removes them while keeping the original meaning and tone. The skill also flags forced groups of three and sentences that carry multiple ideas.
Its guidance covers replies, documentation, README files, PR descriptions and commit messages. For code comments, it keeps explanations of reasons the code itself cannot show, while removing narration of the next line and commented-out code. It recommends ending on a fact or a next step.
What it helps with
- remove inflated wording from a README
- rewrite a PR description in plain English
- trim comments that narrate the code
- edit a reply without changing its tone
Example prompts for the agent
- Rewrite this reply in plain, specific English and keep its tone.
- Remove vague phrasing from the README.
- Edit this PR description with
/ds-unslop.
How to install ds-unslop
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-unslop -a claude-code2Manually: put the files in place
~/.claude/skills/ds-unslop/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ds-unslop/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-unslop -a codex2Manually: put the files in place
.agents/skills/ds-unslop/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-unslop -a cursor2Manually: put the files in place
.cursor/skills/ds-unslop/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aicodeking/deepseek-stack skills/ds-unslop2Manually: put the files in place
.github/skills/ds-unslop/SKILL.md1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-unslop -a gemini-cli2Platform CLI
gemini skills install https://github.com/aicodeking/deepseek-stack --path skills/ds-unslopManually: put the files in place
.devin/skills/ds-unslop/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-unslop -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ds-unslop
How do I install ds-unslop in Claude Code?
Run npx skills add aicodeking/deepseek-stack --skill ds-unslop -a claude-code. The skill file is at ~/.claude/skills/ds-unslop/SKILL.md.
What does ds-unslop do?
It spots inflated or vague phrasing in prose and code comments, then rewrites or removes it while preserving the meaning and tone.
What kinds of text can ds-unslop edit?
It can revise replies, documentation, README files, PR descriptions, commit messages and code comments.
Source text
SKILL.md · MIT
--- name: ds-unslop description: "Remove AI writing tells from prose and code comments, then rewrite in plain, specific English. Use when writing or editing replies, docs, READMEs, PR descriptions, commit messages, or comments, or when the user types /ds-unslop." --- # Unslop Write clean as you draft. Then scan for these tells and rewrite. Keep the meaning and tone. ## Tells to remove Words - Inflated vocabulary: delve, crucial, pivotal, robust, seamless, leverage, utilize, showcase, underscore, tapestry, landscape, testament, vibrant, intricate. Use the plain word. - "Serves as", "stands as", "boasts". Say "is" or "has". - Abstract metaphor nouns: paradigm, north star, flywheel, substrate, bedrock. Name the concrete thing. - Adverbs that prop up weak verbs: "significantly improves". Give the number or a stronger verb. Sentences - "Not just X, but Y." State Y. - Forced groups of three. Use the real count. - Trailing "-ing" clauses: "ensuring reliability", "highlighting the need". Delete them or make a real claim. - Vague sources: "experts say", "many believe". Name the source or cut it. - Filler: "in order to", "it is important to note that", "due to the fact that". - Stacked hedges: "could potentially". Pick one qualifier or none. - Passive voice that hides the actor. Name who does it. - Feelings instead of mechanisms. If a sentence fits any project's docs unchanged, cut it. - Generic endings: "the future looks bright". End on a fact or the next step. - Over-compressed fragments, arrows, and symbol shorthand. Write full sentences with articles and verbs. Formatting - Em dashes. Use a period or a comma. - Colons used as mid-sentence connectors. Keep colons before lists. - Bold on every term, and "**Label:** label restated" bullets. - Title Case Headings. Use sentence case. - Decorative emojis and curly quotes. Chat habits - Openers and closers: "Great question", "Certainly", "I hope this helps", "Let me know if". - Agreement as a reflex. Give your actual judgment. Code comments - Comments that narrate the next line, banner comments, and commented-out code. Delete them. - Keep only comments that explain a reason the code cannot show. ## Rewrite procedure 1. Name the reader and what they need to do or know after reading. 2. Delete every sentence that does not serve that need. 3. Replace synonyms for one thing with a single name. Use the real file, flag, or command name. 4. Split sentences that carry two ideas. Vary sentence length. 5. Put conditions before instructions: "To reset the cache, run `make clean`." 6. Make every "it" and "this" point at one clear noun. 7. Replace vague claims with a number, a command, or a concrete example. 8. Reread once for the tells. A stiff sentence that follows every rule still needs a fix. ## Example Before: "This robust tool serves as a powerful way to seamlessly streamline your workflow, ensuring efficiency." After: "`sync.sh` copies changed files to the server in about two seconds."
© aicodeking · MIT · aicodeking/deepseek-stack