vulnerability-base

Name: vulnerability-base
Availability: InStock
Author: PurpleAILAB

Standardize smart contract vulnerability reporting with severity classification and quality checklists.

60|18|Updated Jan 21, 2026

Search Tags:#security #vulnerability #auditing #reporting #blockchain #smart contract

Ready to run

npx skills add https://github.com/PurpleAILAB/Vigilo --skill vulnerability-base

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vulnerability-base
Source: https://github.com/PurpleAILAB/Vigilo/tree/main/packages/claude/skills/vulnerability-base
Command: npx skills add https://github.com/PurpleAILAB/Vigilo --skill vulnerability-base

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes a universal standard for reporting smart contract vulnerabilities, ensuring consistency, clarity, and actionable information across all auditors.

Core Features & Use Cases

Standardized Reporting: Enforces strict rules for evidence, attack scenarios, and impact descriptions.
Severity Classification: Provides clear criteria for categorizing vulnerabilities (High, Medium, Low).
Quality Assurance: Includes a checklist to ensure all critical reporting elements are present.
Use Case: An auditor discovers a reentrancy vulnerability. This Skill guides them to document the exact code location, provide a step-by-step attack scenario without PoC code, and classify the severity according to defined standards.

Quick Start

Use the vulnerability-base skill to document a newly found reentrancy vulnerability in the 'withdraw' function of 'Vault.sol'.

Frequently Asked Questions about vulnerability-base

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

FAQPage Schema

How do I standardize smart contract vulnerability reporting for consistent auditing?▼

Severity classification for smart contract vulnerabilities categorizes findings into High, Medium, and Low tiers based on defined criteria, ensuring consistent impact assessment across all security audits.

What should a smart contract attack scenario report include without proof of concept code?▼

A smart contract attack scenario report should include the exact code location and a step-by-step description of the exploit without requiring proof of concept code, alongside a strict impact assessment.

Can I document reentrancy vulnerabilities using a standardized reporting framework?▼

Yes, you can document reentrancy vulnerabilities by identifying the exact code location, providing a step-by-step attack scenario, and classifying the severity according to standardized smart contract auditing criteria.

Does smart contract vulnerability auditing require specific output formats for findings?▼

Smart contract vulnerability auditing requires adherence to specific output formats for findings, attack scenarios, and PoC validation to maintain consistency and actionable information across auditors.