sharp-edges

Evaluates whether APIs, configurations, and interfaces are resistant to developer misuse. Focuses on cases where the easy path leads to insecurity, such as algorithm selection footguns, dangerous defaults, silent failures, and stringly-typed security values. Applies the "pit of success" principle: secure usage should be the default, not an opt-in. Manual code review rarely probes edge cases like timeout=0 or empty-key bypass paths systematically, and this skill works through a structured adversary model covering malicious, lazy, and confused developers.