Evaluate bug bounty report submission readiness against platform-specific acceptance criteria.
npx skills add https://github.com/cuongnguyen-git/bug-bounty --skill triager
Please help me install this Agent Skill. Skill: triager Source: https://github.com/cuongnguyen-git/bug-bounty/tree/main/.claude/skills/triager Command: npx skills add https://github.com/cuongnguyen-git/bug-bounty --skill triager
This Skill helps you avoid wasting time and risking account reputation by evaluating whether a bug bounty report is truly reproducible, meaningful, and submission-ready.
Paste your bug bounty report draft and ask the triager to critique it, identify hard-stop reasons, and tell you what must be proven to submit.
High-intent search queries and answers about installing and using this skill.
Validating a bug bounty report requires checking for evidence-backed reproduction, non-speculative impact, and end-to-end impact-chain completeness. The triager Skill evaluates submission readiness by applying real triager skepticism and platform-specific acceptance criteria to your draft.
Yes, the triager applies platform-aware triage expectations. It enforces different credibility rules and thresholds for HackerOne, Bugcrowd, and Intigriti, including specific CVSS and remediation expectations for each platform.
Common hard-stop reasons for bug bounty reports include missing a working PoC, informational-only impact, speculative "could/might" chains, no attacker gain, or data that is already public. The triager blocks submissions when these critical issues are detected.
Checking an incomplete impact chain involves testing each prerequisite and evidence link end-to-end. The triager rejects theoretical or partially demonstrated chains and provides actionable rewrite guidance detailing exactly what evidence is missing.
Bug bounty reports get marked as informational or speculative when they lack non-speculative impact or fail sensitivity and public exposure checks. The triager identifies these specific hard-stop failures and tells you what must be proven before resubmitting.
ArianHobson333Automate HackerOne bug bounty workflows with parallel testing and report generation.
chrismcmackenTriage artifact scan results to surface reportable bug bounty findings.
RifteoAutomate vulnerability risk assessment using likelihood × impact, CIA triad, and CVSS correlation.
Pieverse-EngAssesses blockchain transactions for risks and assigns a verdict.
