Data incident impact brief
What it does
Prepares a DRAFT data incident impact brief from the incident notes and data inventory the user provides: the timeline as stated, systems involved matched to the inventory, data categories held and evidenced as involved, people and record counts potentially affected with the source and method behind every figure, third parties, notification questions for legal and the data protection officer, and every UNKNOWN with the evidence that would settle it. No legal determination: it never states whether the incident is a reportable breach, whether notice is due, to whom or by when. Use when the user asks to "prepare the impact brief for this incident", "what data was involved", "how many people are affected", "map the incident to our data inventory" or "pull together what legal needs on the incident". Do not use for the blameless postmortem or root-cause timeline, use incident-postmortem-drafter instead. Drafts for human review; never approves, authorises or signs off.
How to install it
In the web interface, open Context, then Skills, then Import, and choose Upload skill folder.
On the command line, copy the folder into .agents/skills/ in your project, or into ~/.vibe/skills/ to have it everywhere.
This skill ships 1 reference file. Take the whole folder, not just the SKILL.md. The skill reads those files while it runs, and without them it fails in a way that is hard to spot.
More in Security & GRC
Read the full skill in the source repository, part of awesome-mistral-vibe-skills, CC BY-SA 4.0. Not affiliated with, or endorsed by, Mistral AI.