Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
noorqureshi/reporting-triage-communicationRelatórios e compliance

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 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/reporting-triage-communication

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
W/rg/PG6MM…IBkA5nAg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote04f1070f…d5afdadb
04f1070f67f1…7819d5afdadb1 arquivo · ⁦1.5 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/reporting/reporting-triage-communication@ee0e0c5

Este item ainda não foi escrito no seu idioma, então aparece em English.

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.
  2. 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.
  3. 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.
  4. 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.
  5. Severity dispute: bring the CVSS vector and the program's own scale (reporting-cvss-scoring), and justify the contested metric with what you proved.
  6. 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.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.10.14-ee0e0c513 de nov. de 2026ee0e0c504f1070fAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login