sharp-edges

Name: sharp-edges
Availability: InStock
Author: sbknana

Identify security footguns in API designs, configuration schemas, and cryptographic interfaces.

10|4|Updated Feb 5, 2026

Search Tags:#security #configuration #cryptography #api-design #risk-analysis #security-review #sharp-edges

Ready to run

npx skills add https://github.com/sbknana/equipa --skill sharp-edges-sbknana

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

sharp-edges helps security- and development-teams identify error-prone API designs, dangerous configuration patterns, and footgun designs that enable insecure defaults or misuse. It provides structured guidance to harden interfaces and configurations during design, review, and auditing.

Core Features & Use Cases

Detects API design footguns such as algorithm choice, mode selection, and misused cryptography interfaces.
Flags dangerous configuration patterns including zero/magic values, insecure defaults, and unvalidated constructor parameters.
Offers concrete mitigations, checklists, and example remedies for secure-by-default software across languages.

Quick Start

Inspect the codebase or docs to surface the top three security footguns and present concrete mitigations.

Frequently Asked Questions about sharp-edges

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

FAQPage Schema

How do I identify security footguns in API designs and configuration schemas?▼

To identify security footguns in API designs and configuration schemas, analyze interfaces and configs to detect insecure defaults, dangerous patterns, and potential misuse during security reviews and code audits. This surfaces mitigations, risk classifications, and guardrails for secure-by-default design.

What are common API design footguns involving cryptography interfaces?▼

Common API design footguns involving cryptography interfaces include insecure algorithm choices, improper mode selection, and misused cryptographic functions. Detecting these footguns during security reviews helps prevent potential misuse and enables secure-by-default software design across languages.

How do I check for dangerous configuration patterns during a security review?▼

To check for dangerous configuration patterns during a security review, analyze configuration schemas for zero values, magic values, insecure defaults, and unvalidated constructor parameters. This process flags error-prone patterns and provides concrete mitigations and example remedies.

Can I apply API security analysis across different programming languages?▼

Yes, you can apply API security analysis across different programming languages. Security reviews and code audits detect dangerous patterns and insecure defaults in API designs and configurations independent of language, generating guardrails and mitigations for secure-by-default software.

What is the best way to harden insecure API defaults and dangerous configuration patterns?▼

The best way to harden insecure API defaults and dangerous configuration patterns is to analyze interfaces and schemas during design and auditing to surface footguns. This yields concrete mitigations, checklists, and example remedies for secure-by-default software.

Why does my API design enable insecure defaults and potential misuse?▼

Your API design enables insecure defaults and potential misuse because of error-prone design choices and dangerous configuration patterns like magic values and unvalidated parameters. Analyzing the API surfaces these footguns and provides structured guidance to harden interfaces.