Agent skills
A skill is a single markdown file you give your AI agent once. It carries a complete compliance workflow — which gateway tools to call, in what order, with which arguments, and the grounding rules that make the output citable — so the agent applies it in every conversation without you pasting instructions. Skills are the packaged form of Instruct your agent: the same cite-or-refuse discipline, plus a task-specific method.
The files are free to download and licensed CC BY 4.0. Running them needs the gateway connector and an Ansvar account — the free plan is enough: both skills below use only tools available on every plan, and both were verified end-to-end on a free-tier connection before publication.
Available skills
CRA Vulnerability & Reporting Obligations
“What does the EU Cyber Resilience Act mean for our product — and what does this CVE trigger legally?”
- Determines CRA scope and product classification from the served regulation and implementing-act text, never from a category guess.
- Branches the duties by role — manufacturer, importer, distributor, open-source steward — and fetches the application and transitional dates before calling any duty live.
- Joins live CVE, CISA-KEV, and EPSS intelligence to the CRA's actively-exploited-vulnerability test, applied limb by limb.
- Walks the full Article 14 reporting ladder — early warning, notification, final report, user communications — quoting deadlines verbatim with their trigger events.
Get it: GitHub repository (canonical, with README and license) · SKILL.md (the file itself).
Incident Reporting Navigator (EU)
“We have an incident. Who must we notify, in which member state, and by when?”
- Screens one incident across NIS2, GDPR, DORA, and the CRA — per legal entity, with each entity's own roles and timestamps.
- Checks every duty was actually in force for the incident before reporting it, keyed to the duty's own trigger time.
- Resolves the receiving authority per regime and member state from served national law — Dutch, German, and other transpositions — or says plainly that the name is unresolved.
- Produces a deadline table in which every duty, authority, and date carries an official-publisher citation.
Get it: GitHub repository (canonical, with README and license) · SKILL.md (the file itself).
Install
Claude (claude.ai): Settings → Capabilities → Skills → upload the skill folder. Add the gateway under Settings → Connectors if you have not already:
https://gateway.ansvar.eu/mcpClaude Code: place the folder under .claude/skills/ in your project, with the gateway configured as an MCP server.
ChatGPT, Copilot, Gemini, and other MCP clients: attach SKILL.md as standing instructions for the conversation or project, with the gateway connected. Client-by-client connector setup is in Setup.
Why these are safe to rely on
- Nothing from model memory. Every legal claim the agent makes is fetched from official publisher text at answer time and cited with a source URL. Where the sources do not answer, the skill instructs the agent to say so — a connector failure is never converted into a legal conclusion.
- Reviewed before publication. Each skill went through a two-round adversarial legal-accuracy review with live EUR-Lex cross-checking before release.
- Re-verified nightly. The exact calls each skill instructs are pinned in the gateway's production verification battery and re-checked against the live service every night — if serving ever drifts from what a published skill expects, we find out before you do.