Sharp Edges

1---
2name: sharp-edges
3description: "Identify error-prone APIs and dangerous configurations"
4source: "https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges"
5risk: safe
6---
7 
8# Sharp Edges
9 
10## Overview
11 
12Identify error-prone APIs and dangerous configurations that could lead to bugs, security vulnerabilities, or system failures.
13 
14## When to Use This Skill
15 
16Use this skill when you need to identify error-prone APIs and dangerous configurations.
17 
18Use this skill when:
19- Reviewing code for potentially dangerous API usage
20- Identifying configurations that could cause issues
21- Analyzing code for error-prone patterns
22- Assessing risk in API design or configuration choices
23- Performing security audits focused on API misuse
24 
25## Instructions
26 
27This skill helps identify problematic APIs and configurations:
28 
291. **API Analysis**: Review API usage for error-prone patterns
302. **Configuration Review**: Identify dangerous or risky configurations
313. **Pattern Recognition**: Spot common mistakes and pitfalls
324. **Risk Assessment**: Evaluate the potential impact of identified issues
33 
34## Common Sharp Edges
35 
36### Error-Prone APIs
37 
38- APIs with complex parameter requirements
39- APIs with non-obvious failure modes
40- APIs that require careful resource management
41- APIs with timing or concurrency issues
42- APIs with unclear error handling
43 
44### Dangerous Configurations
45 
46- Default settings that are insecure
47- Configurations that bypass security controls
48- Settings that enable dangerous features
49- Options that reduce system reliability
50- Parameters that affect performance negatively
51 
52## Detection Strategies
53 
541. **Code Review**: Look for known problematic patterns
552. **Static Analysis**: Use tools to identify risky API usage
563. **Configuration Audits**: Review configuration files for dangerous settings
574. **Documentation Review**: Check for warnings about API usage
585. **Experience-Based**: Leverage knowledge of common pitfalls
59 
60## Best Practices
61 
62- Document identified sharp edges
63- Provide clear guidance on safe usage
64- Create examples of correct vs incorrect usage
65- Recommend safer alternatives when available
66- Update documentation with findings
67 
68## Resources
69 
70For more information, see the [source repository](https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges).
71