sharp-edges

Name: sharp-edges
Availability: InStock
Author: manuelbrandner85

Identify error-prone APIs, dangerous configurations, and security-critical design flaws.

Updated Nov 23, 2025

Search Tags:#security #cryptography #configuration-audit #api-design #secure-by-default #vulnerability-analysis

Ready to run

npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill sharp-edges-manuelbrandner85

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and security auditors identify dangerous API designs, insecure configuration schemas, and cryptographic library misuses that lead to vulnerabilities.

Core Features & Use Cases

Misuse Resistance Analysis: Evaluates whether APIs are designed to make secure usage the path of least resistance.
Configuration Auditing: Scans for dangerous defaults, unvalidated constructor parameters, and insecure combinations in configuration files.
Use Case: Use this during an API design review to ensure that cryptographic primitives are not exposed in a way that allows developers to accidentally downgrade security or reuse nonces.

Quick Start

Use the sharp-edges-analyzer agent to perform a full security audit on the current directory to identify potential API design flaws and dangerous configuration patterns.

Frequently Asked Questions about sharp-edges

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

FAQPage Schema

How do I audit my API design for security footguns and misuse resistance?▼

To audit API design for security footguns, evaluate whether interfaces make secure usage the path of least resistance by probing cryptographic ergonomics and authentication parameters for dangerous defaults and edge cases.

What is misuse resistance analysis in secure-by-default API development?▼

Misuse resistance analysis evaluates API designs to ensure secure implementation is the easiest path, preventing developers from accidentally downgrading security or reusing nonces when consuming cryptographic primitives.

How do I check my configuration schemas for dangerous defaults and insecure patterns?▼

Check configuration schemas for dangerous defaults by scanning for unvalidated constructor parameters and insecure combinations that could expose vulnerabilities during application initialization.

Can I use threat modeling to validate authentication interfaces against developer misuse?▼

Yes, threat modeling validates authentication interfaces by performing surface identification and edge case probing to test resistance against common developer footguns and security-critical design flaws.

What's the best way to identify dangerous cryptographic library misuses in my codebase?▼

The best way to identify dangerous cryptographic library misuses is performing a full security audit on your directory to detect exposed primitives that allow developers to accidentally downgrade security.

Why does exposing cryptographic primitives in my API lead to security vulnerabilities?▼

Exposing cryptographic primitives leads to vulnerabilities because developers can accidentally downgrade security or reuse nonces when APIs lack secure-by-default configurations and misuse resistance.