sharp-edges

Detects insecure API usage, dangerous defaults, and configuration flaws in code and config files.

47|5|Updated Apr 25, 2026

Search Tags:#security #api #configuration #cryptography #misconfiguration #defaults

Ready to run

npx skills add https://github.com/RedHatProductSecurity/prodsec-skills --skill sharp-edges-redhatproductsecurity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/sharp-edges
Command: npx skills add https://github.com/RedHatProductSecurity/prodsec-skills --skill sharp-edges-redhatproductsecurity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps developers and security auditors detect APIs and configurations that are prone to misuse and could lead to security vulnerabilities.

Core Features & Use Cases

Security Review: Analyzes APIs, configuration schemas, and cryptographic interfaces for dangerous choices.
Configuration Audit: Detects insecure defaults and risky parameter settings in code and config files.
Use Case: During an API review, identify if cryptographic algorithms can be set to insecure options or if boolean flags disable essential security checks.

Quick Start

Review code snippets or config files for patterns such as insecure algorithm choices, zero or negative timeouts, or boolean flags that disable security features, to find potential sharp edges.

Frequently Asked Questions about sharp-edges

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

FAQPage Schema

How do I detect insecure API designs and misconfigurations in my codebase?▼

You can audit cryptographic interfaces and configuration schemas to detect dangerous defaults by checking if algorithms can be set to insecure options, if boolean flags disable security features, or if risky parameters like zero timeouts exist in the codebase.

What are common dangerous defaults to look for during a security review?▼

Common dangerous defaults include insecure cryptographic algorithm choices, boolean flags that disable essential security checks, and risky parameter settings like zero or negative timeouts within API configurations and codebase files.

Can I use this to audit configuration files for risky parameter settings?▼

Yes, you can audit configuration schemas and files to identify risky parameter settings and insecure defaults, ensuring that critical security parameters are validated and secure by default across various development environments.

Does this approach work for analyzing cryptographic interfaces in different environments?▼

Yes, this approach analyzes cryptographic interfaces across various development environments to identify dangerous choices and ensure critical security parameters are validated and secure by default.

What is the best way to identify APIs that are prone to misuse?▼

The best way to identify APIs prone to misuse is to review code for patterns where security features can be disabled or insecure options selected, detecting configuration flaws and dangerous defaults that could lead to vulnerabilities.