Individual skill

reporting-triage-communication

Work productively with triagers after you submit — answer follow-ups, and handle duplicate, not-applicable, or severity disputes professionally. Load on "triage asked for more info", "they closed it as N/A", "dispute the severity/duplicate", or managing a report thread. Signals: a submitted report awaiting/receiving triage, a disagreement on outcome.

skills/reporting/reporting-triage-communication/SKILL.md

Read pinned source

Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Oct 14, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
ai-security Repository topic
application-security Repository topic
blue-team Repository topic
bug-bounty Repository topic
claude-code Repository topic
codex Repository topic
detection-engineering Repository topic
gemini Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,881 bytes

Read excerpt


# Communicating with triage

## When it applies
The report is in and now it's a conversation. How you handle triage largely decides the outcome — a
valid bug can be closed over a bad thread, and a borderline one can be paid with a clear, calm one.

## Why it works
Triagers process a queue under time pressure and act on what's in front of them. A report that
reproduces from the steps alone, and follow-ups that answer the exact question with evidence, remove
every reason to close it — while professionalism keeps the relationship (and your reputation) intact.

## Method
1. **Pre-empt questions** in the report: exact requests/responses, account roles, a clean-session
   repro, and a crisp impact statement — most "need more info" rounds are avoidable.