declauding

Solid

Load at the start of any task whose deliverable is prose another person will read — a PR description, commit message, README, doc, postmortem, blog post, issue or review comment, report, release note or essay — before drafting it, whether the result is pushed, posted, published or saved to a file, without being asked. Draft, then run this pass on the draft before handing it over. Also use when someone says "de-claude", "de-slop", "humanize this", "this reads like AI", "make it sound human", or asks for a voice, tone or register edit. Rewrites the constructions that mark prose as model-written (staged reveals, verdict headers, aphoristic closers, "it's not X, it's Y", em-dash drama, forced triads, flat-certainty adverbs) into plain technical prose and checks the rewrite kept every claim. Not for fiction, poetry, code, or quoted text; for a full adversarial review of a deliverable use challenging.

Data & Documents 150 stars 6 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
73
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Declauding Turn LLM-shaped prose into prose a human technical writer would have written. Two output modes: - **clean** (default) — the rewritten text, nothing else. - **annotated** — a single-file HTML artifact: rewritten text, every changed passage marked, each with the original, the tic name, and why it goes. A toggle hides the marks so the result can be read straight through. Three ways it gets called, which change what you deliver: - **Pasted text** (default) — the user gives text in the conversation. Return the rewrite, plus a short list of what changed if the edit was substantial. - **File** — the user points at a path. Rewrite the file in place and report a summary in the conversation rather than pasting the whole result back. Edit prose only: leave code blocks, frontmatter, data, link targets and quoted specimens alone. - **Embedded** — another skill or agent is calling this as one step of a larger job (a PR description, a commit message, a doc). Return the final text and nothing else. No preamble, no summary, no tic list. ## Do not invent specifics The rewrite must not contain a fact, name, number, date, quote or citation that is not in the source. This is the failure mode the skill invites rather than prevents: the fix for a vague sentence is a specific one, and the specific has to come from the source or from the author. *Experts believe it plays a crucial role* becomes *the sources here do not say who studies it*, or gets cut. It does not b...

Details

Author
oaustegard
Repository
oaustegard/claude-skills
Created
11 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

declawed

De-slop pass for any text: mechanically scans for the statistical tells of AI writing (the "not X but Y" reflex, puffery, uniform cadence, …) and rewrites by meaning into the target register, tweet to academic paper. Use when the user says "declawed"/"deslop", asks to remove AI tells / humanize text / make it not sound like AI, names a specific tell to strip, or before publishing any agent-drafted prose.

5 Updated 1 weeks ago
kevinlin
Code & Development Listed

unclaude

Rewrite text into plain English before it leaves this session — a Jira or Linear comment, a GitHub or GitLab issue, a PR description or review, a commit message, a Slack or Telegram message, an email, a doc. Use when the user says /unclaude, or asks to post, comment, file, send, summarise or write something up "with /unclaude" or "in plain English". Manual invocation only.

0 Updated 3 weeks ago
sed1108
Data & Documents Featured

clean-user-facing-text

Audit and finalize authorized natural-language text meant for readers: strip suspicious invisible Unicode, then rewrite prose while keeping facts, meaning, and the writer's voice. Use when the user asks to clean, humanize, polish, or finalize articles, manuscripts, reports, documentation, emails, product copy, UI text, Markdown, or HTML prose, or when a project rule explicitly requires this workflow. Don't use for code-only tasks or undisclosed authorship evasion; leave code, commands, identifiers, paths, APIs, formulas, citations, required disclosures, and verbatim quotations unchanged.

841 Updated 3 weeks ago
ShadowAqueduct