severity-classification

Classify smart contract vulnerability severity using an impact-versus-likelihood rubric.

1|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Apegurus/solidity-argus --skill severity-classification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: severity-classification
Source: https://github.com/Apegurus/solidity-argus/tree/main/skills/methodology/severity-classification
Command: npx skills add https://github.com/Apegurus/solidity-argus --skill severity-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized framework for classifying the severity of security vulnerabilities found in Solidity smart contracts, ensuring consistent and professional reporting.

Core Features & Use Cases

  • Impact-Versus-Likelihood Rubric: Clearly defines severity based on the intersection of potential impact and the likelihood of exploitation.
  • Detailed Severity Levels: Provides specific criteria and examples for Critical, High, Medium, Low, and Informational findings.
  • Industry Standard Comparison: Aligns classifications with common standards used in the blockchain security community (Code4rena, Sherlock, Immunefi).
  • Use Case: After an automated scan identifies a potential reentrancy vulnerability, this Skill helps determine if it's a Critical issue (direct fund drain) or a Medium issue (conditional fund loss), guiding the auditor's reporting and remediation efforts.

Quick Start

Use the severity-classification skill to determine the severity of a reentrancy vulnerability.

Frequently Asked Questions about severity-classification

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

FAQPage Schema
How do I classify the severity of a smart contract vulnerability?

Smart contract vulnerability severity is classified by evaluating the intersection of potential impact and exploitation likelihood. This rubric defines Critical, High, Medium, Low, and Informational levels to standardize security audit reporting and risk assessment.

What is the difference between a Critical and High severity finding in a Solidity audit?

A Critical severity finding typically involves direct fund loss, such as a direct fund drain, whereas a High severity finding involves conditional or indirect asset loss. Severity levels are defined by specific criteria illustrating the exact impact and likelihood of the vulnerability.

Does this vulnerability severity classification align with industry standards like Code4rena and Immunefi?

This vulnerability classification aligns with common industry standards used by the blockchain security community, including Code4rena, Sherlock, and Immunefi. It facilitates consistent security audit reporting by mirroring established framework criteria.

How do I determine if a reentrancy vulnerability is a Medium or Critical issue?

To determine if a reentrancy vulnerability is a Medium or Critical issue, evaluate the specific impact and likelihood. A Critical issue involves a direct fund drain, while a Medium issue involves conditional fund loss, guiding remediation efforts accurately.

When do I need to use a severity classification rubric for security audit reporting?

You need a severity classification rubric for security audit reporting after identifying vulnerabilities, such as through automated scans. It provides a standardized framework to determine risk levels and ensures professional, consistent reporting for remediation.