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 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reporting-triage-communicationEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete04f1070f…d5afdadb
04f1070f67f1…7819d5afdadb1 archivo · 1.5 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/reporting/reporting-triage-communication@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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.
Archivos de esta versión
- SKILL.md2.8 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 04f1070f | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Informes y cumplimiento
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login