mtarcure/claude-vibe-squad/review-severity-ladder
Claude Code and agent skill by mtarcure/claude-vibe-squad
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Use when you need severity to mean the same thing across reviewers, specialists, and models — place each finding on one shared critical/high/medium/low/note rung by consequence rather than fix effort, keep severity separate from confidence, and declare the deliverable's reporting floor.
Install
npx vskill@latest install mtarcure/claude-vibe-squad/review-severity-ladderSKILL.md
Review Severity Ladder
Rank findings on one shared ladder so severity means the same thing across reviewers, specialists, and models.
Steps
- Place each finding on the ladder by consequence, not by effort to fix and not by how interesting it is:
- critical — data loss, credential exposure, unauthorized state change, or silent corruption reachable on a normal path.
- high — wrong results, broken invariant, or availability loss on a reachable path; correct behavior depends on luck.
- medium — wrong behavior on an edge, boundary, or error path; degraded but recoverable.
- low — quality, clarity, or duplication that will cause a future defect but causes none now.
- note — observation with no defect claim.
- Justify each placement with the consequence and the path that reaches it. "Could be a problem" is not a placement.
- Apply the reachability test before assigning critical or high: name the entry point, the actor, and the input that gets there. Unreachable code caps at medium.
- Apply the intrinsic-impact test: a finding that only reveals information already disclosed, or that requires privileges the attacker would not have, does not clear high.
- Separate severity from confidence. A high-severity finding you are unsure of is
high / unconfirmed— never demote severity to express doubt, and never inflate confidence to justify severity. - Set a severity floor for the deliverable and report everything at or above it; list the rest as notes rather than discarding them.
- When the ladder produces repeated critical findings on the same mechanism, the correct move is to remove or bound the mechanism, not to keep escalating the threat model.
Acceptance
- Every finding carries exactly one rung and a one-line consequence statement.
- Critical and high findings name entry point, actor, and reaching input.
- Severity and confidence are recorded as separate fields.
- The deliverable states its severity floor.
- Placements are defensible without reference to how hard the fix is.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingmodel-lanes/gemini/.agents/skills/review-severity-ladder/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/mtarcure/claude-vibe-squad/review-severity-ladder)