claude

ai-slop

Catch AI slop and apply writing conventions to any prose, whether Markdown drafts, documentation, or a blog post. Reviewing .tex source adds the empirical software engineering paper rules plus LaTeX checks (BibTeX, reference verification) automatically. The --scientific flag applies the paper rules to a non-LaTeX manuscript, --ste adds Simplified Technical English rules, and --economist adds core Economist style advice. Combines these with the tropes.fyi catalog of general AI writing patterns by Ossama Chaib. Glossary mode extracts definitions and checks terminology against a maintained GLOSSARY.md.

13 on GitHubby Software Engineering Group, Heidelberg Universityv2026-11_rev6CC-BY-4.0updated 8 days ago
/

Plugin ai-slop from marketplace ai-slop in se-uhd/ai-slop-skill. Commands read from the repo's manifest — 8 days ago.

What it installs

Skills (8)

  • glossary

    Extract or maintain GLOSSARY.md for a document and validate its terminology. Use when the user asks for a glossary, proposed definitions, a synonym audit, or a check that a paper or document uses one term for each concept. Flags competing names, conflicting meanings, undefined terms, and newly inven

  • ground

    Fill the grounding comments that review only flags as missing. For each `\cite{}` in a LaTeX paper that has no quote-backed grounding comment, whether no comment at all or a `TODO verify` stub left by revise mode or an earlier run, fetch the cited source, extract a verbatim quote that supports the c

  • init

    Set up the general writing rules and AI trope catalog for Claude Code, Codex, or pi across projects, or export them as one Markdown file for a system prompt. Use when the user wants the assistant's replies, edits, comments, and commit messages to follow these rules, or runs `/ai-slop:init`. Claude C

  • review-diff

    Review only the modified parts of a git-versioned document for AI slop and rule violations. Use when the user has uncommitted edits or a feature branch and wants to audit only what they changed, not the whole draft. Triggers on prompts such as "check my edits", "review what I just changed", "audit t

  • review-repo

    Review the natural-language text of a whole code repository for AI slop and rule violations, covering every Markdown and plain-text file plus the comments and doc-comments of its source and config files, not just one document or a diff. Use when the user wants to audit the prose spread across a code

  • review

    Review a document (LaTeX, PDF, or plain prose) for AI slop and rule violations. Use when the user asks to check, audit, or review a draft (a `.tex`, `.pdf`, or text file) or other prose for AI tropes and, for research papers, for statistical reporting, citations, BibTeX correctness, and hallucinated

  • revise

    Apply the findings of an `/ai-slop:review` report to the source, replacing each flagged quote with its suggested revision and inserting `% GROUNDING` TODO stubs for ungrounded citations. Use when the user has a generated `ai-slop-report.md` (or equivalent) and wants the suggestions applied to the pa

  • writing

    Generate a project-local WRITING.md file from the layered writing rules and add a reference to it in the AGENTS.md of the repository (creating AGENTS.md if it does not exist). Use when the user wants the writing conventions stored in their repo as an editable, project-local file. Triggers on prompts

View source on GitHub

Maintain ai-slop?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted