Index of every page on this site: llms.txt

Anti-slop writing

You want prose that reads like a person wrote it, with the AI tells gone.

Compare Humanizer, Stop Slop, and No AI Slop

Teach your agent skilld

npx skilld install skilld --global
Adds the skilld Skill to your agent for every project.

154 skills

Anti-slop writing skills devs talked about this week

Ranked by how many separate devs talked about each one.

14–21 Nov 2026

  1. /pptx

    Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

    @ArchimedesLoreI can't f*cking believe this: the exact skills Claude uses to build every PowerPoint, Word doc, Excel sheet and PDF have been sitting on GitHub for a year. 197K stars. most Fable 5.2 users have never opened the repo. anthropic shipped Agent Skills in October 2025 and put the source in a public repo. not a summary, not a doc page. the actual folders the product runs on. then Fable 5.2 dropped on November 9 and everyone went back to typing "make me a deck" into a chat window…

    198k GitHub stars
  2. /docx

    Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

    @ArchimedesLoreI can't f*cking believe this: the exact skills Claude uses to build every PowerPoint, Word doc, Excel sheet and PDF have been sitting on GitHub for a year. 197K stars. most Fable 5.2 users have never opened the repo. anthropic shipped Agent Skills in October 2025 and put the source in a public repo. not a summary, not a doc page. the actual folders the product runs on. then Fable 5.2 dropped on November 9 and everyone went back to typing "make me a deck" into a chat window…

    198k GitHub stars
  1. /extract-design-md

    Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework. Analyzes component files, stylesheets, Tailwind configs, theme definitions, and design tokens to produce a rich, Stitch-compatible design system document. Use this skill whenever the user wants to reverse-engineer a design system from an existing codebase, audit the visual language of a project, extract design tokens from source files, or understand the styling patterns in a frontend repo — even if they just say "what does this app look like?" or "pull out the design from this code."

    @DYoung_AIExtract the design system first. Applying it to screens is a second official skill. Google Labs published Stitch Design Skills, a library of agent skills for Google Stitch, compatible with Codex, Antigravity, Gemini CLI, Claude Code, Cursor, and a manual OpenCode path. Official README: these skills need the Stitch MCP server configured and running in the agent environment. Installing the skill files is not enough if that server is missing. Official MCP setup…

    11k GitHub stars

Hand-picked anti-slop writing skills

Ten skills that remove AI writing tells while keeping the author's voice, one per author, ordered after the anti-slop rank @juampitech shared on X in August 2026.

  1. /stop-slop

    Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

    19k GitHub stars
  2. /no-ai-slop

    Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.

    14k GitHub stars
  3. /unslop

    Cut AI tells from any writing.

    18k GitHub stars
  4. /anti-slop

    Edit formulaic or AI-sounding prose while preserving the author's voice. Use for an anti-slop pass, editorial review, or requests to make writing sound more human; ordinary drafting does not require this skill.

    226 GitHub stars
  5. /soundshuman

    Remove signs of AI-generated writing from prose, and keep it out of a repo. Use when drafting, editing, or reviewing text to make it sound natural and human, or when auditing a whole docs folder for AI slop. Detects 41 patterns across content, language, style, communication, filler, and rhetoric, including: significance inflation, promotional language, -ing tails, vague attributions, AI vocabulary, copula avoidance, negative parallelisms, false agency, em dash overuse, chatbot artifacts, hedging stacks, staccato drama, and aphorism formulas. Includes voice calibration, a no-fabrication rule, statistical tells, and a draft -> audit -> final rewrite loop.

    307 GitHub stars

More anti-slop writing skills, ranked by GitHub stars

  1. /edit-article

    Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

    329k GitHub stars
  2. /writing-beats

    Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

    329k GitHub stars
  3. /writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

    329k GitHub stars
  4. /cold-email

    Write B2B cold emails, subject lines, and follow-up sequences that read like a person wrote them. Use when the user wants a cold outreach email or a follow-up, or asks why an opener, a reason to reach out, or an email gets no replies.

    211k GitHub stars
  5. /humanizer

    Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler.

    211k GitHub stars
  1. /discernment-nudge

    After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

    198k GitHub stars
  2. /doc-coauthoring

    Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

    198k GitHub stars
  3. /template

    Replace with description of the skill and when Claude should use it.

    198k GitHub stars
  4. /output-skill

    Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

    119k GitHub stars
  5. /animation-vocabulary

    Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

    58k GitHub stars
  6. /technical-writer

    Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as agent-browser.dev and portless.sh. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.

    53k GitHub stars
  7. /skill-creator

    Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends an AI agent's capabilities with specialized knowledge, workflows, or tool integrations.

    52k GitHub stars
  8. Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

    43k GitHub stars
  9. /skill-creator

    Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

    41k GitHub stars
  10. /add-educational-comments

    Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

    41k GitHub stars

Other tracks