One-click install
npx skills add https://github.com/dakshrawat298-gif/SOL-ALPHA-GUARDIAN --skill sharp-edges-dakshrawat298-gif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/dakshrawat298-gif/SOL-ALPHA-GUARDIAN/tree/main/packages/skills/skills/sharp-edges
Command: npx skills add https://github.com/dakshrawat298-gif/SOL-ALPHA-GUARDIAN --skill sharp-edges-dakshrawat298-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Evaluates whether APIs, configurations, and interfaces are resistant to developer misuse by identifying designs where the "easy path" leads to insecurity.

Core Features & Use Cases

  • Detects common sharp edges across API design, configuration schemas, and cryptographic ergonomics.
  • Provides threat modeling guidance for adversaries (The Scoundrel, The Lazy Developer, The Confused Developer) and an analysis workflow.
  • Supplies references and practical guidance to harden defaults and reduce misconfigurations.

Quick Start

Scan a codebase to surface common security-footgun patterns and generate actionable remediation guidance.

Frequently Asked Questions about sharp-edges

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

FAQPage Schema
How do I find security footguns in my API design and configuration schemas?

Security footguns are API designs where the easy path leads to insecurity, such as unsafe defaults or misconfigurations in cryptographic APIs and authentication code, which threat modeling against adversaries like The Lazy Developer can help surface.

What is a security footgun pattern in code?

Security footguns are API designs where the easy path leads to insecurity, such as unsafe defaults or misconfigurations in cryptographic APIs and authentication code, which threat modeling against adversaries like The Lazy Developer can help surface.

How do I scan a codebase for unsafe defaults and misuse patterns?

Scanning a codebase for unsafe defaults involves applying static analysis to API libraries and authentication code to surface misuse patterns, outputting actionable findings with severity classifications and concrete mitigations to support secure-by-default design.

Does this security analysis work for cryptographic APIs and authentication code?

Yes, this analysis applies to cryptographic APIs and authentication code, evaluating whether interfaces are resistant to developer misuse by identifying designs where the easy path leads to insecurity and providing hardening guidance.

Can I get threat modeling guidance for confused or lazy developer misuse patterns?

Yes, you can get threat modeling guidance for adversaries including The Scoundrel, The Lazy Developer, and The Confused Developer, along with an analysis workflow to apply secure-by-default design principles to your codebase.

What's the best way to harden configuration schemas against misconfigurations?

The best way to harden configuration schemas is to identify designs where the easy path leads to insecurity, then apply practical guidance and concrete mitigations to reduce misconfigurations and enforce secure-by-default defaults.