sharp-edges

Analyze software designs for security vulnerabilities from API usability and insecure defaults.

1|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/arroschaves/brandaocontador-site --skill sharp-edges-arroschaves
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/arroschaves/brandaocontador-site/tree/main/.agent/skills/trailofbits-sharp-edges
Command: npx skills add https://github.com/arroschaves/brandaocontador-site --skill sharp-edges-arroschaves

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and fix security design flaws in APIs, configurations, and interfaces that make them prone to developer misuse, often referred to as "footguns."

Core Features & Use Cases

  • API Design Review: Evaluate if the "easy path" for developers leads to insecure outcomes.
  • Configuration Auditing: Detect dangerous defaults or insecure options in configuration schemas.
  • Use Case: When reviewing a new authentication library, use this Skill to ensure that common mistakes like weak password policies or insecure default settings are flagged before release.

Quick Start

Analyze the provided API specification for potential security design flaws and dangerous defaults.

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 design flaws in my API usability?

To identify security design flaws in API usability, analyze your software designs for dangerous configurations, insecure defaults, and misuse-resistant anti-patterns. Evaluating if the easy developer path leads to insecure outcomes flags potential footguns before release.

What are insecure defaults and footguns in cryptographic libraries?

Insecure defaults and footguns in cryptographic libraries are API design anti-patterns where standard or easy usage leads to vulnerable implementations. Auditing configuration schemas and authentication interfaces detects these dangerous options.

How can I audit configuration schemas for dangerous security defaults?

Audit configuration schemas for dangerous security defaults by reviewing the schema against secure design principles. Detect insecure options and validate that the default settings prevent developer misuse and alignment with a pit of success architecture.

Does this security review detect weak password policies in authentication interfaces?

Yes, this security review detects weak password policies in authentication interfaces by analyzing the API specification for common vulnerability classes. It ensures common mistakes and insecure default settings are flagged during the design phase.