feedback

Classify HackerOne analyst responses and route them to triage handlers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AshtonVaughan/bountyhound --skill feedback-ashtonvaughan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback
Source: https://github.com/AshtonVaughan/bountyhound/tree/main/bountyhound/skills/feedback
Command: npx skills add https://github.com/AshtonVaughan/bountyhound --skill feedback-ashtonvaughan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handle HackerOne analyst responses by classifying feedback type and triggering the corresponding action to close or progress the ticket.

Core Features & Use Cases

  • Classification: automatically categorize analyst messages into one of six types (Needs More Info, Severity Downgrade, Duplicate, Informative, N/A, Resolved) to drive next steps.
  • Gate-driven routing: apply the appropriate protocol (NMI Procedure, Severity Appeal, Duplicate Handler, Informative Handler, or N/A Handler) based on the classification.
  • Context tracking: maintain a running narrative in context.md and log decisions to support audit trails and future reports.
  • Use Case: for a response stating "Duplicate of #12345", route to the Duplicate Handler and request the duplicate ID for confirmation.

Quick Start

Classify the analyst message and route it to the appropriate handler according to the Feedback Response Protocol.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I automate HackerOne bug bounty triage for analyst responses?

Automate HackerOne bug bounty triage by classifying analyst responses into defined categories and triggering structured routing protocols to close or progress tickets consistently. This workflow handles response types like Needs More Info, Duplicate, and Resolved.

What is the best way to handle a HackerOne severity downgrade appeal?

Handle a HackerOne severity downgrade appeal by routing the analyst response to a dedicated Severity Appeal protocol, which applies structured templates to produce consistent responses and logs the decision in context.md for audit trails.

Can I use structured gates to classify duplicate reports on HackerOne?

Yes, you can classify duplicate reports using gate-driven routing protocols. When an analyst message indicates a duplicate, the workflow routes it to a Duplicate Handler to request the duplicate ID and confirm the classification.

How do I maintain context when managing HackerOne feedback across multiple tickets?

Maintain context by logging triage decisions and routing actions in a running context.md file, ensuring a persistent narrative that supports audit trails, preserves response history, and informs future bug bounty reports.

Does this workflow support handling Informative or N/A HackerOne responses?

Yes, this workflow supports Informative and N/A responses by applying dedicated handler protocols that trigger the appropriate triage actions, ensuring consistent ticket progression and structured routing for authorized bug bounty engagements.