evidence-before-claims
Evidence gate for security research, scanner triage, code review, and reporting. Use before confirming vulnerability impact, auth material, control results, cleanup, or root cause.
v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 11 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/evidence-before-claimsGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote9f690ca1…20b252d6
9f690ca1a610…30ab20b252d62 arquivos · 4.4 KBVarreduraBaixo1 achado
- Links para domínios externos
Fontegithub.com/AeonDave/malskill/tree/main/behaviours/evidence-before-claims@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
Use this skill when a conclusion could mislead an operator, reviewer, or report reader if it is overstated.
Activation triggers
- Reporting exploitability, vulnerability impact, credential validity, bypass success, persistence, or cleanup.
- Summarizing scanner output, fuzzing crashes, reverse-engineering findings, malware behavior, or OSINT pivots.
- Saying a bug is fixed, a target is safe, a false positive is dismissed, or a root cause is known.
Match evidence to the claim
Choose evidence that can establish the specific claim within authorized scope. Scale verification effort to the consequences and uncertainty; execution is not required for every fact.
- Observed behavior: a recorded action and result for the relevant environment. Repeat nondeterministic checks according to the uncertainty; a fixed number of passes does not prove reliability.
- Established from artifacts: inspected source, configuration, documents, logs, or other primary material supports the conclusion. Show the derivation and its conditions; distinguish documented or statically established behavior from behavior observed in a running target.
- Reported or hypothesized: attribute unchecked reports and label inferences with unresolved premises. An LLM/subagent summary alone is a lead, not confirmation.
Preserve provenance and context. Prefer searchable originals for textual evidence; screenshots can be primary evidence for visual behavior. A primary source establishes what it records, not automatically every claim its author makes.
Use corroboration to address a specific uncertainty. Check whether sources or methods share the same underlying report, signature, or failure mode; agreement alone is not independent confirmation.
Claim workflow
- State the claim and its scope: target, revision/configuration, and time window where relevant.
- Identify evidence that could falsify it or distinguish competing explanations.
- Inspect applicable evidence and its provenance. Separate observed facts, derived conclusions, and unresolved assumptions.
- Address material contradictory evidence; check for different states or conditions before choosing a conclusion. If unresolved, report the conflict.
- Preserve enough detail to check the result: source locator or command/input, relevant state, output, and limitations.
- Narrow the wording to what the evidence establishes; separate findings from recommendations.
Self-check before asserting
Before emitting a consequential conclusion, check its load-bearing assertions:
- Check that each load-bearing assertion has supporting material and that any derivation follows from it; plausibility alone is not evidence.
- For negative claims, check collection success, search coverage, permissions, and time range. No match supports only the examined scope; failed access or missing telemetry leaves the result unknown.
- Inspect the primary artifacts behind prior output or a subagent report; use
verification-before-completionfor freshness and rerun decisions.
Wording discipline
| Evidence state | Use wording like | Avoid |
|---|---|---|
| Reproduced now | confirmed, reproduced, observed | guaranteed, always |
| Established from inspected source | code establishes X under conditions Y | observed in production, dynamically reproduced |
| Strong but indirect | strongly indicates, consistent with | proven |
| Partial | supported within X; Y remains unverified | claims broader than the evidence |
| Unreviewed scanner finding | scanner reports, tool flagged | confirmed finding |
| Not checked | unverified lead | real issue |
| LLM/subagent summary only | reported by model/subagent, pending artifact review | found, confirmed |
Stop conditions
Do not expand access or authorization merely to verify a claim. If a needed check is outside the approved boundary, report that limitation and obtain the missing authorization before it; continue independent permitted work.
Output contract
For consequential findings, include the following information without requiring a separate template for every minor observation:
- Claim: the exact statement being made.
- Evidence: artifacts and commands used to support it.
- Limits: what was not tested or remains uncertain.
- Next verification, if uncertainty remains: the smallest authorized action that could resolve it, or the missing prerequisite.
Resources
Load on demand:
- references/offensive-evidence-gates.md — load when grading domain-specific research evidence, worker claims, or an engagement's final evidence summary.
Pair with verification-before-completion before claiming a task, fix, validation, or report is complete.
Arquivos desta versão
references/15.6 KB
- offensive-evidence-gates.md5.6 KB
- SKILL.md5.1 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 9f690ca1 | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Engenharia reversa e fuzzing
Ver a categoriaPergunte 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/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login