sharp-edges

Analyze API surfaces and configuration schemas to detect misuse-prone designs.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/roderik/mpe --skill sharp-edges
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/roderik/mpe/tree/main/.agents/skills/sharp-edges
Command: npx skills add https://github.com/roderik/mpe --skill sharp-edges

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security engineers and developers quickly identify error-prone API designs, dangerous defaults, and configuration pitfalls that enable insecure behavior, enabling safer library interfaces.

Core Features & Use Cases

  • Footgun detection across API surfaces, configuration schemas, and default-value decisions to surface insecure patterns.
  • Guidance for secure-by-default design and ergonomic API choices to minimize misuse opportunities.
  • Use Case: Evaluate a new library's public API to surface potential misuse paths and provide recommended defaults and validation patterns.

Quick Start

Run a design-review on a library's public API to surface misuse paths and unsafe defaults. Request actionable mitigations and safe defaults based on the references in this Skill.

Frequently Asked Questions about sharp-edges

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify API design footguns and unsafe defaults in my library?▼

To identify API design footguns and unsafe defaults, analyze API surfaces and configuration schemas to detect misuse-prone designs and dangerous configurations. This process surfaces insecure patterns and provides actionable mitigations with secure-by-default recommendations.

What are common API security pitfalls related to cryptographic ergonomics?▼

Common API security pitfalls involving cryptographic ergonomics include dangerous default values and error-prone configurations that enable insecure behavior. Analyzing these API surfaces helps surface footguns and recommend safe defaults for proactive mitigation.

How do I check if my configuration patterns are secure by default?▼

To check if configuration patterns are secure by default, evaluate your configuration schemas against best-practice checks and detection patterns. This review validates default-value decisions and identifies insecure behavior opportunities for proactive mitigation.

Can I review a public API surface to find potential misuse paths?▼

You can review a public API surface to find potential misuse paths by running a design-review against curated detection patterns. This analysis surfaces footguns and provides recommended safe defaults and validation patterns.

Does this API security analysis work across different programming languages and frameworks?▼

This API security analysis applies across languages and frameworks to evaluate library interfaces. It uses a curated set of detection patterns and best-practice checks to surface footguns and secure-by-default opportunities regardless of the specific environment.