davepoon/slopmop
plugins/slopmop/skills/slopmop/SKILL.md
Trigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to `sm swab`, `sm scour`, `sm buff`, `sm sail`, `sm refit`, or `sm doctor` so remediation follows the established rails. Also trigger when filing issues about slop-mop friction — use `sm barnacle file` / `/slopmop:sm-barnacle`, never `gh issue create`.
$ install --global
skillsauthnpx skillsauth add davepoon/buildwithclaude slopmopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 18, 2026, 2:32 AM49.5s1 file scanned
SKILL.md
- name:
- slopmop
- description:
- >-
- `sm barnacle file` / `/slopmop:
- sm-barnacle`, never `gh issue create`.
Slop-mop skill
Filing slop-mop friction? Use
/slopmop:sm-barnacleorsm barnacle file— nevergh issue createdirectly. The barnacle CLI auto-applies the correct labels and targets the right repo regardless of where you are.
Slop-mop (sm) has two primary modes: refit (one-time onboarding) and maintenance (steady-state development). Refit remediates all existing slop and installs permanent guards; the swab/scour/buff loop then keeps the repo clean as you work.
When to use
- Default action: Run
sm sailwhen you're not sure what's next — it reads workflow state and does the right thing. - Refit (step 0): Run
sm refit --startto generate a remediation plan, thensm refit --iterateuntil complete, thensm refit --finishto enter maintenance. - During implementation: Run
sm swabafter every meaningful code change. Keep running until clean. - Before PR: Run
sm scourfor a comprehensive sweep. - After CI/review: Run
sm buff <PR_NUMBER>to convert feedback into next steps.
The maintenance loop
Fastest path: sm sail → fix what it finds → sm sail → repeat until PR lands
Manual path: write code → sm swab → fix → repeat → sm scour → sm buff <PR#>
sm sail automates verb selection. Use individual verbs (sm swab -g <gate>, sm buff resolve, etc.) for surgical work.
Refit (before entering the loop)
Refit is not part of the maintenance loop. It is step 0 — how you earn the right to enter the loop.
sm refit --start → fix one gate → sm refit --iterate → ... → sm refit --finish
Prerequisite
The sm CLI must be installed in the user's environment. If invocation fails with "command not found", suggest:
pipx install slopmop[all]
Then re-run the command.
Safety
- Never bypass or silence a failing check — that's how repo rot compounds.
- If a gate seems wrong, tune it or file a bug. Don't disable it as a workaround.
- Report friction (invalid guidance, broken state, blocked rails) via
/slopmop:sm-barnaclerather than working around it.
Reference
Full project docs: https://github.com/ScienceIsNeato/slop-mop Workflow state machine: https://github.com/ScienceIsNeato/slop-mop/blob/main/DOCS/WORKFLOW.md Gate reasoning: https://github.com/ScienceIsNeato/slop-mop/blob/main/DOCS/GATE_REASONING.md
Related Skills
davepoon/drill-status
development
VerifiedTrustedCommunity
Show drill-me learning progress — topics studied, cards due for review, weakest concepts, and what to study next. Use when the user asks what's due, how their learning is going, or for their drill-me status.
3,050SKILL.mdUpdated Jun 13, 2026
davepoon/drill-me
development
VerifiedTrustedCommunity
Teach the user a topic as an adaptive tutor — retrieval practice, spaced repetition with decay, and persistent memory in ~/.drill-me/. Use when the user wants to learn or be drilled on something, says "drill me on X", "teach me X", or wants to study a topic, a codebase, or a document.
3,050SKILL.mdUpdated Jun 13, 2026
davepoon/tracedocs
development
VerifiedTrustedCommunity
Turn any codebase into evidence-grounded Markdown docs plus a machine-readable index.json. Every claim cites its source; never invents deployment steps.
3,044SKILL.mdUpdated Jun 11, 2026
davepoon/whats-next
tools
VerifiedTrustedCommunity
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.
3,021SKILL.mdUpdated Jun 5, 2026