humanizelisted
Install: claude install-skill sgtlaugh/skills
# /humanize - strip the AI, keep the substance
Remove the patterns that mark text as AI-generated, then tighten for clarity.
## Usage
```
/humanize <text> # rewrite the pasted text
/humanize # rewrite your previous response
/humanize <file> # print a rewrite of the file (the file itself is not edited)
/humanize --concise ... # any of the above, and cut length roughly in half
```
If the argument is an existing path, Read it; otherwise treat it as text.
## Workflow
### Step 1: Scan for tells
Read the input. Notice: em dashes, rule-of-three lists, "it's not X, it's Y" framing, boldface on every key term, self-narration ("this highlights"), copula avoidance ("serves as" instead of "is").
If the user gave instructions about voice, audience, or format, honor those alongside the rules below.
**Required format beats these style rules.** On another skill's output (e.g. `/nicepr --humanize`), keep the structure it requires - headings and their fixed emoji (`### ✅ QA Steps`), `**Lead-in:**` bold labels with a colon, Title Case titles, `- [ ]` checkboxes, code blocks, permalinks - and rewrite only the prose inside it. In PR text, nicepr's format requires bold lead-ins with a colon and Title Case PR titles; stripping those from a PR is WRONG. Outside PRs the banned list's bold and casing rules apply as written.
**Text headed for GitHub** (a review comment, PR reply or status note): also follow `references/github-voice.md`, and when `~/.config/