anti-vibe-writing
SolidUse 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).
Install
Quality Score: 89/100
Skill Content
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
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.
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.
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.