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 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/evidence-before-claimsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package9f690ca1…20b252d6
9f690ca1a610…30ab20b252d62 files · 4.4 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/behaviours/evidence-before-claims@21cd568
On this page
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.
Files in this version
references/15.6 KB
- offensive-evidence-gates.md5.6 KB
- SKILL.md5.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
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.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 9f690ca1 | Signed | – |
More from AeonDave
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk 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