CommunityImagengithub.com

trailofbits/secure-workflow-guide

Guía a través del flujo de trabajo de desarrollo seguro de 5 pasos de Trail of Bits. Ejecuta análisis de Slither, verifica características especiales (actualizabilidad/conformidad ERC/integración de tokens), genera diagramas de seguridad visuales, ayuda a documentar propiedades de seguridad para fuzzing/verificación y revisa áreas de seguridad manuales.

¿Qué es secure-workflow-guide?

El skill `trailofbits/secure-workflow-guide` automatiza el flujo de trabajo de seguridad de 5 pasos de Trail of Bits, diseñado para ayudar a los desarrolladores a identificar y mitigar vulnerabilidades en contratos inteligentes de Solidity. Es compatible con agentes de IA como Claude Code, Codex y Cursor, pero interactúa directamente con las herramientas de seguridad del ecosistema de Trail of Bits. El skill ejecuta análisis estáticos con Slither, detecta características de contratos como actualizabilidad, cumplimiento de estándares ERC (por ejemplo, ERC20, ERC721) e integraciones de tokens externos. Además, genera diagramas visuales de la arquitectura del contrato, ayuda a documentar propiedades de seguridad (útiles para fuzzing con Echidna o verificación formal con Certora) y guía la revisión manual de áreas de alto riesgo. Está basado en la guía 'Secureum' de Trail of Bits y su documentación oficial, proporcionando un enfoque estructurado y práctico para hardening de seguridad.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/trailofbits/skills/tree/main/skills/secure-workflow-guide

Installed? Explore more Imagen skills: steipete/songsee, affaan-m/frontend-design, mattpocock/improve-codebase-architecture · View all 6 →

Ver original→Ver todas las habilidades

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentación

¿Qué hace secure-workflow-guide?

Guía a través del flujo de trabajo de desarrollo seguro de 5 pasos de Trail of Bits. Ejecuta análisis de Slither, verifica características especiales (actualizabilidad/conformidad ERC/integración de tokens), genera diagramas de seguridad visuales, ayuda a documentar propiedades de seguridad para fuzzing/verificación y revisa áreas de seguridad manuales.

Resumen

Este flujo de trabajo automatiza el proceso de revisión de seguridad recomendado por Trail of Bits, combinando herramientas de análisis estático (Slither), generación de documentación visual (Graphviz) y listas de verificación para áreas de seguridad manuales. Es ideal para desarrolladores que buscan integrar prácticas de seguridad en su ciclo de CI/CD.

Plataformas Soportadas

  • Claude Code
  • Cursor
  • Codex CLI

Requisitos

  • Slither: Instalado y disponible en el PATH (pip install slither-analyzer).
  • Graphviz: Instalado para generar diagramas (apt install graphviz).
  • Acceso a contrato inteligente: Archivos .sol en el directorio de trabajo.

Pasos del Flujo de Trabajo

  1. Paso 1: Análisis Estático

    • Ejecuta slither . en el directorio del proyecto.
    • Revisa la salida en busca de vulnerabilidades comunes (reentrancia, desbordamientos, etc.).

  2. Paso 2: Verificación de Características Especiales

    • Detecta si el contrato es actualizable (patrones de proxy).
    • Verifica cumplimiento de estándares ERC (ERC20, ERC721, ERC1155).
    • Identifica integraciones con tokens externos (balances, transferencias).

  3. Paso 3: Diagrama de Seguridad Visual

    • Genera un diagrama con Graphviz mostrando el flujo de control y las interacciones entre contratos.
    • Resalta puntos de entrada externos y áreas de riesgo.

  4. Paso 4: Documentación de Propiedades

    • Ayuda a documentar propiedades de seguridad utilizando el formato de Echidna o Certora.
    • Ejemplo de propiedad documentada: assert(balanceOf[owner] >= 0).

  5. Paso 5: Revisión Manual Dirigida

    • Proporciona una lista de verificación para áreas que requieren revisión manual (lógica de gobernanza, control de acceso, etc.).

Ejemplo de Uso

# Iniciar el flujo de trabajo con un contrato
> slither .
> detect upgradeability
> generate diagram
> document properties
> manual review areas

Referencias

Contribuciones

Las contribuciones son bienvenidas. Por favor, envía un pull request o reporta un issue en el repositorio oficial.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

trailofbits/address-sanitizer

AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C/C++ code to find buffer overflows and use-after-free bugs.

trailofbits/aflpp

AFL++ is a fork of AFL with better fuzzing performance and advanced features. Use for multi-core fuzzing of C/C++ projects.

trailofbits/agentic-actions-auditor

Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

trailofbits/algorand-vulnerability-scanner

Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal).

trailofbits/ask-questions-if-underspecified

Clarify requirements before implementing. Use when serious doubts arise.

trailofbits/atheris

Atheris is a coverage-guided Python fuzzer based on libFuzzer. Use for fuzzing pure Python code and Python C extensions.

trailofbits/audit-augmentation

Augments Trailmark code graphs with external audit findings from SARIF static analysis results and weAudit annotation files. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, cross-referencing Semgrep or CodeQL findings with call graph data, or visualizing audit findings in the context of code structure.

trailofbits/audit-context-building

Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.

trailofbits/audit-prep-assistant

Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).

trailofbits/burpsuite-project-parser

Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.

trailofbits/cairo-vulnerability-scanner

Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.

trailofbits/cargo-fuzz

cargo-fuzz is the de facto fuzzing tool for Rust projects using Cargo. Use for fuzzing Rust code with libFuzzer backend.

trailofbits/chrome-mcp-troubleshooting

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

trailofbits/claude-in-chrome-troubleshooting

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

trailofbits/code-improver

Runs an autonomous review-and-fix improvement loop over any code target — a skill, plugin, module, or directory — using a reviewer the user names: any installed skill or agent. Keeps a cross-round findings ledger, escalates when fixes stop converging, and guards scope mechanically. Use when asked to 'improve this code until review passes', 'run an improvement loop with <reviewer>', or to iterate review-and-fix with a specific reviewer. For skills prefer the skill-improver entry; for a branch prefer pr-improver.

trailofbits/code-maturity-assessor

Systematic code maturity assessment using Trail of Bits' 9-category framework. Analyzes codebase for arithmetic safety, auditing practices, access controls, complexity, decentralization, documentation, MEV risks, low-level code, and testing. Produces professional scorecard with evidence-based ratings and actionable recommendations.

trailofbits/codeql

Scans a codebase for security vulnerabilities using CodeQL's interprocedural data flow and taint tracking analysis. Triggers on "run codeql", "codeql scan", "codeql analysis", "build codeql database", or "find vulnerabilities with codeql". Supports "run all" (security-and-quality + security-experimental suites) and "important only" (high-precision security findings) scan modes. Also handles creating data extension models and processing CodeQL SARIF output.

trailofbits/constant-time-analysis

Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.

trailofbits/constant-time-testing

Constant-time testing detects timing side channels in cryptographic code. Use when auditing crypto implementations for timing vulnerabilities.

trailofbits/cosmos-vulnerability-scanner

Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

Skills relacionados

steipete/songsee

Generate spectrograms and feature-panel visualizations from audio with the songsee CLI.

community

affaan-m/frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.

community

mattpocock/improve-codebase-architecture

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

community

lobehub/add-provider-doc

Add documentation for a new AI provider — usage docs, env vars, Docker config, image resources.

community

addyosmani/browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

community

bytedance/chart-visualization

This skill should be used when the user wants to visualize data. It intelligently selects the most suitable chart type from 26 available options, extracts parameters based on detailed specifications, and generates a chart image using a JavaScript script.

community
← More Imagen skills