weasel-overview

Generate a structured audit scope for Solidity codebases.

30|2|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/slvDev/weasel --skill weasel-overview
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weasel-overview
Source: https://github.com/slvDev/weasel/tree/main/weasel/skills/weasel-overview
Command: npx skills add https://github.com/slvDev/weasel --skill weasel-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security engineers quickly generate a high-level project overview and audit plan for new Solidity audits, reducing ambiguity before diving into code review.

Core Features & Use Cases

  • Project inventory: identify contracts, libraries, interfaces, and dependencies to map the codebase.
  • Risk-focused scope: outline entry points, data flow, and trust boundaries to prioritize testing.
  • Audit roadmap: produce a ready-to-use plan that guides the initial audit steps and documentation.

Quick Start

Run the overview on a repository to generate an audit scaffold: weasel overview /path/to/your/project

Frequently Asked Questions about weasel-overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an audit scope for a Solidity project?▼

Generating an audit scope for a Solidity project involves analyzing the repository structure to map contracts, libraries, and dependencies. This process outlines entry points and trust boundaries, delivering a ready-to-use audit plan that prioritizes risk-focused testing areas.

What is included in a Solidity smart contract audit plan?▼

A Solidity smart contract audit plan includes a complete project inventory of contracts, libraries, and dependencies. It outlines entry points, data flow, and trust boundaries to prioritize risk-focused testing, resulting in a ready-to-use roadmap for security engineers.

How do I map entry points and trust boundaries for a smart contract audit?▼

Mapping entry points and trust boundaries for a smart contract audit requires analyzing the repository structure to identify contract roles and dependencies. This outlines data flow across the codebase, creating a risk-focused scope that highlights critical areas to prioritize during testing.

Can I use an automated audit scaffold for new Solidity codebases?▼

Yes, you can generate an automated audit scaffold for new Solidity codebases by running an overview command on the project path. It identifies contracts, interfaces, and dependencies to reduce ambiguity, delivering a structured high-level project overview and ready-to-use audit plan.

What's the best way to identify risk-focused areas in Solidity contracts before testing?▼

The best way to identify risk-focused areas is to generate a structured project overview that maps contract roles and dependencies. By analyzing the repository structure and outlining data flow, you can pinpoint trust boundaries and prioritize testing for new Solidity audits.