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 a
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reporting-triage-communicationWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package04f1070f…d5afdadb
04f1070f67f1…7819d5afdadb1 file · 1.5 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reporting/reporting-triage-communication@ee0e0c5
On this page
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
- 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.
- When asked for more: give precisely what's requested (a fresh repro, a video, the missing header), not a wall of text. Re-confirm from a clean state.
- Duplicate: ask politely for the dupe reference and compare — if yours is genuinely distinct (different root cause, endpoint, or a working chain where the original was theoretical), lay out the difference factually. If it's truly the same, accept it and move on.
- Not applicable / won't fix: restate the demonstrated impact and, if needed, escalate the PoC to show real consequence (stay in scope). Don't argue theory — show it.
- Severity dispute: bring the CVSS vector and the program's own scale (
reporting-cvss-scoring), and justify the contested metric with what you proved. - Escalate correctly: use the platform's mediation/escalation path when stuck; keep it factual.
Gotchas
- Never threaten public disclosure or go around the process — it voids safe harbor and burns you.
- Tone is leverage: rude threads get minimal effort; respectful, evidence-first threads get benefit of the doubt.
- Don't keep pushing a genuine dupe or a truly out-of-scope report — it costs goodwill you'll need later.
Verify success
The thread moves toward resolution on the merits: your follow-ups answered the actual question with evidence, and any dispute is argued from demonstrated impact and the program's own policy.
References
Platform mediation/disclosure guidelines; the reporting-bug-bounty-writeup, reporting-cvss-scoring,
and tradecraft-bugbounty-platforms skills.
Files in this version
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 04f1070f | Signed | – |
More from NoorQureshi
All from this publisherMore in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login