Sponsor Suno AI Music arrow_forward
Slash Command

Severity Classify

Classify an issue, finding, or vulnerability by severity level (S1-S4)

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What Severity Classify is

Severity Classify is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Severity Classify gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Severity Classify

Claude Code

  1. Download severity-classify.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/security/severity1-marketplace/commands/severity-classify.md, shared under the repository's MIT license. Read the full file on GitHub.

Analyze the provided issue, bug report, or security finding and assign an appropriate severity level.

Severity Levels

S1 — Critical

  • System completely down or unusable
  • Active data loss or corruption
  • Security breach with confirmed exploitation
  • No workaround available
  • Response time: Immediate

S2 — High

  • Major functionality broken for many users
  • Security vulnerability with high exploitability
  • Data integrity at risk
  • Workaround exists but is impractical
  • Response time: Within 4 hours

S3 — Medium

  • Functionality degraded but operational
  • Security issue with limited scope
  • Reasonable workaround available
  • Affects subset of users or use cases
  • Response time: Within 24 hours

S4 — Low

  • Minor issue or cosmetic defect
  • Enhancement request
  • Documentation improvement
  • Edge case with minimal impact
  • Response time: Backlog

Classification Process

  1. Read the issue — Understand the full context of the report
  2. Assess impact — Determine scope, affected users, and business impact
  3. Evaluate exploitability — For security issues, assess ease of exploitation
  4. Check for workarounds — Determine if users can work around the issue
  5. Assign severity — Apply the appropriate S1-S4 level
  6. Provide rationale — Explain the classification with supporting evidence

Output Format

## Severity: S[1-4] — [Critical|High|Medium|Low]

**Impact:** [Description of impact]
**Scope:** [How many users/systems affected]
**Workaround:** [Available|None|Impractical]
**Rationale:** [Why this severity was assigned]

### Recommended Actions
1. [First action]
2. [Second action]

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Severity Classify?

Severity Classify is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Classify an issue, finding, or vulnerability by severity level (S1-S4)

How do I install Severity Classify in Claude Code?

Download severity-classify.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Severity Classify in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Severity Classify safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.