How do I install the Slop Scan skill?

Run npx skillmds@latest add tomevault-io/slop-scan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Slop Scan safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Slop Scan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Slop Scan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Slop Scan?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Slop Scan by tomevault-io — Agent Skill

Name: Slop Scan
Author: tomevault-io

Slop Scan

Run code quality analysis using the Slop Bot service. Analyzes the codebase for code smells, complexity issues, and improvement opportunities. Use when user says "slop scan", "code quality scan", or "scan code quality". Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Slop Scan - Code Quality Analysis

Runs Slop Bot analysis on the codebase and reports findings. Use before slop_fix to identify fixable issues.

Inputs

Input	Type	Default	Purpose
`codebase_path`	string	""	Path to analyze (default: current workspace)
`max_parallel`	int	3	Maximum concurrent analysis loops

Workflow

1. Determine Workspace Path

Use codebase_path if provided, else current workspace root (e.g. /home/daoneill/src/redhat-ai-workflow)

2. Run Slop Analysis

From workspace root, run:

python -m services.slop --max-parallel 3 --codebase <path>

Timeout: 30 minutes
On success: show stdout. On failure: show stderr. On timeout: report "Analysis timed out"

3. Get Statistics

If ~/.config/aa-workflow/slop.db exists, query:
- SELECT 'Total findings: ' || COUNT(*) FROM findings WHERE status = 'open';
- SELECT severity, COUNT(*) FROM findings WHERE status = 'open' GROUP BY severity;
- SELECT loop, COUNT(*) FROM findings WHERE status = 'open' GROUP BY loop;
Use sqlite_query (aa_sqlite) or sqlite3 CLI if no MCP tool loaded
If DB missing: report "No Slop database found. Run analysis first."

4. Log Session

memory_session_log("Slop scan completed", "Analyzed <workspace_path>")

5. Output Format

## Slop Bot Analysis Complete

### Analysis Result
<analysis_result>

### Statistics
<stats_output>

---
View findings in VSCode or query the database at `~/.config/aa-workflow/slop.db`

Key Details

Chains to: slop_fix - fix issues found by scan
Provides context for: review_local_changes, create_mr
Slop service must be available: services.slop module

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: slop-scandescription: Run code quality analysis using the Slop Bot service. Analyzes the codebase for code smells, complexity issues, and improvement opportunities. Use when user says "slop scan", "code quality scan", or "scan code quality". Use when this capability is needed.---# Slop Scan - Code Quality AnalysisRuns Slop Bot analysis on the codebase and reports findings. Use before `slop_fix` to identify fixable issues.## Inputs| Input | Type | Default | Purpose ||-------|------|---------|---------|| `codebase_path` | string | "" | Path to analyze (default: current workspace) || `max_parallel` | int | 3 | Maximum concurrent analysis loops |## Workflow### 1. Determine Workspace Path- Use `codebase_path` if provided, else current workspace root (e.g. `/home/daoneill/src/redhat-ai-workflow`)### 2. Run Slop Analysis- From workspace root, run: ```bash python -m services.slop --max-parallel 3 --codebase <path> ```- Timeout: 30 minutes- On success: show stdout. On failure: show stderr. On timeout: report "Analysis timed out"### 3. Get Statistics- If `~/.config/aa-workflow/slop.db` exists, query: - `SELECT 'Total findings: ' || COUNT(*) FROM findings WHERE status = 'open';` - `SELECT severity, COUNT(*) FROM findings WHERE status = 'open' GROUP BY severity;` - `SELECT loop, COUNT(*) FROM findings WHERE status = 'open' GROUP BY loop;`- Use `sqlite_query` (aa_sqlite) or `sqlite3` CLI if no MCP tool loaded- If DB missing: report "No Slop database found. Run analysis first."### 4. Log Session- `memory_session_log("Slop scan completed", "Analyzed <workspace_path>")`### 5. Output Format```markdown## Slop Bot Analysis Complete### Analysis Result<analysis_result>### Statistics<stats_output>---View findings in VSCode or query the database at `~/.config/aa-workflow/slop.db````## Key Details- **Chains to:** `slop_fix` - fix issues found by scan- **Provides context for:** `review_local_changes`, `create_mr`- Slop service must be available: `services.slop` module---> Converted and distributed by [TomeVault](https://tomevault.io/claim/dmzoneill) — claim your Tome and manage your conversions.

Frequently asked questions