privacy-incident-agent

Structure privacy-incident information into chronology, impact framing, and containment status.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/harkers/forge-email-server --skill privacy-incident-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: privacy-incident-agent
Source: https://github.com/harkers/forge-email-server/tree/main/skills/privacy-incident-agent
Command: npx skills add https://github.com/harkers/forge-email-server --skill privacy-incident-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Privacy incidents require structured analysis to avoid misstatements and ensure consistent documentation. This Skill helps build a reliable incident chronology, frame likely impact and exposure, summarize containment and recovery status, and identify open questions that block timely notification decisions, while supporting manager reviews with evidence-backed outputs.

Core Features & Use Cases

  • build incident chronology
  • frame likely impact and exposure
  • summarise containment and recovery status
  • identify open questions that block notification decisions
  • support manager review with structured incident outputs
  • evidence-backed incident drafting for documentation and audit trails

Quick Start

Provide a structured incident report for a privacy breach using available data and references.

Frequently Asked Questions about privacy-incident-agent

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

FAQPage Schema
How do I structure a privacy incident chronology for compliance documentation?

Build a privacy incident chronology by inputting raw incident data to generate a structured timeline, impact framing, and containment status. This separates facts from assumptions to produce deterministic outputs for audit trails and notification planning.

What is the best way to frame the impact and exposure of a suspected data breach?

Frame data breach impact by analyzing incident details to summarize likely exposure and recovery status. This structured method identifies open questions blocking notification decisions and supports manager reviews with evidence-backed outputs.

Can I use this for suspected privacy breaches and data-handling failures?

Yes, you can use it for suspected privacy breaches and data-handling failures. It structures incident information into chronologies and impact framings, handling both confirmed and suspected incidents with structured outputs for investigations.

How do I identify open questions that block privacy incident notification decisions?

Identify blocking open questions by structuring incident analysis to highlight information gaps in the chronology and containment status. This process surfaces unresolved factors preventing timely notification decisions and escalation recommendations.

Does this incident analysis approach separate facts from assumptions for manager review?

Yes, this incident analysis approach explicitly separates facts from assumptions. It generates deterministic outputs and escalation recommendations, providing structured incident documentation that supports manager reviews with evidence-backed results.

When do I need structured incident documentation for privacy forensics?

You need structured incident documentation when managing privacy forensics, investigations, and notification planning. It ensures consistent analysis of suspected breaches, providing evidence-backed drafting for audit trails and deterministic escalation recommendations.