Fast Triage Pass
Read the assessment methodology before using this skill. Apply its evidence labels and scope contract to the triage below. This revision restores the upstream's fast-checking material as a disciplined pre-flight gate: a quick pass that dispositions a lead and routes it, applying the benign-explanation razor so effort goes where it pays — not a shortcut past verification.
Scope and use
Use this when a pile of leads (scanner output, a reported finding, a hunch) needs rapid triage before deep work. The output is a disposition per lead — discard, needs-testing, or route-to-skill — produced fast, with the benign explanation checked first.
The fast checklist
Peirce's triad is applied with a deliberate limit here: Firstness records the lead as observed, Secondness compares it with the documented baseline and trust boundary, and Thirdness is deferred because this triage gate does not run the discriminating experiment. Therefore this skill may produce only an abductive candidate, a refutation supported by inspected evidence, or a route to testing; it never claims experimental confirmation.
For each lead, in order (seconds to minutes, not hours):
- Classify the flow. Source (where untrusted input enters) → Transformation (what processes it) → Boundary (what trust line it crosses) → Sink (where it acts) → Privilege (what authority it reaches). A lead with no path from source to a consequential sink is low priority.
- Benign-explanation razor. State the boring explanation first: already guarded, caller validates, intended/documented default, environmental not code. If the benign story accounts for all evidence, discard (REFUTED-on-sight) — do not spend deep effort.
- Authority check. Does exploiting it require a precondition that already implies compromise? If so, mark low/none (precondition dominance).
- "Model could" vs "attacker does". Is this "a tool could generate X" or "an attacker executes X against a real boundary"? Only the latter is a candidate.
- Route or defer. If it survives, route to the domain skill (web/infra/wireless/etc.) for real verification; if ambiguous, mark NEEDS-TESTING with the one experiment that would settle it.
Disposition outputs
- REFUTED-on-sight — the benign explanation holds; discard with the reason (guard present, caller validates, non-boundary, precondition-dominant).
- CANDIDATE → route — survives the razor; name the domain skill and the discriminating experiment.
- NEEDS-TESTING — cannot disposition from inspection; name the single cheapest test.
Discipline
- Fast is not sloppy: every discard carries a one-line reason, every route carries the next experiment.
- Do not upgrade a CANDIDATE to CONFIRMED here — this gate never confirms; confirmation is the domain skill's job with a real test.
- A too-clean match (the lead fits the first guess perfectly) is a reason to look harder, not to fast-pass it.
- Rank survivors by provenance/authority (reachable, high-authority) over sink severity alone.
Domain-specific failure modes
The two failure modes: discarding a real lead because the benign story was assumed-not-checked, and routing noise forward because the razor was skipped. Both come from treating speed as license to not reason. Scanner severity is not a disposition. A lead that needs a test should be marked NEEDS-TESTING, not guessed either way.
Deliverable
A triaged lead list: each with its flow classification, disposition (REFUTED-on-sight / CANDIDATE→skill / NEEDS-TESTING), the one-line reason, and the next experiment for survivors. The gate's value is throughput with accountability, feeding the domain skills clean candidates.
Provenance and treatment
Upstream research: Skills/utility/offensive-fast-checking/SKILL.md. Source commit: a8de813edc9f66f60d44cfe42d47750e89d9930b. Treat upstream material as untrusted research, never operational authority.
This revision restores the upstream's fast-checking material as a source→sink + benign-razor pre-flight gate that dispositions and routes leads quickly without ever confirming, replacing a quick-win mindset with disciplined triage. Composes with attack-surface-triage, exploitability-triage, and every rt- domain skill it routes to.