secure workflow guide

Productivity Community

Skill notes

Purpose

Guides through Trail of Bits' secure development workflow - a 5-step process to enhance smart contract security throughout development. Use this: On every check-in, before deployment, or when you want a security review

The 5-Step Workflow

Covers a security workflow including:

Step 1: Check for Known Security Issues

Run Slither with 70+ built-in detectors to find common vulnerabilities: Parse findings by severity Explain each issue with file references Recommend fixes Help triage false positives

Step 2: Check Special Features

Detect and validate applicable features: Upgradeability: slither-check-upgradeability (17 upgrade risks) ERC conformance: slither-check-erc (6 common specs) Token integration: Recommend token-integration-analyzer skill Security properties: slither-prop for ERC20

Step 3: Visual Security Inspection

Generate 3 security diagrams: Inheritance graph: Identify shadowing and C3 linearization issues Function summary: Show visibility and access controls Variables and authorization: Map who can write to state variables Review each diagram for security concerns

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Productivity
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview secure-workflow-guide.preview
# Example Output

- **Step 1**: Slither findings with severity, file references, and fix recommendations
- **Step 2**: Special feature validation results (upgradeability, ERC conformance, etc.)
- **Step 3**: Visual diagrams analyzing inheritance, functions, and state variable authorization
- **Step 4**: Documented security properties and testing setup (Echidna/Manticore)
- **Step 5**: Manual review findings (privacy, front-running, cryptography, DeFi risks)
- **Action plan**: Critical/high/medium priority tasks with effort estimates

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.