sharp-edges

Analyze code and designs for error-prone APIs and dangerous configurations.

19.0k|5.6k|Updated Jul 9, 2024
One-click install
npx skills add https://github.com/elizaOS/eliza --skill sharp-edges-elizaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/elizaOS/eliza/tree/main/packages/skills/skills/sharp-edges
Command: npx skills add https://github.com/elizaOS/eliza --skill sharp-edges-elizaos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies dangerous API designs, insecure default configurations, and confusing interfaces that make security mistakes easy for developers.

Core Features & Use Cases

  • API Design Review: Analyzes interfaces for "footguns" that lead to vulnerabilities.
  • Configuration Auditing: Flags dangerous default settings or insecure configuration options.
  • Use Case: Before releasing a new authentication library, use this Skill to ensure that common mistakes like weak password policies or insecure session handling are caught by the design itself.

Quick Start

Analyze the security design of the provided API specification for potential misuse.

Frequently Asked Questions about sharp-edges

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

FAQPage Schema
How do I identify insecure API designs and dangerous defaults in my code?

Identifying insecure API designs involves analyzing interfaces for footguns where the path of least resistance leads to insecurity, catching misuse-prone configurations and dangerous defaults before release.

What makes an API misuse-resistant and secure by default?

A misuse-resistant API prevents developer confusion by eliminating configuration cliffs, silent failures, and stringly-typed security, ensuring secure algorithm selection and semantic over primitive APIs.

How do I audit my authentication library for security footguns before release?

Auditing for security footguns requires analyzing API specifications for dangerous default settings, weak policy configurations, and error-prone interfaces that enable security mistakes through developer confusion.

Can I review an API specification for configuration cliffs and silent failures?

Yes, you can review API specifications to detect configuration cliffs and silent failures by analyzing designs where insecure choices are easier than secure ones, exposing dangerous default settings.

What are common security design flaws in API configuration and algorithm selection?

Common security design flaws include dangerous default configurations, stringly-typed security parameters, primitive APIs lacking semantic safety, and algorithm selection that enables developer misuse.

When should I analyze my codebase for error-prone and insecure API patterns?

Analyze codebases for error-prone API patterns before releasing new libraries or interfaces, ensuring the design itself prevents security mistakes rather than relying on developer vigilance.