sharp-edges
Identifies error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes. Use when reviewing API designs, configuration schemas, cryptographic library ergonomics, or evaluating whether code follows "secure by default" and "pit of success" principles. Triggers: footgun, misuse-resistant, secure defaults, API usability, dangerous configuration.
Profile →npx skills add waybarrios/opencode-power-pack --skill sharp-edges --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Sharp Edges Analysis Evaluates whether APIs, configurations, and interfaces are resistant to developer misuse. Identifies designs where the "easy path" leads to insecurity. ## When to Use - Reviewing API or library design decisions - Auditing configuration schemas for dangerous options - Evaluating cryptographic API ergonomics - Assessing authentication/authorization interfaces - Reviewing any code that exposes security-relevant choices to developers ## When NOT to Use - Implementation bugs (use standard code review) - Business logic flaws (use domain-specific analysis) - Performance optimization (different concern) ## Core Principle **The pit of success**: Secure usage should be the path of least resistance. If developers must understand cryptography, read documentation carefully, or remember special rules to avoid vulnerabilities, the API has failed. ## Rationalizations to Reject | Rationalization | Why It's Wrong | Required Action | |-----------------|----------------|-----------------| | "It's documented" | Developers don't read docs under deadline pressure | Make the secure choice the default or only option | | "Advanced users need flexibility" | Flexibility creates footguns
- When to Use
- When NOT to Use
- Core Principle
- Rationalizations to Reject
- Sharp Edge Categories
- 1. Algorithm/Mode Selection Footguns
- 2. Dangerous Defaults
- 3. Primitive vs. Semantic APIs
- 4. Configuration Cliffs
- 5. Silent Failures
- 6. Stringly-Typed Security
- Analysis Workflow
- Phase 1: Surface Identification
- Phase 2: Edge Case Probing
What does the sharp-edges skill do?
Identifies error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes. Use when reviewing API designs, configuration schemas, cryptographic library ergonomics, or evaluating whether code follows "secure by default" and "pit of success" principles. Triggers: footgun, misuse-resistant, secure defaults, API usability, dangerous configuration.
How do I install it?
Run `npx skills add waybarrios/opencode-power-pack --skill sharp-edges --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From waybarrios/opencode-power-pack, a repository with 443 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.