BC Smart Contract Audit Workflow by Atlas
Smart contract audit and DeFi security triage skill for Solidity, EVM protocols, bug bounty programs, Code4Arena, Sherlock, and HackenProof. Maps attack surface, prioritizes vulnerabilities, and generates structured audit checklists and security reports. Use for smart contract review, DeFi protocol audit, Solidity vulnerability scanning, and bug bounty target triage.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 7
✓ No critical or high findings
Medium and low: 7
-
low Risky intent
intent-offensive-securityREADME.md:7Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Keywords: smart contract audit, DeFi audit, Solidity audit, EVM security, vulnerability scanner, bug bounty, Code4rena, Sherlock, HackenProof.
detector -
low Risky intent
intent-offensive-securityskill-card.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Developers, security reviewers, auditors, and bug bounty researchers use this skill to perform a fast first-pass review of Solidity/EVM smart contracts, prioritize likely vulnerability classes, and pr
-
low Risky intent
intent-offensive-securitySKILL.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use)description: Smart contract audit and DeFi security triage skill for Solidity, EVM protocols, bug bounty programs, Code4Arena, Sherlock, and HackenProof. Maps attack surface, prioritizes vulnerabiliti
-
low Risky intent
intent-offensive-securitySKILL.md:48Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- bug bounty target prioritization
-
low Risky intent
intent-offensive-securitySKILL.md:56Offensive-security / dual-use content (legitimate for authorised testing; review intended use)A lightweight **smart contract audit workflow** and **DeFi audit checklist** skill for Solidity/EVM protocols, bug bounty hunters, Code4rena wardens, Sherlock auditors, and HackenProof researchers.
-
low Risky intent
intent-offensive-securitySKILL.md:80Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- bug bounty report template
-
low Risky intent
intent-offensive-securitySKILL.md:96Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- bug bounty triage
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Smart Contract Audit Workflow by Atlas) differs from the folder (atlas-smart-contract-auditor)
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 82 steps
- 100Execution cost. Instruction body is 1961 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 369: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 82 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.