agents/skills/humanize-ai-text/SKILL.md
Humanize AI-generated text to bypass detection. This humanizer rewrites ChatGPT, Claude, and GPT content to sound natural and pass AI detectors like GPTZero, Turnitin, and Originality.ai. Based on Wikipedia's comprehensive "Signs of AI Writing" guide. Makes robotic AI writing undetectable and human-like.
npx skillsauth add carterdea/dots humanize-ai-textInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive CLI for detecting and transforming AI-generated text to bypass detectors. Based on Wikipedia's Signs of AI Writing.
# Detect AI patterns
python scripts/detect.py text.txt
# Transform to human-like
python scripts/transform.py text.txt -o clean.txt
# Compare before/after
python scripts/compare.py text.txt -o clean.txt
The analyzer checks for 16 pattern categories from Wikipedia's guide:
| Category | Examples |
|----------|----------|
| Citation Bugs | oaicite, turn0search, contentReference |
| Knowledge Cutoff | "as of my last training", "based on available information" |
| Chatbot Artifacts | "I hope this helps", "Great question!", "As an AI" |
| Category | Examples | |----------|----------| | AI Vocabulary | delve, tapestry, landscape, pivotal, underscore, foster | | Significance Inflation | "serves as a testament", "pivotal moment", "indelible mark" | | Promotional Language | vibrant, groundbreaking, nestled, breathtaking | | Copula Avoidance | "serves as" instead of "is", "boasts" instead of "has" |
| Category | Examples | |----------|----------| | Superficial -ing | "highlighting the importance", "fostering collaboration" | | Filler Phrases | "in order to", "due to the fact that", "Additionally," | | Vague Attributions | "experts believe", "industry reports suggest" | | Challenges Formula | "Despite these challenges", "Future outlook" |
| Category | Examples | |----------|----------| | Curly Quotes | "" instead of "" (ChatGPT signature) | | Em Dash Overuse | Excessive use of — for emphasis | | Negative Parallelisms | "Not only... but also", "It's not just... it's" | | Rule of Three | Forced triplets like "innovation, inspiration, and insight" |
python scripts/detect.py essay.txt
python scripts/detect.py essay.txt -j # JSON output
python scripts/detect.py essay.txt -s # score only
echo "text" | python scripts/detect.py
Output:
python scripts/transform.py essay.txt
python scripts/transform.py essay.txt -o output.txt
python scripts/transform.py essay.txt -a # aggressive
python scripts/transform.py essay.txt -q # quiet
Auto-fixes:
Aggressive (-a):
python scripts/compare.py essay.txt
python scripts/compare.py essay.txt -a -o clean.txt
Shows side-by-side detection scores before and after transformation
Scan for detection risk:
python scripts/detect.py document.txt
Transform with comparison:
python scripts/compare.py document.txt -o document_v2.txt
Verify improvement:
python scripts/detect.py document_v2.txt -s
Manual review for AI vocabulary and promotional language (requires judgment)
| Rating | Criteria | |--------|----------| | Very High | Citation bugs, knowledge cutoff, or chatbot artifacts present | | High | >30 issues OR >5% issue density | | Medium | >15 issues OR >2% issue density | | Low | <15 issues AND <2% density |
Edit scripts/patterns.json to add/modify:
ai_vocabulary — words to flagsignificance_inflation — puffery phrasespromotional_language — marketing speakcopula_avoidance — phrase → replacementfiller_replacements — phrase → simpler formchatbot_artifacts — phrases triggering sentence removal# Scan all files
for f in *.txt; do
echo "=== $f ==="
python scripts/detect.py "$f" -s
done
# Transform all markdown
for f in *.md; do
python scripts/transform.py "$f" -a -o "${f%.md}_clean.md" -q
done
Based on Wikipedia's Signs of AI Writing, maintained by WikiProject AI Cleanup. Patterns documented from thousands of AI-generated text examples.
Key insight: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."
development
Add net-new product, workflow, platform, or developer-experience features as small vertical slices. Use this skill whenever the user asks to build a new feature, add a new page/route/API/workflow/job/eval/operator path, enrich an existing feature with a new user-visible capability, or plan feature architecture before coding. This skill maps the files to change or create, defines the authoritative contract, specifies tests, and gives a QA plan before treating the feature as done.
development
Verify a developer's finished Trello ticket on a non-Shopify web app and render a verdict. Dogfood the posted preview (desktop + mobile) against the card's acceptance criteria, then PASS it (approve the PR, move to Ready for Release) or FAIL it (request changes, attach repro, reassign the dev, move to Development). Read-only: never implements, commits, or opens a PR. Use when asked to 'QA this card', 'test before release', or 'sign off on this ticket'. Shopify themes use shopify-trello-qa; building a ticket uses trello-delivery.
development
Verify a developer's finished Shopify theme ticket and render a verdict. Dogfood the posted preview theme and Customizer (desktop + mobile) against the card's acceptance criteria and Figma, then PASS it (approve the PR, move to Ready for Release) or FAIL it (request changes, attach repro, reassign the dev, move to Development). Read-only: never implements, commits, deploys, or opens a PR. Use when asked to 'QA this Shopify card', 'verify the Ready for Testing card', or 'sign off on this theme ticket'. Non-Shopify apps use trello-qa; building a ticket uses shopify-trello-delivery.
development
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.