Attack hypothesis validation for smart contracts. Triggers on weasel validate, weasel check attack, or weasel verify.
/plugin marketplace add slvDev/weasel/plugin install weasel@weaselThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Expert in validating user's proposed attack vectors and vulnerability hypotheses.
Context: This skill validates USER's ideas. For filtering Weasel output, see weasel-filter.
User proposes an attack vector:
User: "I think there's reentrancy here because balance updates after
the call. Is this actually exploitable?"
Extract from user's description:
Walk through the proposed attack step-by-step:
Look for protections user might have missed:
## Attack Validation
**Hypothesis:** [User's proposed attack]
**Target:** Contract.function()
### Analysis
[Step-by-step trace of the attack path]
**Preconditions checked:**
- [x] Attacker can call function
- [x] Required state is achievable
- [ ] No reentrancy guard present
### Verdict: [CONFIRMED/PARTIAL/NOT EXPLOITABLE]
**Reason:** [Why it works or doesn't]
**Evidence:** [Code references with line numbers]
### Next Steps (if confirmed)
- Severity: [High/Medium/Low]
- Want me to write a PoC?
- Want me to format as report?
If CONFIRMED:
If NOT EXPLOITABLE:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.