anti-vibe-writing

Solid

Use when the user wants to humanize, de-AI, polish, or warm up an AI-generated document, in English or Chinese. Good for social posts (X/Weibo/Jike/RedNote), Reddit and forum comments, blogs, podcast show notes, README cleanup, product docs, landing page copy, proposals, founder notes, and technical memos. Removes templated phrasing, consultant-speak, vague abstraction, emoji or icon headings, markdown templates, overly balanced tone, and the typographic tells that flag generated text (em-dashes `—`/`——`, smart quotes, the `…` character) while preserving meaning. Supports optional voice modes: human-texture (light irregularities) and learning mode (match a specific host's style from samples).

Data & Documents 101 stars 9 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
67
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Anti-Vibe Writing You are an editorial finishing skill for AI-drafted writing, in English or Chinese. Use this after the substance is already there. The point is not to make the prose prettier. The point is to keep the meaning and remove the habits that make generated writing feel assembled: template language, vague abstraction, safe hedging, consultant tone, and default markdown scaffolding. The skill works best as a final pass after drafting with tools like Claude Code, Codex, or any large-model assistant. It handles English and Chinese as two distinct dialects of AI-smell, not one. ## Core Philosophy - Preserve the writer's meaning. Improve delivery, not substance. - Human writing chooses what matters. AI writing often hedges, formats, and explains by habit. - Warmth comes from specificity, rhythm, and honest emphasis, not emoji, icons, or cheerful filler. - Chinese AI-smell and English AI-smell are different problems. Apply the matching reference. - Several narrow editing passes work better than one vague rewrite. - Clean is not the goal. Sounding like the person who meant it is the goal. ## Best Uses - The draft is correct but flat, generic, or obviously AI-written. - The document has too many headings, bullets, or numbered lists. - The copy sounds cautious, polished, and empty at the same time. - The writing leans on business-speak instead of saying what is true. - The reader needs prose that sounds deliberate rather than generated. - A user wants future writin...

Details

Author
weijt606
Repository
weijt606/anti-vibe-writing
Created
3 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

write

Rewrites and polishes prose in Chinese or English, removes AI-like wording, and reviews product localization copy while preserving intent for drafts, docs, release notes, launch copy, and social posts. Use when users ask in any language to draft, rewrite, proofread, localize, polish release notes, remove AI-like wording, or prepare launch and social copy. Not for code comments, commit messages, or inline docs.

6,649 Updated 2 days ago
tw93
AI & Automation Listed

humanizer

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Detects and fixes AI patterns including inflated symbolism, promotional language, vague attributions, em dash overuse, rule of three, AI vocabulary, sycophantic tone, and generic conclusions. Use after copywriting, social-writer, cold-email, or email-sequence to polish output.

1 Updated yesterday
Layneformalized225
AI & Automation Listed

humanizer

Remove signs of AI-generated writing from prose that carries a personal voice, tuned for Claude output. Use when the user asks to humanize, de-AI, clean up, or improve the tone of blog posts, essays, opinion pieces, launch announcements, newsletters, emails, or long-form articles that read like an LLM wrote them. Also use to judge whether a given text was AI-generated. Triggers on AI patterns like markdown overuse, AI vocabulary, sycophantic openers, post action summaries, standalone caveat lines, unsolicited safety disclaimers, vague attributions, significance inflation, em dash overuse, or manufactured drama. Not for prose that lives in a repository or on a forge: commits, PRs, reviews, issues, READMEs, docs, changelogs, code comments, error messages.

0 Updated 5 days ago
svyatov