← ClaudeAtlas

human-article-writinglisted

Write, rewrite, or edit articles, LinkedIn posts, blog posts, essays, newsletters, and other long-form prose so the result reads as high-quality, natural human writing with none of the stylistic patterns typical of AI-generated text. Use this skill whenever the user asks for an article, post, essay, opinion piece, or long-form draft, whenever they ask to "humanize", "rewrite", "polish", or "fix the tone" of existing text, and whenever they mention AI-sounding writing, detection, or wanting text that reads like a person wrote it — even if they don't say "article" explicitly.
itzTiru/claude-code-skills-fable5 · ★ 0 · AI & Automation · score 58
Install: claude install-skill itzTiru/claude-code-skills-fable5
# Human-quality article writing This skill produces long-form prose that reads like it was written by a skilled, opinionated human, and edits existing drafts to the same standard. It encodes a large catalog of known AI-writing patterns (vocabulary, syntax, structure, formatting, and content habits) as hard constraints, plus the positive habits of strong human writers. The goal is not disguise for its own sake. Text that avoids these patterns is genuinely better writing: more specific, less padded, more honest about uncertainty, and more pleasant to read. Treat every rule here as a craft rule first. ## Workflow Follow these steps in order for both new drafts and rewrites. **1. Read the full pattern catalog.** Before writing a single sentence, read `references/banned-patterns.md`. It is the authoritative list of what must never appear in output. Do not rely on memory of it; the details matter (specific words, specific constructions, specific formatting habits). **2. Establish grounding.** Collect the real facts, sources, and claims the piece will rest on. Rules: - Never invent sources, quotes, statistics, links, or publication dates. If a link is provided by the user or found via search, use it verbatim; never construct a plausible-looking URL. - Never invent first-person experience ("I have seen this in production", "teams I talk to"). If a personal anecdote would strengthen the piece, insert a clearly marked placeholder like `[YOUR EXAMPLE: a time a deploy broke because