weasel-report | weasel | ClaudePluginHub

Skill

Community

weasel-report

5

Description

Audit report writing for smart contract vulnerabilities. Triggers on weasel report, weasel write up, or weasel document.

Install

1

Add the repository(one-time)

$

/plugin marketplace add slvDev/weasel

2

Install the plugin

$

/plugin install weasel@weasel

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Weasel Report Writer

Expert in formatting security findings as professional audit reports.

When to Activate

User wants to document a vulnerability
User asks to write up a finding
User wants to format for submission

Process

Gather info - What's the vuln? Which contract/function? Severity?
Read code - Get exact lines and context
Format report - Use template below
PoC decision - Auto-include if High severity or already written

Do NOT run Weasel analysis - user already found the bug!

Report Template

## [SEVERITY-XX] Title That Describes The Impact

### Summary
One sentence: what's broken and what's the impact.

### Vulnerability Detail
- What the vulnerability is
- How it occurs
- Why it's a problem

### Impact
What an attacker can achieve (fund loss, DoS, corruption).

### Code Snippet

`path/to/file.sol#L123-L130`

\`\`\`solidity
function withdraw(uint256 amount) external {
    (bool success, ) = msg.sender.call{value: amount}(""); // @audit reentrancy
    balances[msg.sender] -= amount;
}
\`\`\`

### Recommendation

\`\`\`solidity
function withdraw(uint256 amount) external nonReentrant {
    balances[msg.sender] -= amount;
    (bool success, ) = msg.sender.call{value: amount}("");
}
\`\`\`

### PoC (omit if none)
See: test/Contract.t.sol::test_VulnName_PoC

Title Conventions

Good: Specific, describes impact

"Reentrancy in withdraw() allows draining of user funds"
"Missing access control on setFee() allows anyone to set 100% fee"

Bad: Vague

"Reentrancy vulnerability"
"Access control issue"

Multiple Findings

Number by severity: H-01, H-02, M-01, M-02, etc. Order: severity first, then by location.

Links

GitHub Stats

0 forks

Updated 18 hours ago

Similar Skills

Command Development

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.

54.7k

Agent Development

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.

54.7k

Hook Development

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.

54.7k