sharp-edges

Identify security-footgun patterns in API designs and configuration schemas.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sharp Edges Analysis identifies error-prone APIs, dangerous configurations, and design footguns that enable security mistakes, helping teams harden interfaces before deployment.

Core Features & Use Cases

  • Detects misdesign patterns in API surfaces, authentication interfaces, and configuration schemas.
  • Documents footguns and provides concrete mitigations to promote secure-by-default design.
  • Supports security reviews across cryptographic, authorization, and data handling surfaces with practical examples.

Quick Start

Identify a new API design to surface footguns and propose secure-by-default mitigations.

Frequently Asked Questions about sharp-edges

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

FAQPage Schema
What are API security footguns and how do they enable misuse?▼

API security footguns are error-prone design patterns in authentication interfaces, cryptographic APIs, and configuration schemas that enable security mistakes. Identifying these dangerous defaults helps teams harden interfaces before deployment.

How do I audit my API design for security misconfiguration?▼

To audit API design for security misconfiguration, analyze design choices and enumerate edge cases across API surfaces, authentication modules, and configuration schemas. Validate defaults against a safety checklist to document footguns and apply concrete mitigations for secure-by-default hardening.

Can I review cryptographic API interfaces for secure-by-default patterns across different programming languages?▼

Yes, you can review cryptographic API interfaces for secure-by-default patterns across languages. The analysis applies to crypto APIs, authorization modules, and data handling surfaces, validating design choices and edge cases against a safety checklist to provide hardening guidance.

What is the best way to harden authentication module configurations before deployment?▼

The best way to harden authentication module configurations is to detect misdesign patterns, validate defaults against a safety checklist, and document concrete mitigations. This secure-by-default review surfaces dangerous configurations and provides practical examples to prevent security mistakes.

Why does my configuration schema allow insecure default settings?▼

Configuration schemas allow insecure default settings due to design footguns that prioritize flexibility over safety. Analyzing configuration systems against a safety checklist identifies these dangerous defaults, enabling teams to implement secure-by-default mitigations and prevent misuse.