create-investigation-report

Generates structured incident investigation reports from SOAR case data and security tool findings.

85|14|Updated May 17, 2025
One-click install
npx skills add https://github.com/dandye/adk_runbooks --skill create-investigation-report-dandye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-investigation-report
Source: https://github.com/dandye/adk_runbooks/tree/main/skills/reporting/create-investigation-report
Command: npx skills add https://github.com/dandye/adk_runbooks --skill create-investigation-report-dandye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After completing a security investigation, analysts must manually consolidate findings scattered across SIEM, SOAR, threat intelligence, and identity tools into a coherent report for stakeholders and post-incident review, which is time-consuming and error-prone. ## Core Features & Use Cases - Case Context Aggregation: Retrieves full SOAR case details, alerts, comments, and entities, then synthesizes findings from tools like Chronicle SIEM, Google Threat Intelligence, SCC, Okta, and CrowdStrike. - Structured Report Generation: Produces a Markdown report following standard templates with executive summary, timeline, entity enrichment, root cause analysis, and recommendations, plus a Mermaid sequence diagram of the actual investigation workflow. - Delivery & Documentation: Writes the report file, attempts SOAR case attachment with a comment fallback, and optionally uploads to Google Drive or GCS after analyst review and redaction of sensitive data. - Use Case: After triaging a phishing incident in a SOAR case, an analyst invokes this runbook to compile all enrichment findings into a redacted executive-ready report attached directly to the case. ## Quick Start Generate an investigation report for SOAR case 4821 summarizing all findings and attach it to the case.

Frequently Asked Questions about create-investigation-report

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

FAQPage Schema
How do I generate an incident investigation report from a SOAR case?▼

Provide the SOAR case ID as input. The runbook retrieves full case details, synthesizes findings from connected security tools, structures them into a Markdown report template, and attaches the result to the case or posts a fallback comment.

What security tools feed data into the investigation report?▼

The report summarizes findings from Chronicle SIEM (secops-mcp), Google Threat Intelligence, Security Command Center, Okta, and CrowdStrike, depending on which tools were used during the investigation. Only the SOAR case details and report-writing tools are strictly required.

What sections does the investigation report template include?▼

The report includes an executive summary, high-level investigation timeline, involved entities with enrichment summary, analysis or root cause, actions taken, and recommendations or lessons learned, following the reporting templates referenced in the rules-bank.

What happens if attaching the report to the SOAR case fails?▼

If the attachment tool is unavailable or fails, the runbook posts a comment to the SOAR case containing the report file path and a brief summary of findings, ensuring the case still documents the report's existence and location.

Does the report handle sensitive data before distribution?▼

Yes, the workflow includes a mandatory manual review step where the analyst confirms redaction or defanging of sensitive data such as PII, internal hostnames, and credentials before the final report is generated and distributed.

Can I upload the investigation report to Google Drive or GCS?▼

Yes, after report generation the runbook asks whether to upload the redacted file to Google Drive or GCS. If confirmed and the corresponding MCP tool is available, it uploads the file and documents the upload status in the SOAR case.