Incident Reporting Navigator

Use when a security incident, data breach, or actively exploited vulnerability raises the question "who must we notify, where, and by when?" Screens one incident across the EU reporting regimes — NIS2, GDPR, DORA, and the Cyber Resilience Act — determines which duties fire for each involved entity's roles, resolves the receiving authority per regime and member state from served national law, and produces a deadline table in which every duty, authority, and deadline is cited from official publisher text fetched live through the Ansvar Gateway MCP connector. Never answers from model memory.

1 starsSecurity

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Ansvar-Systems/incident-reporting-navigator-skill --skill incident-reporting-navigator
Manual install
git clone --depth 1 https://github.com/Ansvar-Systems/incident-reporting-navigator-skill.git /tmp/incident-reporting-navigator-skill
mkdir -p ~/.claude/skills
cp -r /tmp/incident-reporting-navigator-skill/. ~/.claude/skills/incident-reporting-navigator

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Incident Reporting Navigator (EU)

One security event can trigger several EU reporting regimes at once, each
with its own trigger test, receiving authority, and clock. Given the
incident facts and the organisation's profile, produce a cited notification
map: which regimes fire for which legal entity, which do not and why, which
authority receives each notification in which member state, and every
deadline as the served legal text states it. This skill determines *what
must be reported to whom and by when*; it does not draft the notifications
themselves.

## Requirements

- The **Ansvar Gateway** MCP connector must be connected:
  `https://gateway.ansvar.eu/mcp` (OAuth 2.1 with Dynamic Client
  Registration; free plan signup at https://ansvar.eu). Works in Claude,
  ChatGPT, Copilot, Gemini, and any MCP-capable agent.
- Tools this skill uses: `search`, `get_provision`, `get_my_capabilities` —
  and, when a CVE is involved and the user consents to transmitting its id,
  `get_cve_details` and `check_kev_status`. All are available on every
  plan, including Free (lower quotas; one jurisdiction-or-framework scope
  per search call).
- If these tools are not available, stop and tell the user to connect the
  gateway. Do not answer from model knowledge.

## Ground rules (non-negotiable)

1. **Answer only from tool results.** If the fetched rows do not contain
   the answer, say which searches you ran and that you will not answer from
Read the full skill on GitHub

Details

Skill name
incident-reporting-navigator
Repository
Ansvar-Systems/incident-reporting-navigator-skill
Repo updated
27 July 2026
Listed in
karanb192/awesome-claude-skills

FAQ

What does the Incident Reporting Navigator skill do?

Use when a security incident, data breach, or actively exploited vulnerability raises the question "who must we notify, where, and by when?" Screens one incident across the EU reporting regimes — NIS2, GDPR, DORA, and the Cyber Resilience Act — determines which duties fire for each involved entity's roles, resolves the receiving authority per regime and member state from served national law, and produces a deadline table in which every duty, authority, and deadline is cited from official publisher text fetched live through the Ansvar Gateway MCP connector. Never answers from model memory.

How do I install the Incident Reporting Navigator skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Ansvar-Systems/incident-reporting-navigator-skill --skill incident-reporting-navigator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Incident Reporting Navigator popular?

It lives in Ansvar-Systems/incident-reporting-navigator-skill, which has 1 GitHub stars and 0 forks, and is included in 1 curated skill list.

Related skills

Regulatory Threat Model

1

Ansvar-Systems/regulatory-threat-model-skill

Use when an application or system — including one built quickly with AI coding agents — needs a security review with regulatory grounding: a STRIDE threat model, a LINDDUN privacy threat model, a dependency exposure screen against live CVE / CISA-KEV / EPSS data, or a selected, non-exhaustive screen of which EU security obligations (GDPR, NIS2, Cyber Resilience Act, AI Act) may apply and which need determination. Orchestrates the server-enforced threat-modeling workflows of the Ansvar Gateway MCP connector and grounds every regulatory statement in officially published text fetched at answer ti

SecurityIn 1 list

Deep Security Check

2

give-jd/deep-security-check

Use when the user asks for a defensive security assessment, security audit, vulnerability scan, or "how safe / how reliable is this code/project/repo". Runs Semgrep (SAST), osv-scanner (dependency CVEs) and gitleaks (secrets) against a local project, then produces a report with a reproducible reliability grade (0-100, A-F). Defensive only — finds weaknesses in code you own; it does not exploit, attack, or test remote targets.

SecurityIn 1 list

Awesome Bug Bounty

YangTech-gh/Awesome-Bug-Bounty

Use when doing bug bounty hunting, vulnerability research, security report writing/analysis, payload or WAF-bypass selection, business logic / IDOR / race / API testing, recon methodology, tool choice (Burp vs Caido vs ZAP, AI pentest agents, MCP security testing, headless browsers), or looking up writeups/programs — e.g. "find XSS payload", "business logic checklist", "SSRF bypass", "HackerOne top reports", "bug bounty methodology", "which tools to install". Merges curated knowledge with source-repo fallbacks; authorized testing only.

SecurityIn 1 list

Deep Security Audit

3

ravindrakele/claude-skills

Deep, multi-agent security audit of a codebase — WordPress plugin, Laravel, Next.js, Node/Express, Django/Rails, or any app. Detects the framework, maps the REAL attack surface (routes, handlers, auth, sinks), then fans out scoped finder agents that READ and understand the code (not just grep), adversarially verifies every finding (proves the guard is genuinely absent + traces reachability), scores honest CVSS 3.1, dedupes, and produces a ranked report. Use whenever the user asks to find security issues / vulnerabilities, run a security audit or pentest, "is this secure", "scan this plugin/app

SecurityIn 1 list

Cra Vulnerability Obligations

Ansvar-Systems/cra-vulnerability-obligations-skill

Use when a user asks what the EU Cyber Resilience Act (CRA) means for their product, whether and when they must report a vulnerability or incident, or what a specific CVE triggers legally. Maps a product with digital elements to CRA scope, product classification, Annex I vulnerability-handling duties, and Article 14 reporting obligations — every legal claim cited from official regulation text fetched live through the Ansvar Gateway MCP connector, joined with live CVE / CISA-KEV / EPSS vulnerability intelligence from the same connector.

SecurityIn 1 list

Web Security Reviewer

5

goingli0324/web-security-reviewer

對使用者自己的程式碼做防禦性安全審查，檢測資安漏洞、資料外洩風險、壓力／效能風險與程式品質，並產出「依嚴重度排序的風險報告 ＋ 修正後程式碼」。涵蓋 Google Apps Script（Workspace 自動化）、前端 HTML/CSS/JS、後端 API（Node/Python/PHP 等）。特別適用於「使用者用 AI 生成 / vibe coding 寫出來、希望更安全、避免被攻擊或破壞」的網頁程式碼。MANDATORY TRIGGERS：使用者要求「檢測程式碼安全」「幫我看這段 code 有沒有漏洞」「防止資料外洩」「review 我的網頁／後端程式」「這段會不會被攻擊／被駭」「加固 / harden」「壓力測試」「優化程式碼安全性」「個資會不會外洩」「這是 AI 寫的幫我看安不安全」，或貼上一段前端／後端／Apps Script 程式碼並要求審查、找漏洞、修正建議、加固時，都要套用此 skill。即使使用者沒明說「資安」，只要意圖是審查或加固自己的程式碼，就觸發。SCOPE：本 skill 僅用於防禦性檢測——找出並修補使用者自己程式碼裡的漏洞；不協助撰寫可直接攻擊用的 exploit、不協助繞過資安機制。本 skill 同時是 agentic-dev-loop「Verify 雙閘」的安全閘：當該編排器要在部署前驗證安全／個資時會呼叫本 skill；使用者單獨要求安全審

Security

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.