AGENT SKILL

cmichel-smart-contract-auditor-guide

Points to Christoph Michel’s (cmichel.io) long-form guide on becoming a smart contract security auditor-EVM-centric learning path, CTFs, canonical DeFi contracts, finance basics, and an FAQ (tools, scoping, compensation). Use when the user asks how to start in Solidity/EVM auditing or cites this article-not as current salary data, job placement advice, or a substitute for hands-on practice and primary documentation.

License 许可
Apache-2.0
所属仓库
zkos-labs/bastion
最近更新
2026-11-13
Stars
★ 3
Forks
1

01 前言 Front Matter

name
cmichel-smart-contract-auditor-guide
description
Points to Christoph Michel’s (cmichel.io) long-form guide on becoming a smart contract security auditor-EVM-centric learning path, CTFs, canonical DeFi contracts, finance basics, and an FAQ (tools, scoping, compensation). Use when the user asks how to start in Solidity/EVM auditing or cites this article-not as current salary data, job placement advice, or a substitute for hands-on practice and primary documentation.

03 SKILL.md 正文

cmichel.io - How to become a smart contract auditor (reference)

Educational routing only. This skill does not reproduce the full article. Read the live page for complete detail, links, and any author updates.

Canonical URL

What the guide covers (outline)

The post is Ethereum / EVM–oriented (most paid audit demand at time of writing, per author). Rough structure:

Section Topics (high level)
Prerequisites Programming first; suggests JavaScript as a gateway if new; argues reading code is foundational for review work.
Solidity & security Learn by doing; recommends CTF-style challenges (e.g. Damn Vulnerable DeFi, Ethernaut, Capture The Ether) and notes overlap / legacy Solidity caveats; mentions harder contests (e.g. Paradigm CTF) and permissionless venues (Immunefi, Code4rena).
Common contracts ERC-20 / ERC-721 nuances, proxies / delegatecall, MasterChef-style rewards, Compound-style lending, Uniswap V2 as AMM baseline-author frames these as recurring patterns in real audits.
Finance vocabulary Points to a Khan Academy derivatives chapter for options/futures/perp-style language used in DeFi.
FAQ Staying current (e.g. Twitter, BlockThreat newsletter), rough hourly bands (treat as historical), LOC/hour scoping heuristics, when to stop reviewing, tooling (Solidity Visual Developer), traits (e.g. conscientiousness), Solana as a harder pivot (Rust + account model).

How to combine with blockint

Need Skill
EVM DeFi triage patterns evm-solidity-defi-triage-agent
Broader DeFi audit / rug posture defi-security-audit-agent
Exploit post-mortems flash-loan-exploit-investigator-agent, honeypot-detection-techniques
Solana program security (different stack) solana-defi-vulnerability-analyst-agent, sealevel-attacks-solana

Guardrails

  • Stale data - compensation ranges and tool landscape are 2021-era; verify current market and tooling.
  • Not career or legal advice - hiring, visas, and contracts need professional counsel where relevant.
  • Jurisdiction - bug bounties and contests have rules; follow each program’s terms.
  • Ethics - use skills for defensive security and responsible disclosure, not theft or harassment.

Goal: a discoverable pointer to cmichel.io/how-to-become-a-smart-contract-auditor for EVM auditor education context inside blockint.

04 同仓库更多 Skills

zkos-labs
zkos-labs/bastion

bastion

Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.

★ 3
zkos-labs
zkos-labs/bastion

web2-api-firewall-administrator

Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII/secrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.

★ 3
zkos-labs
zkos-labs/bastion

transaction-screening-workflow-concepts

Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.

★ 3
zkos-labs
zkos-labs/bastion

solana-tracing-specialist

Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX/Jito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.

★ 3
zkos-labs
zkos-labs/bastion

solana-onchain-intelligence-resources

Companion to blockint-skills Solana work-official doc indexes and stacks for RPC/indexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy/regulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev/testing), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.

★ 3
zkos-labs
zkos-labs/bastion

solana-defi-vulnerability-analyst-agent

Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor/native programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.

★ 3