Dedupe and rank Slither/Aderyn/Mythril/fuzz hits: (file, line), SWC, exploitability x funds, false positives, known issues. Use before writing a contest report.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add nuroctane/nur-cli --skill triaging-and-deduping-findings --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Triaging And Deduping Findings?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nuroctane-triaging-and-deduping-findings)More formats (shields.io, HTML) on the badges page.
---
name: triaging-and-deduping-findings
description: "Dedupe and rank Slither/Aderyn/Mythril/fuzz hits: (file, line), SWC, exploitability x funds, false positives, known issues. Use before writing a contest report."
---
# Triaging and deduping findings
A 200-line Slither dump is not research. This is the filter.
## Procedure
1. Combine Slither + Aderyn + Mythril + invariant failures + manual notes.
2. Key: `(file, function, root cause)` not every detector name.
3. Drop: informational, style, known issues from the contest README, issues in `lib/`.
4. Rank: exploitability x funds at risk. Critical/High block a deploy recommendation.
5. Map SWC + Solodit analog + bug class (`bug-classes.md`).
6. Require a local Foundry test for High/Critical. No test = not ready to file.
7. One report per root cause (`contest-and-bounty-reporting`).
PASS/FAIL for pre-deploy still lives on `auditing-foundry-smart-contract-security`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...