- Home
- Skills
- Legal & Compliance
- Compliance Snapshot — NIS2, GDPR, ISO 27001, SOC 2, AI Act
Works with the AI Agents you already use
Compliance Snapshot — NIS2, GDPR, ISO 27001, SOC 2, AI Act
Compliance Snapshot is five framework skills and a combined run on one shared core.
$39
Compliance Snapshot — NIS2, GDPR, ISO 27001, SOC 2, AI Act
Example session with this skill installed
compliance snapshot --export-report --drafts
- Read your context and instructions
- Compiled the compliance snapshot
A redacted excerpt from a real run on an open-source Python MCP browser agent, from the repository alone with no documents folder:
| Framework | Covered | Partial | Gap | Not verifiable | Not applicable | % |
| NIS2 | 0 | 2 | 11 | 2 | 0 | 0% |
| GDPR | 0 | 4 | 11 | 3 | 0 | 0% |
| ISO 27001 | 0 | 14 | 50 | 29 | 0 | 0% |
| SOC 2 | 0 | 7 | 22 | 9 | 0 | 0% |
| AI Act | 0 | 2 | 0 | 1 | 9 | 0% |
gaps: 15 HIGH, 108 MEDIUM, 0 LOW
CTL-IR-02 gap HIGH
Affects: NIS2 23(1); NIS2 23(4)(a); GDPR 33(1); ISO A.5.26; SOC2 CC7.4 (10 in all)
Gap: No notification step, deadline or authority or CSIRT contact found
Fix: Add to the runbook, for early warning (24 h), incident notification (72 h),
final report (one month) and GDPR breach notice (72 h): deadline, clock start,
sender, recipient and contents
CTL-VUL-01 gap MEDIUM
Affects: NIS2 21(2)(e); GDPR 32(1)(d); ISO A.8.8; SOC2 CC7.1 (10 in all)
Gap: uv.lock pins dependencies, but pyproject.toml:7 takes one library from the
moving branch main, and there is no update bot, no CI dependency audit and no
fix-deadline procedure
Fix: Add dependabot.yml or renovate.json and a pip-audit or osv-scanner step in CI,
pin the library to a tag or commit, and state fix deadlines by severity
Connects securely to your tools. The creator never sees your data.
About this skill
Compliance Snapshot is five framework skills and a combined run on one shared core. Ask for "a compliance snapshot" or "are we ready for an audit" and the agent checks all five in one pass. Ask for one ("GDPR readiness", "ISO 27001 gap analysis") and a router sends you to that skill alone. Each control is checked once and reused across every framework it touches.
| Skill | What it checks |
|---|---|
| nis2 | The Art. 21(2) security measures and the Art. 23 notification steps (24 h early warning, 72 h notification, one-month final report) |
| gdpr | Security, accountability and processor duties (Art. 5, 25, 28, 30, 32, 33), for controllers, processors or both |
| iso27001 | All 93 Annex A controls of ISO/IEC 27001:2022 |
| soc2 | Trust Services Criteria: security, plus availability and confidentiality when in scope |
| ai-act | Finds the AI systems in the code, sets a risk class with reasons, and checks the articles that class brings |
| compliance-snapshot | All five in one pass, with a summary table and a cross-framework gap list |
What sets it apart:
- Evidence per requirement. Each requirement cites the file and line, or the document and section, that supports its status. Quotes are short, and secrets and personal data are redacted.
- Five statuses, no invented coverage. Covered, partial, gap, not verifiable, not applicable. A requirement with no evidence is a gap. One that needs records a repository cannot hold (HR screening, management review, physical security) is not verifiable, never covered.
- Severity you can act on. HIGH for a NIS2, GDPR or AI Act obligation with no technical or documentary evidence at all, LOW for a gap where the technical side is in place and only written policy or records are missing, MEDIUM for the rest. Each gap comes with a concrete fix.
- Your documents count. Point
--docsat a folder of policies, runbooks and records. The snapshot reads them, cites the section, and flags where a policy says one thing and the code another. - Full Audit Pack bridge. If a Full Audit Pack run left findings in
.audit/, they feed the matching controls as gaps or partials. They are never treated as proof of coverage, and a stale store is called out. - Drafts to start from.
--draftswrites the NIS2 Art. 21 measures table, GDPR processor terms and records of processing, an ISO 27001 Statement of Applicability, SOC 2 control descriptions and an AI Act classification note, filled from evidence and markedTO COMPLETEwhere the company must decide. - Run memory and CI. Gaps are fingerprinted in
.compliance/, so the next run shows what is new, recurring and fixed.--ciprints JSON and exits 0, 1 or 2 by severity.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Legal & Compliance.
Readiness snapshot, not a certification or legal opinion. It reads your repository and documents and never checks live systems, cloud accounts or running infrastructure. Organisational controls (HR, physical security, management review) can only be settled from documents you supply. The ISO 27001 mapping was checked against the official text; the SOC 2 mapping was checked against a vendor guide and the AICPA criterion ids, not the AICPA text. Statuses come from an agent's judgement on the evidence it cites, so review them before relying on them.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed today
Nothing to install. It runs in your AI agent.
- Optional
- Bash, jq and perl (run memory)
Without Bash, jq or perl the snapshot still finishes; only run memory (new, recurring and fixed gaps between runs) is skipped.
Permissions
File Scopes
Reads the repository you check and the --docs folder. Writes only under .compliance/ (profile and run memory) and docs/compliance/ (reports, matrices and drafts). No network calls and no install scripts. The shell runs the run-memory script (Bash, jq, perl).