What problem does it solve? Security testers often cannot distinguish real SQL injection from WAF noise, caching artifacts, or application validation errors, leading to false positives and unsafe testing. This Skill enforces a disciplined, evidence-gated workflow that only confirms SQLi when reproducible server-side oracle differences are observed under authorized scope. ## Core Features & Use Cases - Engagement Gating: Requires declared authorization, locked scope, and established host/identity/path baselines before any probe is sent. - Minimal Safe Validation: Uses single-variable, non-destructive syntax/type/logic boundary probes; forbids data extraction, UNION queries, stacked queries, and sqlmap auto-write. - Oracle-Based Confirmation: Treats WAF blocks, captchas, timeouts, single errors, and scanner hits as INCONCLUSIVE, requiring reproducible database-layer semantic differences as proof. - Use Case: During an authorized web assessment, a filter parameter returns a database error. Use this Skill to run baseline/probe/post-baseline comparisons and determine whether the behavior is a genuine, reproducible SQLi oracle or a false positive. ## Quick Start Use hunt-sqli to plan an evidence-gated, authorized validation of the suspected SQL injection on the in-scope filter parameter.
