Validate attacker hypotheses for Solidity smart contracts and produce structured verdicts.
npx skills add https://github.com/slvDev/weasel --skill weasel-validate
Please help me install this Agent Skill. Skill: weasel-validate Source: https://github.com/slvDev/weasel/tree/main/weasel/skills/weasel-validate Command: npx skills add https://github.com/slvDev/weasel --skill weasel-validate
This Skill helps security engineers and developers validate proposed attack vectors against smart contracts, preventing misinterpretation and duplicate findings during audits.
Provide a written attack hypothesis to Weasel, e.g., "Is there a reentrancy vulnerability after balance updates?" and request a verdict along with a suggested next step (PoC or report). This will instruct the tool to begin context gathering, code reading, and threat analysis.
High-intent search queries and answers about installing and using this skill.
To validate a smart contract vulnerability hypothesis, you provide the suspected attack vector to the skill. It reads project documentation and traces Solidity code paths to produce a structured verdict, such as CONFIRMED or NOT EXPLOITABLE, with evidence.
Attack hypothesis validation in smart contract security is the process of tracing a proposed exploit path through the codebase to determine exploitability. It prevents misinterpretation and duplicate findings by checking project context and delivering a structured verdict.
To check if a suspected reentrancy attack is exploitable, provide the hypothesis to the skill. It analyzes the referenced Solidity functions, checks guards, references known issues, and delivers a verdict with recommended next steps like a proof of concept.
Yes, you can audit Solidity code for exploitability while avoiding false positives. The skill reads README files and known issues to respect design decisions, ensuring that prior issues are classified correctly rather than reported as new vulnerabilities.
Validating smart contract attack vectors produces structured outcomes including CONFIRMED, PARTIAL, NOT EXPLOITABLE, KNOWN ISSUE, and BY DESIGN. Each verdict includes rationale, references to the analyzed code paths, and recommended next steps for reporting.
A suspected smart contract vulnerability returns a BY DESIGN verdict when the analysis references project documentation and determines the pattern is an intentional design decision rather than an exploitable flaw, preventing duplicate findings during audits.
lucaswallInvestigate Railway logs and codebase to report findings on API, deployment, and configuration issues.
enderphan94Convert verified security vulnerabilities into executable proof-of-concept code and attack narratives.
Ramprasad4121Audit Solidity smart contracts using Slither, Aderyn, and the Map-Hunt-Attack methodology.
PlamenTSVTrace SYNC_GAP, ACCUMULATION_EXPOSURE, and CONDITIONAL annotations to classify semantic invariants in smart contracts.
