Sharp Edges
Overview
Identify error-prone APIs and dangerous configurations that could lead to bugs, security vulnerabilities, or system failures.
When to Use This Skill
Use this skill when you need to identify error-prone APIs and dangerous configurations.
Use this skill when:
Reviewing code for potentially dangerous API usageIdentifying configurations that could cause issuesAnalyzing code for error-prone patternsAssessing risk in API design or configuration choicesPerforming security audits focused on API misuseInstructions
This skill helps identify problematic APIs and configurations:
API Analysis: Review API usage for error-prone patternsConfiguration Review: Identify dangerous or risky configurationsPattern Recognition: Spot common mistakes and pitfallsRisk Assessment: Evaluate the potential impact of identified issuesCommon Sharp Edges
Error-Prone APIs
APIs with complex parameter requirementsAPIs with non-obvious failure modesAPIs that require careful resource managementAPIs with timing or concurrency issuesAPIs with unclear error handlingDangerous Configurations
Default settings that are insecureConfigurations that bypass security controlsSettings that enable dangerous featuresOptions that reduce system reliabilityParameters that affect performance negativelyDetection Strategies
Code Review: Look for known problematic patternsStatic Analysis: Use tools to identify risky API usageConfiguration Audits: Review configuration files for dangerous settingsDocumentation Review: Check for warnings about API usageExperience-Based: Leverage knowledge of common pitfallsBest Practices
Document identified sharp edgesProvide clear guidance on safe usageCreate examples of correct vs incorrect usageRecommend safer alternatives when availableUpdate documentation with findingsResources
For more information, see the source repository.