Skip to main content

sharp-edges

Identify error-prone APIs and dangerous configurations

설치로 이동

소스 정보

저장소
Zidong-LLC/BIBLIOTECA
최근 소스 활동
2026년 3월 11일 13:02
감지된 SKILL.md 언어
영어
스타
36
포크
22

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
sharp-edges
description
Identify error-prone APIs and dangerous configurations
risk
safe
source
https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges
date_added
2026-02-27
# 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 usage - Identifying configurations that could cause issues - Analyzing code for error-prone patterns - Assessing risk in API design or configuration choices - Performing security audits focused on API misuse ## Instructions This skill helps identify problematic APIs and configurations: 1. **API Analysis**: Review API usage for error-prone patterns 2. **Configuration Review**: Identify dangerous or risky configurations 3. **Pattern Recognition**: Spot common mistakes and pitfalls 4. **Risk Assessment**: Evaluate the potential impact of identified issues ## Common Sharp Edges ### Error-Prone APIs - APIs with complex parameter requirements - APIs with non-obvious failure modes - APIs that require careful resource management - APIs with timing or concurrency issues - APIs with unclear error handling ### Dangerous Configurations - Default settings that are insecure - Configurations that bypass security controls - Settings that enable dangerous features - Options that reduce system reliability - Parameters that affect performance negatively ## Detection Strategies 1. **Code Review**: Look for known problematic patterns 2. **Static Analysis**: Use tools to identify risky API usage 3. **Configuration Audits**: Review configuration files for dangerous settings 4. **Documentation Review**: Check for warnings about API usage 5. **Experience-Based**: Leverage knowledge of common pitfalls ## Best Practices - Document identified sharp edges - Provide clear guidance on safe usage - Create examples of correct vs incorrect usage - Recommend safer alternatives when available - Update documentation with findings ## Resources For more information, see the [source repository](https://github.com/trailofbits/skills/tree/main/plugins/sharp-edges).
GitHub에서 보기