gather-evidence

Correlate code, infrastructure, and organizational signals into an incident evidence timeline.

13|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/unblocked/cookbook --skill gather-evidence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gather-evidence
Source: https://github.com/unblocked/cookbook/tree/main/recipes/gather-evidence
Command: npx skills add https://github.com/unblocked/cookbook --skill gather-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Evidence gathering that correlates signals from code, infrastructure, and organizational sources for an incident. Use when an alert, incident, or symptom needs cross-system evidence collection — building a correlation timeline, evaluating hypotheses against evidence, and presenting findings in plain language. Presents the evidence report to the user. Does not plan the investigation or implement fixes.

Core Features & Use Cases

  • Cross-system evidence gathering from code, infrastructure, and organizational sources.
  • Build a correlation timeline including last known good, changes, and first symptom.
  • Synthesize findings into plain-language conclusions with sources.
  • Generate a structured evidence report ready for review and sharing using references/evidence-template.md.

Quick Start

Initiate evidence gathering by aggregating code, infrastructure, and organizational signals to produce a consolidated incident report.

Frequently Asked Questions about gather-evidence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather evidence and correlate cross-system signals for an incident investigation?

Cross-system incident evidence gathering synthesizes signals from code, infrastructure, and organizational sources to produce a cohesive correlation timeline and plain-language findings report. It aggregates alerts and symptoms to identify the last known good state, changes, and first symptom.

What's the best way to build an incident timeline from forensic signals across multiple systems?

Building a forensic incident timeline involves correlating code, infrastructure, and organizational signals to map the sequence from last known good through changes to first symptom. This approach evaluates hypotheses against collected evidence and synthesizes conclusions in plain language with cited sources.

Can I use cross-system evidence collection for alerts that haven't escalated to full incidents?

Yes, cross-system evidence collection applies to incidents, alerts, or symptoms requiring investigation. It gathers signals, builds a correlation timeline, evaluates findings against hypotheses, and generates a structured report suitable for any level of operational alert or symptom.

How do I generate a structured incident report from correlated forensic evidence?

Generate a structured incident report by synthesizing gathered cross-system evidence into a cohesive timeline, evaluating hypotheses against the findings, and presenting plain-language conclusions with sources. The output follows a standardized evidence template ready for review and sharing.

Does evidence gathering and correlation plan the incident investigation or implement fixes?

No, evidence gathering and correlation does not plan the investigation or implement fixes. It strictly focuses on collecting cross-system signals, building a correlation timeline, evaluating findings, and presenting a structured report for downstream remediation.