secure-workflow-guide

Guides Trail of Bits' 5-step smart contract security workflow using Slither, Echidna, and Manticore.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill secure-workflow-guide-ayoub-ouederni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secure-workflow-guide
Source: https://github.com/Ayoub-ouederni/SENTINEL/tree/main/.claude/skills/secure-workflow-guide
Command: npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill secure-workflow-guide-ayoub-ouederni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Smart contract developers often skip structured security review or rely on ad-hoc checks, missing vulnerabilities that automated detectors and property-based testing would catch. This Skill walks you through Trail of Bits' 5-step secure development workflow so every check-in or pre-deployment review follows a consistent, thorough process. ## Core Features & Use Cases - Automated Vulnerability Scanning: Runs Slither with 70+ detectors, parses findings by severity, and recommends fixes with file references. - Special Feature Validation: Checks upgradeability risks, ERC conformance, and token integration patterns only when applicable to your codebase. - Visual Security Inspection: Generates inheritance graphs, function summaries, and state-variable authorization diagrams to expose shadowing and access control issues. - Property Documentation & Testing: Helps document security invariants and set up Echidna fuzzing or Manticore symbolic execution. - Use Case: Before deploying an upgradeable ERC20 staking contract, run the workflow to get a clean Slither report, validated upgrade safety, documented invariants with fuzzing coverage, and a prioritized action plan. ## Quick Start Ask the assistant to run the secure development workflow on your Solidity project before your next deployment.

Frequently Asked Questions about secure-workflow-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Slither security scan on my Solidity project?

Run Slither with the command 'slither . --exclude-dependencies' to execute 70+ built-in vulnerability detectors. The workflow then parses findings by severity, explains each issue with file references, and helps triage false positives.

What tools check smart contract upgradeability risks?

Use slither-check-upgradeability to detect 17 ways upgrades can fail, including storage layout collisions and unprotected initialize functions. The workflow runs this automatically when proxy or upgradeable patterns are detected in your codebase.

How do I set up Echidna fuzzing for smart contract invariants?

Document your security properties as Solidity functions prefixed with 'echidna_', then configure echidna.yaml with test mode, run limits, and sender addresses. The workflow helps define invariants like balance sufficiency and state consistency before fuzzing.

Does this workflow work if Slither is not installed?

Slither is required for Steps 1-3 since manual checking cannot replicate 70+ detector patterns or generate visual diagrams. You must install Slither or explicitly document why it is blocked before proceeding.

What security areas do automated tools miss in smart contracts?

Automated tools miss privacy leaks, front-running and MEV risks, weak randomness, signature issues, and DeFi-specific risks like oracle manipulation and flash loans. Step 5 of the workflow manually reviews these areas by searching your codebase for risky patterns.