Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Writing Humanize

ASecurity

Review and rewrite text to reduce AI detection signals and increase authenticity. Flags overrepresented AI vocabulary, structural signatures (uniform paragraph lengths, formulaic openers/closers, transition-word overuse), burstiness flatness, hedging, abstract nominalizations, and missing specificity. Produces flagged audit with line-level rewrites. Use on cover letters, personal statements, blog posts, essays, and documentation where the author's voice must read as genuinely human.

8 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsapidocumentation

Works with

api

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add tstapler/dotfiles --skill writing-humanize --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Writing Humanize?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Writing Humanize
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tstapler-writing-humanize/badge)](https://www.skillsdirectory.com/skills/tstapler-writing-humanize)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: writing-humanize
description: Review and rewrite text to reduce AI detection signals and increase authenticity. Flags overrepresented AI vocabulary, structural signatures (uniform paragraph lengths, formulaic openers/closers, transition-word overuse), burstiness flatness, hedging, abstract nominalizations, and missing specificity. Produces flagged audit with line-level rewrites. Use on cover letters, personal statements, blog posts, essays, and documentation where the author's voice must read as genuinely human.
---

# Writing Humanize

Audit text for AI detection signals and rewrite to increase authenticity, sentence-rhythm variation, and authorial specificity.

## When to Use This Skill

- Cover letters, personal statements, graduate school essays
- Blog posts or articles where voice and credibility matter
- Documentation written with AI assistance that needs a human editorial pass
- Any text being submitted to a platform with AI detection screening

## The Two Metrics That Drive AI Detection

GPTZero and similar detectors use two core signals:

**Perplexity** — how unpredictable each word choice is. AI runs low (predictable, safe word choices). Human writing surprises.

**Burstiness** — how much sentence-length complexity varies. AI runs flat. Humans alternate: a short punch. Then a long, clause-heavy sentence that builds toward something.

Both must improve. Fixing vocabulary without fixing rhythm leaves the structural fingerprint intact.

## Audit Protocol

Run in sequence. Flag every instance with location and rewrite suggestion.

### Step 1 — Vocabulary Scan

Check for flagged terms from `references/word-lists.md`:
- **Tier 1** (50–269× overrepresented): delve, realm, nuanced, multifaceted, tapestry, robust, pivotal, seamless, leverage, harness, underscore, testament, cutting-edge, intricate
- **Tier 2** (transition overuse): moreover, furthermore, additionally, it is worth noting
- **Em dash overuse**: flag every em dash where a comma or period would be natural

For each hit: identify the sentence, explain why it signals AI, offer a concrete replacement.

### Step 2 — Structural Signature Scan

Check paragraph-level patterns:

| Signal | What to Look For | Fix |
|--------|-----------------|-----|
| Uniform length | Every paragraph 3–5 sentences, similar word counts | Break one short (1–2 sentences). Expand one long. |
| Wall of text | 4+ sentences / 100+ words delivered as one unbroken block with no internal line break — the default shape LLMs fall back to in chat, PR/issue comments, and DMs | Break at thought boundaries, one idea per line-group, the way a person actually types a reply. Treat as a **soft signal only** — an ordinary dense human paragraph can share this exact shape, so weight it alongside register and redundant-context tells below, not as a standalone detector. |
| Formulaic opener | "In today's rapidly evolving landscape..." or similar throat-clearing | Cut entirely or replace with a specific claim or scene |
| Formulaic closer | "In conclusion, it is clear that..." | End on a specific image, an open question, or a direct call |
| Transition-word boundary | moreover/furthermore starting 2+ consecutive paragraphs | Remove or replace with a direct pivot sentence |
| Participial opening overuse | 3+ sentences opening with a present participle ("Leveraging...", "Building on...") | Rewrite as declarative or imperative |

### Step 3 — Burstiness Check

Count sentence lengths (in words) across the full text. Calculate:
- Mean sentence length
- Longest sentence / shortest sentence ratio
- Run of 3+ consecutive sentences within 3 words of the mean (flat zone)

**Target**: ratio ≥ 3:1 (longest to shortest). Flat zones of 4+ sentences should be broken.

Report the distribution. Rewrite one flat zone as an example.

### Step 4 — Authenticity Scan

Check for tells that AI describes rather than experiences:

| Tell | Example | Fix |
|------|---------|-----|
| No anecdote / all abstract | "I have experience managing cross-functional teams" | Specific: who, when, what broke, what happened |
| Hedging density | might, could, arguably, it's important to note (>3 per 300 words) | Commit to the claim or cut it |
| Abstract nominalization | "implementation", "utilization", "optimization" hiding who did what | "We shipped", "Sarah rebuilt", "I cut latency by 40ms" |
| Positivity bias | No tension, no failure, no contradiction | Add one thing that went wrong or one position held against consensus |
| Passive agency | "It was decided that..." / "Steps were taken to..." | Name the agent |

### Step 5 — Synthesis and Rewrite Offer

After flagging, offer three options:
1. **Audit only** — Return the flagged report, let the user rewrite
2. **Targeted rewrites** — Rewrite each flagged passage inline, preserving the user's intent
3. **Full humanized draft** — Rewrite the entire text applying all fixes; user reviews

Default to option 2 unless the user specifies otherwise.

## Output Format

```
HUMANIZE AUDIT: [document type] — [word count]

VOCABULARY FLAGS (N found)
[line/paragraph] "exact phrase" → TIER 1 hit: [word]
  Suggestion: [concrete replacement]

STRUCTURAL FLAGS (N found)
[signal type] — [location description]
  Fix: [specific instruction]

BURSTINESS REPORT
Mean sentence length: X words
Longest/Shortest ratio: X:1
Flat zones: [locations]
Example rewrite: [before] → [after]

AUTHENTICITY FLAGS (N found)
[tell type] — [exact phrase or passage]
  Fix: [specific instruction or rewrite]

SUMMARY
Risk level: LOW / MEDIUM / HIGH
Top 3 priority changes: [ordered list]
```

## Quality Standards

- Every flag must cite the exact text, not a paraphrase
- Every suggestion must be concrete — not "be more specific" but "add the year, the company name, or the metric"
- Never remove the author's argument, only the AI fingerprint
- Preserve register: if the source is casual, rewrites stay casual
- Do not introduce new claims the author didn't make

---

## Related Skills

| Skill | When to apply |
|-------|--------------|
| `knowledge-synthesis` | Polish Zettelkasten notes or wiki pages after synthesis |
| `knowledge-confluence-sync` | Publish humanized documentation to Confluence |
| `meta-prompt-engineering` | Improve prompts that generate the text being humanized |

## Reference Files

- `references/word-lists.md` — Full flagged vocabulary, tier rationale, and safe substitutions
- `references/research-notes.md` — Detection mechanism detail, burstiness math, source citations

Attribution

tstaplertstapler
View sourceMore from tstapler →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →