Coding

pantry-moth-eliminator

Try it

Use when you see small moths in the kitchen, webbing in flour or rice, or larvae climbing walls/ceiling — Indian meal moth infestation. Generates a staged elimination protocol (find-pull-freeze-clean-trap) with exact timelines, an item-by-item disposition engine (freeze/toss/heat), pheromone-trap placement math, cabinet crack-cleaning procedure, and a re-infestation watch with expected moth-free dates.

What it does

The Indian meal moth (*Plodia interpunctella*) is the moth most kitchens eventually meet: it hitches in via birdseed, bulk grains, dried fruit, pet food, or grocery packaging gaps. One fertilized female lays ~400 eggs; in a warm kitchen the cycle (egg→larva→pupate→adult) runs **4–8 weeks**, so "jus…

The skill document

Pantry Moth Eliminator

Overview

The Indian meal moth (Plodia interpunctella) is the moth most kitchens eventually meet: it hitches in via birdseed, bulk grains, dried fruit, pet food, or grocery packaging gaps. One fertilized female lays ~400 eggs; in a warm kitchen the cycle (egg→larva→pupate→adult) runs 4–8 weeks, so "just throwing out the flour" fails — larvae are already pupating in the ceiling corner, under shelf liners, and inside the seams of sealed-looking boxes.

This skill generates a staged protocol calibrated to infestation level:

  1. Level triage — mild (moths seen, no webbing) / moderate (webbing, larvae on walls) / severe (recurring catch, multiple cabinets).
  2. Disposition engine — for every category of dry food: freeze-kill (−18°C/0°F for ≥4 days), heat-kill (140°F/60°C for 30 min oven), or toss — including the non-obvious calls (spices, tea, chocolate, pet food, unopened boxes with larvae-sized gaps).
  3. Timeline — day 0 pull, freeze windows, deep-clean cracks (where pupae hide), day 7/14/30 trap checks with pass/fail thresholds.
  4. Trap math — where pheromone traps go, how many, and how to read them (traps are monitors, not control).
  5. Re-infestation defense — incoming-goods quarantine, storage hardening, and expected moth-free date math from biology.

When to Use

  • Moths fluttering in the kitchen or near dry goods
  • Webbing / clumping / larvae in flour, rice, oats, nuts, cereal, pet food
  • Larvae climbing walls or ceiling corners (they seek dark pupation cracks)
  • After bringing in bulk grains, birdseed, or dried fruit and wanting to prevent an infestation

Don't use for: clothes moths (different species, different protocol — look for holes in wool, cases not webbing), weevils in pasta (disposition similar but no trapping), or commercial kitchens (call a licensed pest operator).

Quick Start

python3 scripts/moths.py protocol --level moderate
python3 scripts/moths.py disposition --item "brown rice, opened"
python3 scripts/moths.py disposition --item "spices"
python3 scripts/moths.py traps --cabinets 4
python3 scripts/moths.py timeline --start 2026-10-04 --level moderate
python3 scripts/moths.py watch --start 2026-10-04 --catch-day7 3 --catch-day14 0

Stdlib-only, no network.

The Biology You're Fighting (why partial attempts fail)

StageDuration (warm kitchen)WhereKillable by
Egg2–14 dayson/near food surfacetoss/freezing
Larva2–6 weeks (the webbing stage)INSIDE food, then wanderingfreeze/heat/toss
Pupa1–2 weekscracks, seams, ceiling corners — away from foodvacuum + wipe only
Adult1–2 weeksflying; ♂ follows pheromonetraps MONITOR only

Key facts the protocol encodes:

  • Larvae chew into packaging that looks sealed: folded carton seams, plastic bags. Cardboard is not a barrier.
  • Pupae hide away from food — cleaning only the pantry shelves misses the ceiling corner, under-cabinet lip, and shelf-support holes. This is the #1 reason infestations "come back" (they never left).
  • Freeze at −18°C/0°F for 4+ days kills all stages (standard food- industry disinfestation). Home freezers vary — give it a week for thick bags.
  • Pheromone traps catch males only — they confirm and date-stamp the infestation but will never eliminate it. Zero catch for 3 consecutive weeks = clean.
  • Adults live ~2 weeks without mating success once traps + food removal collapse the population — the visible-moth tail after a proper day-0 is normal, not failure.

Workflow

  1. Triage: protocol --level mild|moderate|severe prints the full staged plan (find → pull → freeze → clean → trap → watch).
  2. Pull everything dry from the infested zone — including unopened boxes (larvae enter through seams). Run each through disposition --item "..." for freeze/toss/heat calls.
  3. Freeze-kill keepers (−18°C, ≥4 days; a week for thick packages), then transfer to glass/metal with gasket lids. Moths cannot chew glass.
  4. Deep clean on the same day — vacuum every crack, seam, and corner in and around the cabinets (include under-shelf lips, shelf pins, ceiling corners within ~1 m, and the cabinet top gap). Wipe with vinegar/dish soap; let dry. Empty the vacuum OUTSIDE.
  5. Traps: traps --cabinets N — placement plan (one per cabinet zone, at eye level, away from windows/drafts, never stacked near each other).
  6. Watch: watch --start DATE --catch-day7 N --catch-day14 N → verdict against thresholds (day7 >5 = protocol gap, day14 >1 = missed source, day14 =0 = on track, day30+ 3-weeks-zero = declared clean).
  7. Quarantine everything new: freeze bulk goods for 4 days before shelving; inspect birdseed/pet food on arrival (top sources).

Common Pitfalls

  1. Throwing out only the visibly infested bag. Larvae have already migrated — pull the ENTIRE dry-goods zone, not the casualties.
  2. Trusting "sealed" boxes. Cardboard seams and folded flaps are larva-doors. Unopened ≠ safe.
  3. Skipping the crack-cleaning. Pupae sit in seams away from food; this is the actual comeback mechanism.
  4. Treating pheromone traps as the weapon. They catch ~males only and saturate; they date-stamp progress, they don't collapse populations — food removal does.
  5. Cleaning before pulling. Adults re-oviposit on the next night's goods. Pull → freeze/toss → clean, in that order, same day.
  6. Forgetting pet food and birdseed — the two most common import vectors. Dry pet food must go through the same protocol.
  7. Sprays/aerosols in food cabinets — unnecessary and contaminates food-contact surfaces; vacuum + soap is the whole job.
  8. Declaring victory at day 10. The cycle is 4–8 weeks; only 3 consecutive zero-catch weeks (day ~30–45) is a clean verdict.

Verification Checklist

  • Level triaged and full protocol printed before touching anything
  • ALL dry goods pulled (incl. unopened, spices, tea, chocolate, pet food)
  • Every keeper frozen −18°C ≥4 days (or heat-treated) before re-storage
  • Keepers re-stored in glass/metal gasket containers
  • Cracks/seams/corners vacuumed then wiped; vacuum emptied outside
  • Traps placed per plan (count + eye level + spacing)
  • Day 7 / 14 / 30 trap checks logged; verdict from thresholds
  • New bulk goods quarantine habit installed (freeze-on-arrival)

Safety Notes

  • Freeze-treat, never microwave sealed bags; heat-treat only true oven- safe containers at 60°C/140°F for 30 min.
  • Pheromone traps are non-toxic; keep out of reach of pets that might eat the sticky insert.
  • If larvae appear in bedroom closets or wool items — that's clothes moths, a different protocol (see When NOT to use).

Related skills

Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.

by Iván857 installs69 stars

Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.

by nssa.io1.0k installs47 stars

Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.

by Iván561 installs18 stars

Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.

by fly0pants4.3k installs296 stars

Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.

by johnpatternai22 installs8 stars

More from voronindenis5

Browse all skills

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.

by voronindenis51 installs

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.

by voronindenis52 installs

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.

by voronindenis52 installs

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.

by voronindenis51 installs

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.

by voronindenis51 installs