Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Coding
toilet-triage-ranger
Try itUse when a toilet runs constantly, refills by itself, phantom-flushes, or the flush is weak and you're staring into the tank wondering what to touch — symptom-based diagnosis tree (flapper vs fill-valve vs chain vs flange), exact water-waste math from your meter (a stuck flapper wastes 950-9500 L/day, doubling a household's water use), safe DIY-vs-shutoff decision, the 10-minute flapper replacement protocol, weak-flush causes ranked, and a shutoff-valve-stuck rescue path.
What it does
Overview A running toilet is the highest-ROI household repair most people postpone: a stuck-open flapper passes 200+ gallons a day silently — that's 2-4× a typical household's entire indoor use, flowing while you sleep. And the diagnosis is easier than people fear: the tank is just a container of c…
The skill document
Toilet Triage Ranger
Overview
A running toilet is the highest-ROI household repair most people postpone: a stuck-open flapper passes 200+ gallons a day silently — that's 2-4× a typical household's entire indoor use, flowing while you sleep. And the diagnosis is easier than people fear: the tank is just a container of clean water with three parts that fail in known ways.
This skill is the 2 AM tank-staring companion:
- diagnose — symptom → ranked causes → which part → test that confirms it (dye test, lift-the-float test, listening protocol).
- waste — waste math from your situation (drip/ trickle/ running): liters and money per day/month/year, with meter-verification steps.
- decide — DIY now / DIY this week / water-off + plumber, based on symptom class and your answers.
- fix — step protocols per part: flapper (10 min), fill valve (30 min), chain, flange bolts; tool list; what NOT to do.
- weak — weak/partial flush causes ranked (jet holes, water level, venting) with the trap-siphon explanation.
Pure stdlib, offline. Water is clean in the tank; the only real risks are over-tightening porcelain (crack = new toilet) and the stuck shutoff valve.
When to Use
- Toilet runs continuously, or refills itself every few minutes (phantom flush)
- Hissing/trickling sounds between flushes
- Weak or incomplete flush, water rising then settling without going down
- Post-repair verification (did the dye test clear?)
- "How much water is this actually wasting?" before deciding urgency
- Rental/landlord situations: document waste + urgency for the notice
Don't use for: sewage backup into the bowl (that's a main-line problem — plumber), tank or bowl cracks leaking water onto the floor (water supply off, replace toilet), or frozen/burst supply lines.
The Parts Map (60-second orientation)
[fill valve tower] [overflow tube]
| |
[float] ---+ | water line ↑
[flapper] ------hinge------ [flush valve seat]
| [chain] to flush handle
- Flapper (rubber seal at tank bottom): lifts to flush, drops to seal. Fails by warping/ mineral buildup → tank drains to bowl slowly → phantom refills. #1 failure by far.
- Fill valve (tower with float): refills tank after flush, stops at set height. Fails by not shutting off (overflow rattle) or filling slowly/noisily.
- Overflow tube: the tank's safety drain — water that rises too high dumps here into the bowl. Constant trickle into it = fill valve set too high or not shutting off.
- Chain: too tight = flapper can't seal; too loose = doesn't lift fully; kinked = double-flush or no flush.
How It Works — Numbered Steps
- Identify the symptom class, then run the tree:
python3 scripts/toilet_triage.py diagnose --symptom runs-constantly python3 scripts/toilet_triage.py diagnose --symptom phantom-refill - Quantify what the silence is costing:
python3 scripts/toilet_triage.py waste --rate running --price 4.1 --currency EUR python3 scripts/toilet_triage.py waste --rate trickle - Decide urgency and who fixes it:
python3 scripts/toilet_triage.py decide --symptom phantom-refill --renter - Execute the part-specific protocol:
python3 scripts/toilet_triage.py fix --part flapper python3 scripts/toilet_triage.py fix --part fill-valve - Verify with the dye test afterward (in
fixoutput), and for weak flush:weakcommand.
Waste Math (why this is urgent-adjacent)
Flow through a stuck flapper or running fill valve, by severity:
| Sound | Est. flow | Liters/day | @ $4/kl (EUR-ish) |
|---|---|---|---|
| intermittent trickle | 0.1 L/min | 144 | $0.58 |
| constant trickle | 0.4 L/min | 576 | $2.30 |
| quietly running | 1.5 L/min | 2,160 | $8.64 |
| loud running | 4 L/min | 5,760 | $23/day ≈ $700/yr |
A "quietly running" toilet doubles a 2-person household's typical 11,000-14,000 L/month. Phantom refills every 10 min ≈ a stuck flapper: 3-5 L per event, 6-9 kl/month. Meter check (below) turns estimates into facts in 30 minutes.
Common Pitfalls
- Over-tightening anything on porcelain. Snug + quarter-turn. Cracked tanks = new toilet. This is THE toilet-repair injury.
- Replacing the flapper without cleaning the seat. Mineral scale under the new flapper = same leak. Scour the seat with a scrubbie (not steel wool).
- Chain tension ignored. ½-1 cm of slack. Too tight: flapper drops but sits propped → constant run. Too loose: weak flush.
- Tank bricks / bricks in the tank "to save water." Disintegrate, jam the flapper. If saving water: dual-flush valve or fill-cycle diverter, not bricks.
- Bleach tablets in the tank. Chlorine attacks rubber — flappers and seals die in months. Bowl-side only, never tank.
- Forcing a stuck shutoff valve. Snap the handle → spray. Fix:
gentle work loose, or wrench on the SUPPLY after closing upstream;
see
decideoutput. - Mistaking bowl-refill vs tank-refill sounds. The refill after flush refills BOTH (the bowl via the overflow tube) — a few seconds is normal; minutes is not.
- Ignoring the wax ring when the floor is wet. Water AROUND the base isn't the tank's fault — rocking toilet compresses the ring: that's the flange-bolt protocol, and it's a different job.
Example
$ toilet_triage.py diagnose --symptom phantom-refill
SYMPTOM: tank refills by itself every few minutes
1. [70%] FLAPPER not sealing (warped/ mineral/ chain propping it)
CONFIRM: dye test — food coloring in tank, wait 15 min NO FLUSH;
color in bowl = flapper passing water.
FIX: fix --part flapper (10 min, $8)
2. [20%] Water level set ABOVE overflow tube top
CONFIRM: waterline at/over the tube? trickle into tube?
FIX: bend float arm down / adjust screw 1-2 cm
3. [10%] Fill valve not shutting off (internal diaphragm)
CONFIRM: lift float arm fully — does water STOP? if not → valve
FIX: fix --part fill-valve (30 min, $15)
$ toilet_triage.py waste --rate running
quietly running ≈ 1.5 L/min → 2,160 L/day → ~$8.6/day at $4/kl
≈ 65 kl/month — your whole household usually uses 11-14.
VERDICT: fix today; it's a $8 flapper, not a plumber call.
Verification Checklist
- Symptom class identified; dye test run where indicated
- Waste quantified (and meter-verified if bill-anxiety is high)
- Water off at supply before touching parts
- Correct part protocol followed; seat cleaned before new flapper
- Chain slack ½-1 cm; waterline 1-2 cm below overflow top
- Dye test RE-RUN after repair: clear bowl after 20 min
- Floor around base dry (else: wax ring job, different protocol)
Related skills
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Write, debug, and tune Playwright specs with locator strategy, trace diagnosis, and CI-aware timeouts.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
More from voronindenis5
Browse all skillsPryamoy Russkiy (Straight Russian) — AI assistant that tells it like it is. Direct answers, no fluff, occasional profanity. Specializes in honest analysis, t...
Prepare salary negotiations with a structured toolkit: market-rate anchoring math, walk-away floor calculation, total-compensation evaluation (equity, bonuses, benefits), negotiation scripts for offers, raises, and counter-offers, and BATNA analysis. Use when the user has a job offer, is preparing a raise conversation, wants to know if their pay is competitive, or needs scripts and a strategy for negotiating compensation.
Use when your calendar is eating your week and you want to know exactly where the time goes, when planning recurring meetings for a team, before proposing a new recurring meeting, when someone says 'we should sync weekly' and you want data, or when auditing which meetings to kill — imports ICS calendar files, measures meeting hours per week/person/meeting-series (including double-bookings and fragmentation), computes focus-time destruction from meeting placement, scores the true cost of each series (hours × attendees × frequency), flags specific meetings to kill/shorten/make-async using explicit rules, and simulates the recovered hours before anyone has to argue about it.
Use when you realize your photos/code/documents exist in exactly one place (or your 'backup' is a external drive in the same room as the computer) — audits your actual data-loss risk against the 3-2-1 rule (3 copies, 2 media, 1 offsite) asset by asset, scores blast radius (ransomware encrypts synced copies too), prices honest recovery (professional recovery lab $300-3000 vs $0), generates the minimum-cost redundancy plan for YOUR asset list, and produces a restore-test drill because an untested backup is a hope, not a backup.
Audit password vault exports (Bitwarden, 1Password, KeePass, Chrome, Firefox) for reuse, weakness, staleness, breach exposure, and 2FA gaps without ever storing or transmitting a plaintext password. Use when the user asks to audit passwords, check password strength/reuse, review vault health, or verify whether credentials appeared in breaches.
Use before any difficult phone call you're anxious about or that has stakes — calling customer service to dispute a fee, negotiating a bill, cold-calling a client, delivering bad news to a vendor, calling a landlord about repairs, insurance disputes, or handling collections calls — builds a branching call script from your situation (goal, leverage, fallback), generates objection→response trees for the specific counter-arguments you'll hear, produces a one-page printable cheat sheet, and includes a practice-drills mode that plays the other side and scores your responses.