Skip to content
cccskills
FreePublished on GitHub

humanizer

Remove AI-isms and artificial language patterns from text. Makes documentation, comments, commit messages, and prose sound more natural and human. Based on Wikipedia's "Signs of AI writing" patterns.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

humanizer skill

Polish text by removing detectable AI-generated writing patterns. Ideal for finalizing documentation, commit messages, comments, and any prose before merging.

When to use

  • After @docs generates feature documentation
  • Before committing code (check commit messages and comments)
  • Polishing README updates, CHANGELOG entries, or runbooks
  • Making AI-assisted prose sound more natural
  • Manual voice calibration for brand consistency

How to invoke

/humanizer

[paste your text here]

Or ask directly in chat:

Please humanize this text: [your text]

Voice calibration (optional)

Provide a sample of your own writing for the skill to match your style:

/humanizer

Here's a sample of my writing for voice matching:
[paste 2-3 paragraphs of your own writing]

Now humanize this text:
[paste AI text to humanize]

What it detects

The skill checks for 29 AI-writing patterns, including:

  • Significance inflation — "marking a pivotal moment in the evolution of..." → "was established in 1989"
  • Notability name-dropping — Lists of citations → specific examples with context
  • Superficial -ing phrases — "symbolizing, reflecting, showcasing" → active explanations
  • Promotional language — Corporate jargon → straightforward description
  • Overuse of 'indeed' — Filler words → tighter prose
  • Transition abuse — Excessive "Furthermore, In conclusion..." → natural flow
  • Hedging redundancy — "arguably, in some sense, it could be argued..." → clarity
  • Rare word stacking — Thesaurus abuse → common vocabulary
  • False expert mode — Generic expertise → grounded examples
  • Generalist fluff — "many fields, various domains..." → specific scope

Integration with MAPLE

  • Auto-call after Phase 7 (DOCUMENT) if humanize: true in feature story frontmatter
  • Manual: invoke at any phase before merge
  • Works across all harnesses (Claude Code, OpenCode, Cursor, Copilot CLI)

Output

Returns a humanized version of your text with:

  1. First pass: Remove identified AI patterns
  2. Final audit: "Obviously AI generated?" check
  3. Second rewrite: Catch lingering AI-isms

Further reading

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Run WCAG 2.2 Level AA accessibility audits against generated UI. Use when a story has ui:true or when asked to audit accessibility.

The English summary is being prepared. Showing the original description.

kinncj/Heimdall70Updated Sep 2, 2026

Generate a complete component file tree wired to design tokens with tests and Gherkin spec. Use when scaffolding a new UI component.

The English summary is being prepared. Showing the original description.

kinncj/Heimdall70Updated Sep 2, 2026

Extract Gherkin scenarios from story markdown files into runnable .feature files and generate step definition stubs. Use when syncing stories to test suites.

The English summary is being prepared. Showing the original description.

kinncj/Heimdall70Updated Sep 2, 2026

Read and write design tokens in W3C DTCG format (tokens.json) and emit CSS, Tailwind, and Mantine outputs. Use when modifying or generating design tokens.

The English summary is being prepared. Showing the original description.

kinncj/Heimdall70Updated Sep 2, 2026

Apply Docker and Docker Compose best practices for containerising services. Use when writing or reviewing Dockerfiles and compose configs.

The English summary is being prepared. Showing the original description.

kinncj/Heimdall70Updated Sep 2, 2026

Identify and annotate cloud cost implications of architectural decisions. Use when reviewing infrastructure changes or designing new services.

The English summary is being prepared. Showing the original description.

kinncj/Heimdall70Updated Sep 2, 2026

See all skills by kinncj

Report a problem with this skill