sharp-edges

Identify security-critical design flaws and insecure configuration patterns in software projects.

1|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/AidenSbVevo/claude-code-starter --skill sharp-edges-aidensbvevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/AidenSbVevo/claude-code-starter/tree/main/skills/tob-sharp-edges/skills/sharp-edges
Command: npx skills add https://github.com/AidenSbVevo/claude-code-starter --skill sharp-edges-aidensbvevo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify error-prone APIs, dangerous configurations, and design flaws that lead to security vulnerabilities, ensuring that the secure path is the easiest path to take.

Core Features & Use Cases

  • Security-Relevant API Auditing: Evaluates authentication, cryptography, and session management interfaces for common misuse patterns.
  • Configuration Schema Analysis: Probes for dangerous defaults, unvalidated constructor parameters, and silent failure modes in configuration files.
  • Use Case: Use this during a design review of a new authentication library to ensure that developers cannot accidentally bypass security checks or use weak cryptographic algorithms.

Quick Start

Use the sharp-edges skill to analyze the current directory for dangerous API designs and insecure 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 codebase for dangerous API design flaws and security footguns?

Auditing for dangerous API design flaws involves evaluating authentication and cryptography interfaces for common misuse patterns. This process systematically probes configuration schemas for dangerous defaults, ensuring secure-by-default implementation.

What are common cryptographic algorithm selection footguns and how do I identify them?

Cryptographic algorithm selection footguns occur when APIs permit weak cryptographic algorithms or dangerous defaults. You identify them by conducting systematic threat modeling and edge-case probing during a design review of security-critical libraries.

Can I use this for threat modeling and edge-case probing of an authentication library?

Yes, this evaluates authentication and session management interfaces for common misuse patterns during design reviews. It provides systematic threat modeling and edge-case probing to ensure secure-by-default implementation in authentication libraries.

How do I check for silent failure modes and unvalidated constructor parameters in my configuration schema?

You check for silent failure modes and unvalidated constructor parameters by running a configuration schema analysis on your software project. This probes for dangerous defaults and insecure configuration patterns that lead to vulnerabilities.

What is secure-by-default API design and why is it important for session management?

Secure-by-default API design ensures that the easiest path developers can take when using an interface is the secure one. It is important for session management because it prevents accidental security bypasses and eliminates error-prone configurations.