Skip to content
SkillCheatSheet Sign in

antislop

An AI agent skill from miqdadbadjuber/anti-slop, scored 72 out of 100 by code.

72/ 100B

Code score by group

  • Spec18/20
  • Description7/20
  • Procedure15/15
  • Done criteria15/15
  • Resources2/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Description (13), the group that checks whether the description says what the skill does and when to use it.

What the author says it does

Anti Slop: Rules for AI Coding Agents. The core filter. Load always to stop generic AI slop.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
miqdadbadjuber/anti-slop
Folder
skills/antislop
License
MIT
GitHub stars
9,004
SKILL.md lines
701
Other files
1

Add antislop to your agent

npx skills add miqdadbadjuber/anti-slop --skill antislop

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

Labelled for

More skills from miqdadbadjuber/anti-slop

  1. antislop-layoutmobile

    Mobile layout skill for antislop. Use for layouts that reflow across screen sizes, phone to desktop: grids, overflow, tap targets. Load with the core.

    75B
  2. antislop-copywriting

    Copy and text skill for antislop. Use when writing or editing prose: headlines, tone, CTAs, and anti-AI-writing patterns. Load with the core.

    74B
  3. antislop-ui

    UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion, and page performance. Load with the core.

    74B
  4. antislop-human

    Human and accessibility skill for antislop. Contrast, keyboard, focus, states, and interaction affordances for real people. Includes the contrast checker.

    72B
  5. antislop-code

    Code comment hygiene for AI coding agents: remove generic AI-slop comments, keep the valuable ones, never touch the code.

    64C

All skills in miqdadbadjuber/anti-slop

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.