Agent skill

Kill AI Slop

Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

Apache-2.0Auto-check passedFrontend & Design

Install Kill AI Slop

skills CLI

$ npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install yetone/kill-ai-slop kill-ai-slop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/yetone/kill-ai-slop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill .claude/skills/kill-ai-slop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "kill-ai-slop" agent skill from https://github.com/yetone/kill-ai-slop/tree/main/skill into .claude/skills/kill-ai-slop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kill-ai-slop", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/yetone/kill-ai-slop/tree/main/skill

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install yetone/kill-ai-slop kill-ai-slop --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yetone/kill-ai-slop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill .agents/skills/kill-ai-slop && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "kill-ai-slop" agent skill from https://github.com/yetone/kill-ai-slop/tree/main/skill into .agents/skills/kill-ai-slop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kill-ai-slop", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install yetone/kill-ai-slop kill-ai-slop --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yetone/kill-ai-slop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill .cursor/skills/kill-ai-slop && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "kill-ai-slop" agent skill from https://github.com/yetone/kill-ai-slop/tree/main/skill into .cursor/skills/kill-ai-slop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kill-ai-slop", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/yetone/kill-ai-slop.git --path skill

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install yetone/kill-ai-slop kill-ai-slop --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yetone/kill-ai-slop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill .gemini/skills/kill-ai-slop && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "kill-ai-slop" agent skill from https://github.com/yetone/kill-ai-slop/tree/main/skill into .gemini/skills/kill-ai-slop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kill-ai-slop", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install yetone/kill-ai-slop kill-ai-slop

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/yetone/kill-ai-slop.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill .github/skills/kill-ai-slop && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "kill-ai-slop" agent skill from https://github.com/yetone/kill-ai-slop/tree/main/skill into .github/skills/kill-ai-slop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kill-ai-slop", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install yetone/kill-ai-slop kill-ai-slop --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yetone/kill-ai-slop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill .opencode/skills/kill-ai-slop && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "kill-ai-slop" agent skill from https://github.com/yetone/kill-ai-slop/tree/main/skill into .opencode/skills/kill-ai-slop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kill-ai-slop", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: kill-ai-slop
GitHub stars: 1.3k
Token cost: ~1.4k tokens
SKILL.md length: 607 words
Files: 8 (incl. scripts, references)
Skills in repo: 1
Repo updated: Sep 15, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

Works in 5 steps: Scope → Scan → Triage → …
The user asks to kill AI slop
SKILL.md covers Workflow, Guardrails and References
Runs JavaScript scripts from its folder; calls node and git

What it does

Kill AI Slop is an agent skill from yetone/kill-ai-slop. Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project. Use when the user asks to "kill AI slop", "de-slop", "remove the AI look", "make this not look AI-generated", or clean up a landing page / UI / docs that feels templated. Detects and fixes the catalogue of tells: indigo→violet gradients, gradient-clip headlines, the default semantic palette, one-hue status boxes, atmospheric gradients, serif-italic emphasis, highlighted keywords, AI copywriting…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `README.md`, `references/detection.md` and `references/fixes.md`).

It sits in Frontend & Design, covering CSS and styling, Icons and illustration and Landing pages. It works with Astro, React, Svelte and Vue.js. The repository describes itself as: A field guide to the visual & copy tics of AI-generated products — and an Agent Skill that scans your project and strips them out. https://killaislop.com. The licence is Apache-2.0.

When your agent uses it

The user asks to kill AI slop
Remove the AI look
Make this not look AI-generated
Clean up a landing page / UI / docs that feels templated

Example prompts

“kill AI slop”
“de-slop”
“remove the AI look”
“/kill-ai-slop”

Requirements

Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Scope
Scan
Triage
Report
Fix

What it can do on your machine

Read from SKILL.md and the folder at commit f6e2ae3. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
- node
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kill AI Slop loads about 1.4k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 258 tokens; SKILL.md has 607 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~258
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~15k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from yetone/kill-ai-slop at commit f6e2ae3, republished under its Apache-2.0 licence (© yetone). 607 words, ~1,408 tokens.

Download SKILL.mdSave it as .claude/skills/kill-ai-slop/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.

name: kill-ai-slop
description: Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project. Use when the user asks to "kill AI slop", "de-slop", "remove the AI look", "make this not look AI-generated", or clean up a landing page / UI / docs that feels templated. Detects and fixes the catalogue of tells: indigo→violet gradients, gradient-clip headlines, the default semantic palette, one-hue status boxes, atmospheric gradients, serif-italic emphasis, highlighted keywords, AI copywriting voice ("not just X — it's Y"), emoji everywhere, glowing status dots, wobbling spinners, colored-left-border callouts, pastel icon tiles, glassmorphism, over-rounding, oversized shadows, borders that die at corners, badge & pill spam, AI-drawn SVG icons, kickers over every heading, flat type hierarchies, invented stat rows, 01/02/03 section markers, cards nested in cards, the default Inter/Space Grotesk look, and more. Works on HTML/CSS, React/Vue/Svelte/Astro, Tailwind, PHP, and Markdown copy.

Kill AI Slop

AI slop is ugly in a specific way: it piles on every possible style and detail without settling on a focus. A gradient, a glow, a mascot, emoji, a wall of glowing cards, every default switched on at once, until every product looks like the same garish template. It reads as "designed" in a thumbnail and falls apart the moment anyone looks. Your job is to strip it back to something a person would actually choose.

The principles, held on every fix you make:

Decide before you decorate. Every visual choice must be explainable.
One accent, one voice.
Hierarchy from scale and space. Coloring words or swapping fonts is a shortcut.
Subtract first. The first move toward not-ugly is removing things.
Specific beats punchy in copy.
Decoration must mean something — icons, badges, callouts are signals.

Workflow

Follow these steps in order. Do not mass-edit before the user has seen the report.

1. Scope

Confirm what to scan. Default to the app/site source (skip node_modules, dist, build, .git, vendor, lockfiles, minified files). Ask if the project mixes several apps.

2. Scan

Run the bundled scanner, which greps the codebase for the code-level signals of each tell and prints grouped file:line hits:

node scripts/scan.mjs <root>          # human-readable report
node scripts/scan.mjs <root> --json   # machine-readable, for triage

It is pure Node (no dependencies) and never edits files. Use its output as a starting map, not gospel — confirm each hit by reading the code.

To narrow a scan: --only=01,06 / --skip=19 filter by tell id, and --exclude=legacy drops paths (substring match on the project-relative path). --rules=extra.mjs loads additional project- or language-specific tells (scripts/rules.ru.mjs is a shipped Russian-copy example and the template for your own). Hits the user has confirmed as intentional can be pinned in source with deslop-ignore, deslop-ignore-next-line 06, or deslop-ignore-file comments — prefer the id-scoped forms so new tells still surface.

3. Triage

For every hit, open the file and decide slop vs. intentional. This is the step that separates this skill from a lint rule. A gradient, a serif, or an emoji can be a real, defended choice. Keep anything the user clearly chose (brand tokens, a logo, a deliberate illustration). Flag only defaults.

Read references/taxonomy.md for what each tell is and why it reads as machine-made, and references/detection.md for the exact patterns and their common false positives.

Show full SKILL.md (227 more words)Show less

4. Report

Before changing anything, give the user a grouped summary: each tell, the file:line hits you confirmed, one sentence on why, and the proposed fix. Mirror the format:

slop  src/Hero.tsx:12   indigo→violet gradient        → one solid accent
slop  src/Hero.tsx:31   gradient-clip headline        → solid ink, scale up
slop  src/Note.tsx:8    border-l-4 callout ×3         → 1 aside, rest is body
slop  copy.md:1         "not just X — it's Y"         → say the specific thing
→ 4 groups, 11 hits.

Then ask which groups to apply, or whether to proceed on all.

5. Fix

Apply the minimal change that removes the tell while preserving intent and function. Use references/fixes.md for the before→after pattern per tell.

Prefer editing shared tokens/components over touching every call site.
Never invent new brand colors; if a palette must change, propose neutrals + the project's existing accent and let the user confirm.
Keep copy meaning; make it specific, don't just delete it.
Re-run the scanner after fixing to confirm the count dropped, and note any hits you intentionally left (with the reason).

Guardrails

Respect authorship. Treat unfamiliar files and deliberate flourishes as someone's choice. When unsure whether something is slop, ask — don't strip it.
Small, reviewable diffs. Never reformat unrelated code. Never run git add -A; stage explicit files only, and leave others' work-in-progress alone.
No new dependencies to do this work.
Verify visually when possible. If a dev server exists, look at the before and after; a passing scan is not the same as a better page.

References

references/taxonomy.md — the 35 tells: what each is, why it's slop, the fix.
references/detection.md — concrete ripgrep/regex patterns + false positives.
references/fixes.md — before→after remediation patterns.
scripts/scan.mjs — the dependency-free scanner.

Files

SKILL.md and 7 other files (scripts, references) in skill of yetone/kill-ai-slop.

SKILL.md
README.md
references/detection.md
references/fixes.md
references/taxonomy.md
scripts/rules.ru.mjs
scripts/scan.mjs
scripts/scan.test.mjs

Open the folder on GitHubat commit f6e2ae3

Compare with similar skills

Kill AI Slop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kill AI Slop compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Kill AI Slop this skillyetone/kill-ai-slop	1.3k	—	~1.4k	Automated safety check: Pass	Apache-2.0	24 days ago
GlideSrivarsanK/Glide	125	—	~1.7k	Automated safety check: Pass	Apache-2.0	9 days ago
Design StyleCastor6/tactus	376	1 repos	~2.1k	Automated safety check: Pass	Apache-2.0	5 mo ago
Atlaspacifio/ui	154	—	~2.5k	Automated safety check: Pass	MIT	5 mo ago
Bryl Minimal Designbryllim/bryl-minimal-design	115	—	~2.9k	Automated safety check: Pass	MIT	3 mo ago
UI UX Pro Maxshobcoder/shob	576	—	~3.7k	Automated safety check: Pass	MIT	21 days ago

Similar skills

Glide
SrivarsanK/Glide
Authoritative guide and toolset for AI agents to operate, configure, and visually design applications using Glide (@srivarsank/glide).
125 GitHub stars~1.7k tokensUpdated 9 days ago
Frontend & DesignAuto-check passed
Design Style
Castor6/tactus
A skill your agent uses whenever the user asks to build, create, design, develop, improve, or style any frontend interface or visual element.
376 GitHub starsUsed in 1 repo~2.1k tokens
Frontend & DesignAuto-check passed
Atlas
pacifio/ui
Atlas — a design language and UI guide system for agent interfaces.
154 GitHub stars~2.5k tokensUpdated 5 mo ago
Frontend & DesignAuto-check passed
Bryl Minimal Design
bryllim/bryl-minimal-design
Apply the bryl-minimal design language — a monochrome, typography-driven minimal aesthetic with halftone dot textures, pixel-font display headings, tiny uppercase monospace labels, soft large-radius…
115 GitHub stars~2.9k tokensUpdated 3 mo ago
Frontend & DesignAuto-check passed
UI UX Pro Max
shobcoder/shob
UI/UX design intelligence expert for web and mobile applications.
576 GitHub stars~3.7k tokensUpdated 21 days ago
Frontend & DesignAuto-check passed
Glide Component Segregator
SrivarsanK/Glide
Component segregation guide for Glide (@srivarsank/glide). An agent skill from SrivarsanK/Glide.
125 GitHub stars~1.2k tokensUpdated 9 days ago
Frontend & DesignAuto-check passed

Works with

Questions about Kill AI Slop

What does Kill AI Slop do?

Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project. Kill AI Slop is an agent skill from yetone/kill-ai-slop. Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

When should I use Kill AI Slop?

Kill AI Slop fits situations like: the user asks to kill AI slop; remove the AI look; make this not look AI-generated; clean up a landing page / UI / docs that feels templated.

How do I install Kill AI Slop in Claude Code?

Run `npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a claude-code`. Or copy the skill folder (skill in yetone/kill-ai-slop) into .claude/skills/kill-ai-slop in your project. Claude Code loads it when a task matches its description.

How do I install Kill AI Slop in Codex?

Run `npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a codex`. Or copy the skill folder (skill in yetone/kill-ai-slop) into .agents/skills/kill-ai-slop in your project. Codex loads it when a task matches its description.

Can I use Kill AI Slop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yetone/kill-ai-slop --skill kill-ai-slop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kill-ai-slop, .gemini/skills/kill-ai-slop, .github/skills/kill-ai-slop and .opencode/skills/kill-ai-slop in your project.

What does Kill AI Slop need to run?

Going by SKILL.md and its folder, Kill AI Slop needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and git). Our summary lists: Node.js.

Does Kill AI Slop access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Kill AI Slop safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Kill AI Slop use?

Kill AI Slop is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kill AI Slop use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.

What are the alternatives to Kill AI Slop?

Skills that share tags, products or a category with Kill AI Slop: Glide (SrivarsanK/Glide, 125 stars), Design Style (Castor6/tactus, 376 stars), Atlas (pacifio/ui, 154 stars) and Bryl Minimal Design (bryllim/bryl-minimal-design, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kill AI Slop?

yetone (a GitHub user) maintains it in yetone/kill-ai-slop, which has 1,324 GitHub stars. The repository was last updated on September 15, 2026.

Source: yetone/kill-ai-slop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Kill AI Slop

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Kill AI Slop

Workflow

1. Scope

2. Scan

3. Triage

4. Report

5. Fix

Guardrails

References

Files

Compare with similar skills

Similar skills

Glide

Design Style

Atlas

Bryl Minimal Design

UI UX Pro Max

Glide Component Segregator

Related

Questions about Kill AI Slop