weasel-report

Format confirmed smart contract vulnerabilities into standardized Markdown audit reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill formats security findings into professional audit reports, saving auditors time and ensuring consistency across engagements.

Core Features & Use Cases

  • Structured Reporting: Converts vulnerability findings into standardized Markdown reports ready for submission and review.
  • Contextual Detailing: Ingests function names, code references, and severity to provide precise, actionable narratives.
  • Use Case: When a vulnerability is confirmed, generate a complete audit report artifact that can be archived or submitted to the client.

Quick Start

Use the weasel-report skill after you have a confirmed vulnerability from the analyzer. It will create a properly formatted audit report and place it under the findings/ directory for review and submission.

Frequently Asked Questions about weasel-report

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

FAQPage Schema
How do I format smart contract vulnerability findings into a Markdown audit report?

To format smart contract vulnerability findings into a Markdown audit report, use a reporting tool that ingests confirmed vulnerabilities, function names, and code references to generate a standardized Markdown artifact.

What information do I need to generate a professional smart contract security audit report?

Generating a professional smart contract security audit report requires confirmed vulnerability context, including specific function names, code references, and severity levels, to ensure precise and actionable reporting narratives.

Can I automatically create submission-ready Markdown reports for confirmed smart contract vulnerabilities?

Yes, you can automatically create submission-ready Markdown reports for confirmed smart contract vulnerabilities, which are placed in a findings directory for archiving or client submission.

When should I use a dedicated audit reporting tool for smart contract security findings?

You should use a dedicated audit reporting tool for smart contract security findings when you have confirmed vulnerabilities from analyzers and need to enforce adherence to a specific project reporting template.

Does the audit reporting process enforce a specific project template for Markdown output?

Yes, the audit reporting process enforces adherence to the project's reporting template, ensuring standardized Markdown output suitable for professional review and client submission.