Menu

Individual skill

humanize-content

0upvotes

Use this skill when marketing or sales copy reads as machine-written and needs to sound like a person wrote it: AI drafts of articles, web pages, case studies, emails, LinkedIn posts, meta descriptions and FAQ answers. Produces a rewrite that keeps the meaning and facts, removes six specific patterns that give AI copy away, and comes with a checker report. Fires on "humanize this", "this sounds like AI", "make it sound human", "remove the AI tells", "tidy the copy", "does this sound like AI", "edit this draft", "check this against our style", "this reads like a slogan stack".

skills/amith-tk/humanize-content/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use when a draft is correct but sounds produced rather than written. Produces a rewrite in plain, connected prose with claims first, evidence attached and a person doing the acting, plus a short list of what changed and what still needs a source.

**Load first:** the draft, where it will appear (page, email, post, article) and who reads it. Ask whether a brand voice guide or house style exists and follow it where it conflicts with the defaults in `references/house-style-options.md`. Confirm the few switches that vary by company: English variant, em dashes, banned vocabulary, and whether byline or headline wording is already agreed. The purpose is clarity and voice. It is not to defeat AI detectors, and it never changes who the author is.

## The play

1. **Diagnose.** Run `scripts/lint_style.py` on the draft when code execution is available (`references/using-the-checker.md`). Otherwise test the draft by hand against the six patterns below. Also read for sentences with no verb, which the checker only partly catches.
2. **Rewrite pattern by pattern.** Give every sentence a subject and a finite verb, keep every fact and number, and use the fixes in `references/retired-patterns.md`. Study `references/rewrite-bank.md` for before-and-after pairs.
3. **Re-check and read aloud.** Rerun the checker until no `RULE` hits remain, decide each `CHECK` hit, then read the draft once as speech. If it sounds like a stack of statements, join them into continuous prose.
4. **Report.** List the patterns removed, the sentences that changed meaning even slightly, and every figure that has no unit, source or date. Ask for those instead of inventing them.

For voice, sentence length and structure, read `references/voice-and-structure.md`.

## The six patterns to retire
Back to top