sharp-edges

Analyze API designs and configuration schemas for security footguns.

1|Updated Jan 31, 2026

Search Tags:#security #api design #secure coding #developer experience #configuration security #footgun analysis

Ready to run

npx skills add https://github.com/allanninal/claude-code-skills --skill sharp-edges-allanninal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/allanninal/claude-code-skills/tree/main/skills/sharp-edges
Command: npx skills add https://github.com/allanninal/claude-code-skills --skill sharp-edges-allanninal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and helps you fix error-prone APIs, dangerous configurations, and "footgun" designs that enable security mistakes, making your code more secure and robust.

Core Features & Use Cases

API Design Review: Evaluate interfaces for resistance to developer misuse.
Configuration Auditing: Detect dangerous options in configuration schemas.
Security Principle Enforcement: Ensure code follows "secure by default" and "pit of success" principles.
Use Case: Before releasing a new authentication library, use this Skill to review its API design and ensure that the easiest path for a developer is also the most secure one, preventing common vulnerabilities like algorithm confusion or weak defaults.

Quick Start

Analyze the provided API design documentation for potential security footguns.

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 misuse risks and security footguns in my code?▼

To identify API misuse risks, you analyze API designs and configuration schemas for dangerous defaults, silent failures, and stringly-typed security issues. This reveals error-prone interfaces and cryptographic library footguns that enable developer errors.

What are dangerous defaults in configuration security and how do I audit them?▼

Dangerous defaults in configuration security are pre-set options that leave systems vulnerable. You audit them by analyzing configuration schemas to detect configuration cliffs and ensure secure by default principles are followed.

How do I review an API design for secure coding and pit of success principles?▼

Reviewing an API design for secure coding involves analyzing its resistance to misuse based on primitive vs. semantic APIs. This ensures the easiest developer path is the most secure one, preventing algorithm confusion and weak defaults.

Can I analyze cryptographic library ergonomics for potential security vulnerabilities?▼

You can analyze cryptographic library ergonomics to identify sharp edges and security vulnerabilities. This focuses on algorithm selection and primitive vs. semantic APIs to prevent developers from making critical cryptographic implementation errors.

What is stringly-typed security and how does it create API sharp edges?▼

Stringly-typed security creates API sharp edges by using strings to handle security controls, which enables silent failures and developer errors. Analyzing this identifies footguns where weak string inputs bypass intended security restrictions.