← ClaudeAtlas

slop-offlisted

Process Slop Off browser reports via the slop-off MCP server and apply the edits to the current project's source. By default keeps looping over reports until the user stops. Use for "/slop-off", "apply my edit report", "wait for my browser edits", or after the user has made edits in the browser with the Slop Off extension.
wbso-ai/slop-off · ★ 2 · AI & Automation · score 66
Install: claude install-skill wbso-ai/slop-off
# Apply browser edits Process reports from the `slop-off` MCP server and apply them to the source. Everything happens in the MAIN thread — no subagents — so every report gives an immediate "✅ …" line and nothing sits between the queue and the work. ## Mode - **Default (loop)**: say once "Waiting for browser edits — say 'stop' when you're done", then loop: 1. Call `wait_for_report` with timeout_seconds: 60. Empty? Call it again, silently — empty waits are normal. After ~10 consecutive empty minutes, mention in one line that you're still waiting (don't ask, don't stop); repeat that at most once an hour. 2. Report received → apply it per "Apply edits" below, then follow "Per processed report". 3. Loop again immediately — more edits may already be queued. Stop only when the user says "stop" (or "done"). - Argument `once`: process exactly one report and stop. - Argument `latest`: call `get_latest_report` (don't wait), process, stop. - Argument `list`: call `list_reports`, show the queue, ask which one. - Argument `clear`: call `clear_reports` and report in a single line how many reports were cleared. Process nothing, then stop. ## Apply edits The report contains per-URL sections with Before/After HTML pairs and/or Element/Instruction pairs, each with a CSS selector as a hint. 1. For each edit find the source file that renders that page/HTML: search for distinctive text from the Before block (literal strings first, then fuzzy). The URL