New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Slop Detector

by flamehaven01 in flamehaven01/AI-SLOP-Detector

Structural review skill for AI-SLOP Detector. An agent skill from flamehaven01/AI-SLOP-Detector.

MITAuto-check passedDevelopment

Install Slop Detector

skills CLI
$ npx skills add flamehaven01/AI-SLOP-Detector --skill slop-detector -a claude-code

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

GitHub CLI
$ gh skill install flamehaven01/AI-SLOP-Detector slop-detector --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/flamehaven01/AI-SLOP-Detector.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-skills/slop-detector .claude/skills/slop-detector && 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/

Facts

Skill name
slop-detector
GitHub stars
101
Token cost
~1.3k tokens
SKILL.md length
440 words
Files
1
Repo updated
First seen
Licence
MIT

At a glance

Structural review skill for AI-SLOP Detector. An agent skill from flamehaven01/AI-SLOP-Detector.

  • Works in 5 steps: Run changed-code review first → Inspect only bounded evidence → Use cleanup families intentionally → …
  • Asked to review AI-assisted code
  • SKILL.md covers Install, Command Selection, Recommended Agent Loop and Programmatic Node Surface, plus 1 more section
  • Calls pip, npm and npx

What it does

Slop Detector is an agent skill from flamehaven01/AI-SLOP-Detector. Structural review skill for AI-SLOP Detector. Use when asked to review AI-assisted code, inspect changed-code risk, prioritize structural hotspots, plan cleanup, verify governance, or run MCP/JSON-first workflows. Prefer the canonical CLI surfaces: scan, review, pulse, sweep, explain, verify-governance, and mcp. Treat review/pulse/sweep as the primary agent-facing surfaces; use scan for full baseline analysis.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Model Context Protocol. The repository describes itself as: Stop shipping AI slop. Detects empty functions, fake documentation, and inflated comments in AI-generated code. Production-ready. The licence is MIT.

When your agent uses it

  • Asked to review AI-assisted code
  • Inspect changed-code risk
  • Prioritize structural hotspots
  • Verify governance

Example prompts

  • “/slop-detector”

Requirements

  • Python 3
  • Node.js

Workflow steps

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

  1. Run changed-code review first
  2. Inspect only bounded evidence
  3. Use cleanup families intentionally
  4. Re-run health after edits
  5. Escalate with evidence

What it can do on your machine

Read from SKILL.md and the folder at commit 0811aef. 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

    Shell commands in SKILL.md call:

    • pip
    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip, npm and npx, 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

Slop Detector loads about 1.3k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from flamehaven01/AI-SLOP-Detector at commit 0811aef, republished under its MIT licence (© flamehaven01). 440 words, ~1,288 tokens.

Download SKILL.mdSave it as .claude/skills/slop-detector/SKILL.md (or your agent's skills folder).
name
slop-detector
description
Structural review skill for AI-SLOP Detector. Use when asked to review AI-assisted code, inspect changed-code risk, prioritize structural hotspots, plan cleanup, verify governance, or run MCP/JSON-first workflows. Prefer the canonical CLI surfaces: scan, review, pulse, sweep, explain, verify-governance, and mcp. Treat review/pulse/sweep as the primary agent-facing surfaces; use scan for full baseline analysis.

AI-SLOP Detector Skill

Use AI-SLOP Detector as a structured review loop, not as a last-minute lint step.

The preferred flow is:

  1. generate or edit code
  2. run a structured review in JSON
  3. inspect evidence and action classes
  4. apply only bounded fixes
  5. re-run review / health / cleanup
  6. hand the result to a human with evidence

Install

Python core:

bash
pip install ai-slop-detector
pip install "ai-slop-detector[js]"   # optional JS/TS support
pip install "ai-slop-detector[go]"   # optional Go support

Optional Node-first wrapper:

bash
npm install --save-dev ai-slop-detector

Verify:

bash
slop-detector --version
npx ai-slop-detector --version

Command Selection

Use the smallest surface that matches the job.

scan
bash
slop-detector scan . --format json

Use when you need:

  • full single-file or project analysis
  • baseline structural metrics
  • complete pattern output

Before acting on a project scan, inspect:

  • finding_summary for total and severity counts
  • scan_coverage for analyzed, excluded, and unsupported files
  • ml_scoring for the optional ML capability state
review
bash
slop-detector review . --format json

Use when you need:

  • changed-code review
  • introduced vs inherited attribution
  • build/pass-fail guidance

Inspect first:

  • verdict
  • should_fail_build
  • attribution
  • targets
  • actions
  • findings
pulse
bash
slop-detector pulse . --format json

Use when you need:

  • health summary
  • hotspot prioritization
  • next repair order

Inspect first:

  • summary
  • targets
  • signals
sweep <family>
bash
slop-detector sweep dead-code . --format json
slop-detector sweep dupes . --format json
slop-detector sweep unused-deps . --format json
slop-detector sweep stale-suppressions . --format json
slop-detector sweep boundary-violations . --format json

Use when you need cleanup planning with:

  • issues
  • confidence
  • action_class
  • evidence
explain
bash
slop-detector explain empty_except --format json

Use when you need mitigation guidance for a pattern or finding.

verify-governance
bash
slop-detector verify-governance ./.cr-ep

Use when governance artifacts, not score output, are the enforcement boundary.

mcp
bash
slop-detector mcp

Use when the host tool already speaks MCP and wants the structured tool surface directly.

1. Run changed-code review first
bash
slop-detector review . --format json

If the task is PR-like or patch-like, this is the default entry point.

Show full SKILL.md (210 more words)Show less
2. Inspect only bounded evidence

Safe agent targets:

  • unused imports
  • obvious duplicate functions
  • placeholder branches
  • stale suppressions

Unsafe without human confirmation:

  • deleting needs_review cleanup findings automatically
  • changing architecture boundaries
  • removing high-churn files solely from cleanup heuristics
  • treating clean as proof that no findings exist or all files were analyzed
  • treating an unavailable ML capability as a passing ML signal

Use --include-tests only when test-file findings are in scope. It includes built-in test-file exclusions only; configured ignores and artifacts remain excluded.

3. Use cleanup families intentionally

If review points at a cleanup class, run the narrow family:

bash
slop-detector sweep dupes . --format json
slop-detector sweep dead-code . --format json
slop-detector sweep unused-deps . --format json

Do not treat confidence as permission. It is prioritization guidance.

4. Re-run health after edits
bash
slop-detector pulse . --format json

Confirm that the hotspot moved, the score improved, or the finding count dropped.

5. Escalate with evidence

Human handoff should include:

  • what changed
  • what command was run
  • what verdict / score / issue count changed
  • what remains unfixed
  • what the agent deliberately did not change

Programmatic Node Surface

ts
import {
  scanProject,
  reviewChanges,
  computeHealth,
  runCleanupFamily,
} from "ai-slop-detector";

Typed contracts:

ts
import type {
  ScanOutput,
  ReviewOutput,
  HealthOutput,
  CleanupOutput,
} from "ai-slop-detector/types";

Legacy Note

Older skill revisions used a /slop, /slop-file, /slop-gate, /slop-delta, and /slop-spar framing. Those names are historical. Prefer the canonical product surfaces:

  • scan
  • review
  • pulse
  • sweep
  • explain
  • verify-governance
  • mcp

If a host environment adds slash aliases, they should delegate to those canonical commands rather than documenting a separate behavior model.

© flamehaven01, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in claude-skills/slop-detector of flamehaven01/AI-SLOP-Detector.

Open the folder on GitHubat commit 0811aef

Compare with similar skills

Slop Detector 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.

Slop Detector compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slop Detector this skillflamehaven01/AI-SLOP-Detector101—~1.3kAutomated safety check: PassMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT
Analyze Logsactivepieces/activepieces25k1 repos~1.6kAutomated safety check: PassMIT
Rea Changelog Updatemorluto/rea80k—~1.9kAutomated safety check: PassMIT
ReleasePrefectHQ/fastmcp28k—~2.9kAutomated safety check: PassApache-2.0

Similar skills

  • Debugging Executions

    n8n-io/n8n

    Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Analyze Logs

    activepieces/activepieces

    Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.

    25k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Rea Changelog Update

    morluto/rea

    Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.

    80k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Claude Code Skill

    codeaashu/claude-code

    Development conventions and architecture guide for the Claude Code CLI repository.

    3.4k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

Works with

Categories

Questions about Slop Detector

What does Slop Detector do?

Structural review skill for AI-SLOP Detector. An agent skill from flamehaven01/AI-SLOP-Detector. Slop Detector is an agent skill from flamehaven01/AI-SLOP-Detector. Structural review skill for AI-SLOP Detector.

When should I use Slop Detector?

Slop Detector fits situations like: asked to review AI-assisted code; inspect changed-code risk; prioritize structural hotspots; verify governance.

How do I install Slop Detector in Claude Code?

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

How do I install Slop Detector in Codex?

Run `npx skills add flamehaven01/AI-SLOP-Detector --skill slop-detector -a codex`. Or copy the skill folder (claude-skills/slop-detector in flamehaven01/AI-SLOP-Detector) into .agents/skills/slop-detector in your project. Codex loads it when a task matches its description.

Can I use Slop Detector 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 flamehaven01/AI-SLOP-Detector --skill slop-detector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slop-detector, .gemini/skills/slop-detector, .github/skills/slop-detector and .opencode/skills/slop-detector in your project.

What does Slop Detector need to run?

Going by SKILL.md and its folder, Slop Detector needs the command-line tools its instructions call (pip, npm and npx). Our summary lists: Python 3; Node.js.

Does Slop Detector access the network?

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

Is Slop Detector 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. Review the folder before installing.

What licence does Slop Detector use?

Slop Detector is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Slop Detector use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Slop Detector?

Skills that share tags, products or a category with Slop Detector: Debugging Executions (n8n-io/n8n, 207k stars), ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars), Analyze Logs (activepieces/activepieces, 25k stars) and Rea Changelog Update (morluto/rea, 80k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slop Detector?

flamehaven01 (a GitHub user) maintains it in flamehaven01/AI-SLOP-Detector, which has 101 GitHub stars. The repository was last updated on October 10, 2026.

Source: flamehaven01/AI-SLOP-Detector on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.