Zum Hauptinhalt springen
Dieser Inhalt ist noch nicht in Ihrer Sprache verfügbar und wird auf Englisch angezeigt.

Sharp Edges

Skill Verifiziert Aktiv
Teil von:Sharp Edges

Identifies error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes. Use when reviewing API designs, configuration schemas, cryptographic library ergonomics, or evaluating whether code follows 'secure by default' and 'pit of success' principles. Triggers: footgun, misuse-resistant, secure defaults, API usability, dangerous configuration.

Zweck

To proactively identify and mitigate security vulnerabilities introduced by poor API design, dangerous configurations, and insecure defaults, ensuring that secure usage is the path of least resistance.

Funktionen

  • Identifies algorithm selection footguns
  • Detects dangerous defaults and configuration cliffs
  • Analyzes primitive vs. semantic APIs for misuse potential
  • Highlights silent failure modes in security operations
  • Provides language-specific sharp edge patterns

Anwendungsfälle

  • Reviewing new API or library designs for security flaws
  • Auditing configuration schemas for dangerous options
  • Assessing cryptographic API ergonomics for misuse resistance
  • Evaluating interfaces for adherence to 'secure by default' principles

Nicht-Ziele

  • Finding implementation bugs or standard code review issues
  • Performance optimization analysis
  • Business logic flaw detection

Workflow

  1. Identify security-relevant surfaces (APIs, configs)
  2. Probe edge cases (zero/empty/null inputs, defaults)
  3. Model threats from different user types (malicious, lazy, confused)
  4. Reproduce and validate identified sharp edges

Installation

Zuerst Marketplace hinzufügen

/plugin marketplace add trailofbits/skills
/plugin install sharp-edges@trailofbits

Qualitätspunktzahl

Verifiziert
95 /100
Analysiert about 22 hours ago

Vertrauenssignale

Letzter Commit3 days ago
Sterne5.2k
LizenzCC-BY-SA-4.0
Status
Quellcode ansehen

Ähnliche Erweiterungen

Soul Guardian

100

Drift detection + baseline integrity guard for agent workspace files with automatic alerting support

Skill
prompt-security

Audit Dependency Versions

100

Audit project dependencies for version staleness, security vulnerabilities, and compatibility issues. Covers lock file analysis, upgrade path planning, and breaking change assessment. Use before a release to ensure dependencies are current and secure, during periodic maintenance reviews, after receiving a security advisory, when upgrading to a new language version, before submitting to CRAN or npm, or when inheriting a project to assess its dependency health.

Skill
pjt222

Codex Diff Develop

100

Revisa el diff de la rama actual frente a develop en proyectos Drupal 11 siguiendo la metodología Codex (lógica de negocio, edge cases de hooks/queries, seguridad, performance, completitud). Genera un informe .md en la carpeta del IDE detectado (.antigravity/, .cursor/, .vscode/ o docs/) con hallazgos por severidad y soluciones accionables. Usar cuando el usuario pida "Revisión diff develop", "revisión diff develop", "diff develop", "revisar diff", "codex diff" o expresiones similares con intención de auditar cambios contra develop. Triggers: diff develop, codex diff, revisión diff, lint diff develop, auditar diff.

Skill
j4rk0r

Sdk Dx

100

Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"

Skill
jonathimer

Investigate Capa Root Cause

100

Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.

Skill
pjt222

Toprank Weekly Review

100

Run a weekly SEO review for one registered website, write audit artifacts, and choose the next best safe action.

Skill
nowork-studio