anti-ai-writing

Enforce human tone and ban AI-overused phrasing in generated prose.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill anti-ai-writing-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-ai-writing
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/anti-ai-writing
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill anti-ai-writing-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent generic, AI-overused prose by enforcing concrete, human-sounding writing and removing filler language so documents, emails, and reports read like they were written by a knowledgeable person.

Core Features & Use Cases

  • Banned-word enforcement: Hard bans on common AI filler words and a restricted list for sparse use to make writing specific and credible.
  • Structural and evidence checks: Sentence-, paragraph-, and document-level rules (lead with the point, max 3 sentences per paragraph, require numbers/citations for claims).
  • Voice calibration and integration: Loads department-specific voice and domain contexts to match tone and audience before generation.
  • Use Case: Edit a PR description to remove AI-phrasing, add measurable metrics, and adapt the tone to the engineering voice file.

Quick Start

Apply anti-ai-writing rules to this draft and return an edited version that replaces banned words, reduces adjective density, and adds concrete evidence or numbers for claims.

Frequently Asked Questions about anti-ai-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI filler words from generated prose and marketing copy?

To remove AI filler words from generated prose, apply banned-word enforcement checks that flag restricted vocabulary and reduce adjective density. This process forces the text to use specific, credible phrasing instead of generic filler.

What is the best way to enforce a human tone in AI-generated documentation?

Enforcing a human tone in AI-generated documentation requires loading department-specific voice context files before generation and applying structural rules like leading with the main point and limiting paragraphs to three sentences.

How do I validate that AI writing includes concrete evidence and citations?

Validate AI writing for concrete evidence by running evidence checks that require numbers or citations for any claims made in the document. This ensures outputs are backed by measurable metrics rather than vague statements.

Can I apply content editing rules to edit PR descriptions and commit messages?

Yes, you can apply content editing rules to edit PR descriptions and commit messages by checking opening statements, validating paragraph length, and adapting the text to match your engineering department's specific voice file.

Why does my AI content editing fail to match my team's style guide?

AI content editing fails to match a team's style guide when department-specific voice and domain context files are not loaded before text generation. Loading these context files ensures the output tone matches the intended audience.