Docs Deslop

Rewrite technical product documentation to strip AI slop and conform to the CTRT topic-type model (Concept, Task, Reference, Troubleshooting) plus Tutorial. Use whenever the user wants to deslop, tighten, edit, or rewrite technical docs — concept pages, task / how-to pages, reference material (API, CLI, config tables), troubleshooting pages, runbooks, tutorials, release notes, or product README sections. Trigger on phrases like \"deslop\", \"make this doc less AI-sounding\", \"edit this docs page\", \"tighten my draft\", or \"rewrite this in CTRT\", whether the user pastes prose or points at a file (.md, .mdx, .rst, .adoc, .txt, .docx). Scope is product/technical documentation only — do not use for marketing copy, blog posts, social posts, or general prose. Default behavior is to classify the input by topic type, then apply a heavy rewrite per the type-specific rules. Supports an optional passive mode (light-touch: word- and sentence-level fixes only, no restructuring — trigger on \"passive\", \"light-touch\", \"words only\", \"don't restructure\") and an optional verbose mode (change summary shows each edit as a before/after pair with the rule that triggered it — trigger on \"verbose\", \"explain each change\", \"show before/after\"); the two modes combine. Always return the rewritten text plus a short summary naming the topic type(s) and the changes made.

mkdir -p ~/.claude/skills/docs-deslop
curl -L https://claudskills.com/skills/docs-deslop/SKILL.md \
  -o ~/.claude/skills/docs-deslop/SKILL.md

@misc{docs-deslop-2026,
  author    = {seqeralabs},
  title     = {Docs Deslop [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/docs-deslop/}
}