skills/panic-room-finder/SKILL.md
Expert in residential hollow space detection, hidden room discovery, and safe room planning. Helps map house dimensions, identify anomalies suggesting hidden spaces, and safely explore potential voids. Knowledge of architectural history, construction methods, and non-destructive investigation techniques. Activate on "panic room", "hidden room", "secret room", "hollow space", "house mapping", "find hidden space", "room dimensions", "hidden door", "false wall", "priest hole", "prohibition era", "safe room". NOT for illegal entry, structural modifications without permits, or bypassing security systems.
npx skillsauth add curiositech/windags-skills panic-room-finderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Discover hidden spaces through systematic investigation and safe exploration.
IF discrepancy size = >12 inches AND wall thickness = standard (4-8")
→ THEN investigate via acoustic testing first
→ IF acoustic confirms void → proceed to visual inspection
→ IF visual inspection inconclusive → use borescope
IF discrepancy size = 6-12 inches AND wall thickness = thick (>8")
→ THEN likely mechanical void (plumbing/HVAC)
→ investigate via thermal imaging
→ IF thermal shows unusual patterns → acoustic test
IF discrepancy size = >24 inches AND house era = pre-1950
→ THEN high probability of intentional hidden space
→ start with historical research
→ proceed to comprehensive investigation
IF visual clues present (mismatched trim, hollow sound, trigger mechanisms)
→ THEN prioritize visual inspection over measurement
→ document all clues before testing mechanisms
→ IF mechanism found → document before activating
IF basement/attic access reveals suspicious areas
→ THEN map from multiple access points
→ check for false walls/floors from both sides
→ IF confirmed void → assess structural safety before entry
House Age < 1920:
├── Start with historical research
├── Focus on priest holes, servant passages
├── Use acoustic testing in thick-walled areas
└── Check for speaking tubes, hidden stairs
House Age 1920-1940:
├── Focus on Prohibition-era modifications
├── Check basement and behind built-ins
├── Look for speakeasy access points
└── Test walls behind bars/entertainment areas
House Age 1940-1970:
├── Check for Cold War fallout shelters
├── Focus on basement secure rooms
├── Look for reinforced hidden doors
└── Check garage and utility area connections
House Age > 1970:
├── Focus on security-oriented safe rooms
├── Check master bedroom/walk-in closets
├── Look for electronic/mechanical triggers
└── Check for modern panic room features
Setup: 1890s rowhouse, owner noticed 3-foot discrepancy between front parlor width and adjacent dining room.
Investigation Process:
Key Decision: When measurement showed >3 feet discrepancy in Victorian house, prioritized historical research over continued measuring. This revealed the architectural pattern and guided investigation to the correct wall.
Novice Miss: Would have kept measuring other rooms instead of investigating the obvious anomaly. Expert recognized that >3 feet in Victorian = intentional service space.
Setup: 1955 ranch house, homeowner renovating basement noticed area behind furnace seemed larger from outside measurements.
Investigation Process:
Key Decision: When thermal imaging showed temperature differential, confirmed this was unconditioned space rather than mechanical void. Guided safe opening procedure.
Trade-off: Owner chose to remove panel section (minimally destructive) rather than use borescope because thermal imaging strongly confirmed substantial void.
This skill should NOT be used for:
Delegate to other skills when:
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.