Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Design & media
water-shutoff-map
Try itUse before a plumbing emergency, when moving into a new home, before DIY repairs, when a pipe bursts or a toilet overflows, or when creating a household emergency reference sheet — walks you through locating every water shutoff in your home (main, fixture stops, water heater, irrigation), records what you find into a durable JSON registry with photos, generates a printable emergency card for the fridge, and gives the 3-step first response for floods, burst pipes, and overflowing fixtures.
What it does
A pipe bursts. Water is spreading across the floor. The main shutoff is *somewhere* — basement? Crawl space? By the street? The average person has never turned it and doesn't know where it is, and a homeowner wastes precious minutes searching while the damage grows. Burst-flex-line claims average $…
The skill document
Water Shutoff Map
Overview
A pipe bursts. Water is spreading across the floor. The main shutoff is somewhere — basement? Crawl space? By the street? The average person has never turned it and doesn't know where it is, and a homeowner wastes precious minutes searching while the damage grows. Burst-flex-line claims average $10,000+, and response time is the single biggest controllable factor: every minute of flow is roughly 2–5 gallons onto your floors.
This skill solves the "know before you need it" problem in two parts:
- A guided location procedure (
references/locating-shutoffs.md) — where shutoffs hide by home type (basement, slab, crawlspace, condo), how to identify each valve type, how to test it safely, and what to do if it's stuck (the #1 discovery people make the hard way). - A registry + emergency card generator (
scripts/shutoff_registry.py) — record every valve you find with location, type, tool needed, direction, test date. Validate the registry for completeness, print a fridge card with the 3-step first response, and export JSON so your household (and your agent) always knows where everything is.
When to Use
- Moving into any home — the very first weekend, before unpacking the kitchen
- Before DIY plumbing work — replacing a faucet, toilet flapper, dishwasher, water heater
- Leaving town / freezing weather — confirm the main works and know how to drain down
- Creating a household emergency reference for family members, babysitters, renters
- After the fact: a plumber showed you a valve — log it so it's never lost knowledge again
- Right now, during a leak: jump to Emergency First Response below
- Don't use for: gas shutoffs (different tool/procedure), electrical issues, or municipal supply problems outside your property line.
Emergency First Response (memorize this much)
- Kill the fixture if you can — angle stop under the toilet/sink (clockwise). Fixture stop handles the 80% case with zero tools.
- If you can't isolate it, kill the house — main shutoff clockwise. It's stiff: use a wrench if needed; never force half-way — full closed or leave it.
- Then damage control — power off the affected area if water is near outlets (breaker first), towels/shop-vac, move valuables, then call a plumber and your insurer (mitigation duty starts immediately).
Run python3 scripts/shutoff_registry.py drill for a 60-second quarterly rehearsal script.
Commands
# Start / edit the registry (interactive, or via flags in one shot)
python3 scripts/shutoff_registry.py add --id main --label "Main shutoff" \
--location "Basement, east wall behind furnace" --type gate \
--tool "12in crescent wrench" --direction clockwise --tested 2026-08-30 \
--notes "Stiff first 2 turns; exercise annually"
python3 scripts/shutoff_registry.py add --id water-heater --label "Water heater" \
--location "Garage, cold inlet above unit" --type ball --direction perpendicular \
--tested 2026-08-30
# Guided entry — prompts for the fields that matter
python3 scripts/shutoff_registry.py add --interactive
# See what you've recorded and what's missing
python3 scripts/shutoff_registry.py list
python3 scripts/shutoff_registry.py validate
# Printable fridge card with the 3-step response + your valve table
python3 scripts/shutoff_registry.py card > shutoff-card.txt
# Quarterly rehearsal script (the thing that makes this real)
python3 scripts/shutoff_registry.py drill
# Where things hide, by home type — the hunting guide
python3 scripts/shutoff_registry.py hunt --home basement
python3 scripts/shutoff_registry.py hunt --home slab
# Export for other tools / your agent
python3 scripts/shutoff_registry.py export --json
Registry lives at ~/.shutoff-registry.json by default (--file to override; keep a printed copy — emergencies take power and Wi-Fi with them).
Registry Fields
| Field | Why it matters |
|---|---|
id | short handle (main, toilet-1, water-heater) |
location | specific enough that a panicked person finds it: "under kitchen sink, left wall, behind cleaning bottles" |
type | gate / ball / angle-stop / straight-stop / meter-key / other — determines how it closes |
direction | clockwise / perpendicular (ball valves: handle across pipe = OFF) |
tool | none / flat screwdriver / crescent wrench / meter key — stored WHERE? |
tested | date you last exercised it — untested valves are seized valves |
photo | path/filename of the photo you took (photo > description) |
notes | quirks: "stiff", "access panel behind toilet", "shared with unit 4B" |
Valve Types at a Glance
| Type | Looks like | Closes by | Common failure |
|---|---|---|---|
| Ball | lever handle, 90° arc | quarter-turn: handle ⟂ pipe = OFF | rarely sticks; leaks at stem |
| Gate | round wheel like an outdoor faucet | many clockwise turns | seizes OPEN after years — the classic |
| Angle/straight stop | small oval/knurled handle under sinks & toilets | clockwise few turns | seizes, strips; replace with quarter-turn |
| Meter key valve | in concrete box at property/street edge | 5-sided key or meter wrench | needs the key — own one ($12) |
| Washing machine valves | behind washer, red/blue or single lever | clockwise / lever | aging flex lines burst — replace w/ braided + lever box |
Common Pitfalls
- Never testing the main until the emergency. Gate valves that sit open for a decade often won't close. Test at move-in, then exercise yearly (
drill). If it won't turn, a plumber can replace it for ~$150–400 — vastly cheaper than discovering it seized during a flood. - Confusing the house main with the irrigation/yard main. Closing the wrong one leaves the leak flowing. The registry records which is which.
- Forcing a stuck valve with a giant cheater bar. You can snap the stem and create the flood. Gentle penetrating oil, back-and-forth rocking, then call a plumber.
- Closing only the water heater's cold inlet for a whole-house leak (or vice versa). Fixture → appliance → main: isolate at the smallest valve that contains the leak.
- Not owning the tools your valves need. A meter key and a 12" adjustable wrench, stored where the card says, are part of the system.
- Relying on memory or a phone note. Emergencies happen to whoever is home — babysitter, guest, teen. The printed card in a known spot is the deliverable.
- Shutting off power AFTER wading into water. Breaker first, then wet-vac. GFCI outlets don't make water safe.
Verification Checklist
-
mainentry exists, with tool + direction, andtestedwithin 12 months - Every toilet and sink has an entry (angle stops) — or a note that it lacks one
- Water heater cold inlet entry exists (also your drain-down point)
- Photo filenames recorded (or photos taped inside a cabinet near the valve)
- Card printed and posted where household members already look (fridge)
- Meter key + wrench purchased and stored in the location the card names
-
drillrun once per quarter — 60 seconds, calendar it
Related skills
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
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.
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.