Who created the Sharp Edges skill?

This skill was developed by Trail of Bits, a premier security research and auditing firm, as part of their suite of security-focused developer tools.

How does this skill improve code security?

It identifies patterns that are technically valid but practically dangerous, guiding developers toward 'secure by default' implementations where the easiest path is the safest.

Does this replace traditional security scanners?

It complements them. While scanners look for known vulnerabilities, Sharp Edges looks at the design level to prevent the classes of errors that scanners often miss.

What is a 'footgun' in API design?

A 'footgun' is a design feature or API pattern that, while functional, makes it incredibly easy for a developer to accidentally introduce a bug or security vulnerability.

When should I use the Sharp Edges skill?

Trigger this skill during API design reviews, when defining configuration schemas, or when implementing sensitive cryptographic logic to catch ergonomic flaws.

Sharp Edges Security Auditor

Name: Sharp Edges Security Auditor
Author: plurigrid

byplurigrid

•

Security & Testing

Identifies error-prone API designs and dangerous configuration patterns to prevent security vulnerabilities and misuse.

About

The Sharp Edges skill, developed by Trail of Bits, helps developers identify 'footgun' designs—architectural patterns that make security mistakes easy or even inevitable. It evaluates API ergonomics, configuration schemas, and cryptographic implementations against 'secure by default' principles, ensuring that the easiest path for a developer is also the most secure. By catching misuse-resistant flaws early in the design or review phase, it helps teams build more resilient software and avoid common security pitfalls before they reach production.

Key Features

Evaluates configuration schemas for dangerous or insecure defaults
Detects error-prone API design patterns and architectural 'footguns'
Promotes 'pit of success' principles in software architecture
Identifies designs that violate 'secure by default' standards
2 GitHub stars
Reviews cryptographic library ergonomics for potential developer misuse

Use Cases

Reviewing new REST or GraphQL API designs for security ergonomics
Evaluating internal library implementations to ensure they are misuse-resistant
Auditing complex configuration schemas for insecure default settings

About

Key Features

Evaluates configuration schemas for dangerous or insecure defaults
Detects error-prone API design patterns and architectural 'footguns'
Promotes 'pit of success' principles in software architecture
Identifies designs that violate 'secure by default' standards
2 GitHub stars
Reviews cryptographic library ergonomics for potential developer misuse

Use Cases

Reviewing new REST or GraphQL API designs for security ergonomics
Evaluating internal library implementations to ensure they are misuse-resistant
Auditing complex configuration schemas for insecure default settings