anti-patterns

Detect and fix writing, reasoning, and LLM output anti-patterns in text.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/varlabz/skills --skill anti-patterns-varlabz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-patterns
Source: https://github.com/varlabz/skills/tree/main/other/anti-patterns
Command: npx skills add https://github.com/varlabz/skills --skill anti-patterns-varlabz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated and human writing often contains hollow, evasive, or formulaic language—corporate jargon, hedging, vague quantifiers, logical fallacies, and AI clichés—that undermines credibility and clarity. This Skill provides a systematic checklist and reference tables to identify and fix these patterns. ## Core Features & Use Cases - Writing and documentation review: Eliminate robotic openings, buzzwords, hedging, fake statistics, and formatting problems using the writing-and-docs reference tables. - Reasoning validation: Catch logical fallacies like false dichotomy, straw man, and false balance before publishing arguments or recommendations. - LLM output auditing: Detect hallucination, sycophancy, API hallucination, overengineering, and prompt engineering mistakes in AI-generated content and code. - Use Case: Before sending a team announcement or publishing a blog post, run the quick self-check to strip phrases like "leverage," "game-changer," and "it is worth noting that," replacing vague claims with specific numbers and direct statements. ## Quick Start Review my draft text and remove all anti-patterns including jargon, hedging, vague quantifiers, and AI clichés, replacing them with direct specific language.

Frequently Asked Questions about anti-patterns

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

FAQPage Schema
How do I remove AI clichés from generated text?

Scan the text for phrases like "Let's dive in," "delve," "tapestry," "game-changer," and "In today's world," then replace them with direct statements of the actual content. The writing-and-docs reference lists each cliché with its concrete fix.

How to fix hedging and vague language in writing?

Replace qualifiers like "I think that," "it seems that," and "might possibly" with direct statements or explicit uncertainty. Swap vague quantifiers such as "many" or "significantly" for actual numbers, names, or cited sources.

What are common LLM coding anti-patterns to avoid?

Common LLM coding anti-patterns include API hallucination, missing imports, ignored error handling, overengineering, and assuming modern API versions. Fixes include checking official documentation, running the code, and requesting the simplest solution first.

Can this skill detect logical fallacies in arguments?

Yes, the reasoning reference covers fallacies including false dichotomy, straw man, circular reasoning, survivorship bias, and correlation versus causation. It also addresses false balance, where unequal evidence is presented as equally valid.

When should I not rely on LLM self-assessment for writing quality?

LLMs exhibit self-reinforcing errors and overconfidence, so they often fail to catch their own mistakes. Verify facts and citations independently, run generated code, and treat first outputs as drafts requiring iteration.