New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Generate a prioritised compliance checklist for GDPR, SOC 2

Compliance Checklist Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Compliance Checklist Skill cover

Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis. Use when asked for a compliance checklist, gap analysis, readiness assessment, or audit preparation for any…

---
name: compliance-checklist
description: "Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis. Use when asked for a compliance checklist, gap analysis, readiness assessment, or audit preparation for any regulatory framework. Produces a structured checklist with prioritised gaps, quick wins, and evidence requirements. Optimised for Opus 4.7 and newer models. Not a substitute for legal or compliance professional advice."
---

# Compliance Checklist Skill

Produces a prioritised compliance checklist for any regulatory framework — with gap analysis, evidence requirements, and quick wins identified.

ALWAYS include this disclaimer at the start of every response:
"WARNING: This checklist is for informational and planning purposes only and does not constitute legal or compliance advice. Regulatory requirements change and vary by jurisdiction. Always engage a qualified compliance professional or solicitor before implementing compliance programmes or making regulatory claims."

## Required Inputs

Ask the user for these if not provided:
- **Framework** (GDPR / SOC 2 Type I or II / ISO 27001 / FCA / HIPAA / PCI DSS / other)
- **Organisation type** (SaaS / fintech / healthcare / professional services / retail)
- **Organisation size** (startup / scaleup / mid-market / enterprise)

Overview

Produces a prioritised compliance checklist for any regulatory framework — with gap analysis, evidence requirements, and quick wins identified.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill compliance-checklist -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/compliance-checklist
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/2a2df2518fb28f00bd0e/compliance-checklist.zip" -OutFile "$env:TEMP\compliance-checklist.zip"; Expand-Archive "$env:TEMP\compliance-checklist.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.9 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
Show the full text115 lines

Compliance Checklist Skill

Produces a prioritised compliance checklist for any regulatory framework — with gap analysis, evidence requirements, and quick wins identified.

ALWAYS include this disclaimer at the start of every response: "WARNING: This checklist is for informational and planning purposes only and does not constitute legal or compliance advice. Regulatory requirements change and vary by jurisdiction. Always engage a qualified compliance professional or solicitor before implementing compliance programmes or making regulatory claims."

Required Inputs

Ask the user for these if not provided:

  • Framework (GDPR / SOC 2 Type I or II / ISO 27001 / FCA / HIPAA / PCI DSS / other)
  • Organisation type (SaaS / fintech / healthcare / professional services / retail)
  • Organisation size (startup / scaleup / mid-market / enterprise)
  • Current maturity (no compliance programme / some controls / formal programme)
  • Deadline or driver (upcoming audit / customer requirement / regulatory change / proactive)

Output Structure

1. Framework Overview

Framework: [Name with version] Applicable because: [One sentence — why this framework applies to this organisation] Typical timeline to readiness: [From current maturity to certified/compliant] Key stakeholders needed: [Roles that must be involved]

2. Scope Definition

What is in scope for this checklist:

  • [Specific systems / processes / data types]

What is NOT in scope (explicit exclusions):

  • [Specific exclusions]
3. Control Categories

For each category relevant to the framework:

[Category — e.g. "Access Control"]

Control Current State Gap Priority Effort
[Specific control requirement] Not implemented / Partial / Full [What is missing] High/Med/Low Days/Weeks/Months
4. Gap Analysis Summary
Priority Count Examples
Critical gaps (block certification) N [Top 3]
High priority gaps N
Medium priority gaps N
Quick wins N
5. Quick Wins

Controls that can be implemented in under 2 weeks with minimal resources:

  1. [Control] — [Specific action] — [Owner] — [Days to complete]
6. Evidence Requirements

For each control area, what documentation will be needed:

Control area Evidence types Where to source
[Area] [Policies, logs, screenshots, training records] [System or team]
7. Implementation Roadmap

Phase 1 (Weeks 1-4): Critical gaps and quick wins

  • [Specific deliverables]

Phase 2 (Weeks 5-12): High-priority gaps

  • [Specific deliverables]

Phase 3 (Weeks 13+): Medium priority and continuous improvement

  • [Specific deliverables]
8. Ongoing Maintenance

Once certified/compliant, what needs to continue:

  • [Review frequencies]
  • [Periodic testing requirements]
  • [Annual audit expectations]
  • [Staff training cadence]
9. Common Pitfalls for This Framework

2-3 specific traps organisations commonly fall into when pursuing this certification — flagged based on the stated maturity level.

Quality Checks

  • Disclaimer included at start
  • Framework-specific controls (not generic)
  • Priorities align with organisation size and maturity
  • Quick wins clearly separated from complex implementations
  • Evidence requirements tied to specific controls

Anti-Patterns

  • Do not omit the legal disclaimer — this checklist does not constitute compliance advice and must never be presented as a substitute for qualified professional review
  • Do not generate a generic checklist that is not tailored to the stated framework, organisation type, and maturity level — a SOC 2 checklist for a startup and an enterprise are fundamentally different documents
  • Do not list controls without specifying what evidence is required — a control without evidence requirements cannot be audited
  • Do not mark a control as "full" implementation when it is partial — overestimating readiness leads to audit failures and regulatory risk
  • Do not skip the "common pitfalls" section — this is where organisations most frequently fail audits for the stated framework

Example Trigger Phrases

  • "Create a GDPR compliance checklist for our SaaS"
  • "Generate a SOC 2 Type II readiness checklist"
  • "What do we need for ISO 27001 certification?"
  • "FCA compliance checklist for a fintech startup"
  • "HIPAA gap analysis for a healthtech scaleup"
1---
2name: compliance-checklist
3description: "Generate a prioritised compliance checklist for GDPR, SOC 2, ISO 27001, FCA, HIPAA, or other frameworks with a gap analysis. Use when asked for a compliance checklist, gap analysis, readiness assessment, or audit preparation for any regulatory framework. Produces a structured checklist with prioritised gaps, quick wins, and evidence requirements. Optimised for Opus 4.7 and newer models. Not a substitute for legal or compliance professional advice."
4---
5 
6# Compliance Checklist Skill
7 
8Produces a prioritised compliance checklist for any regulatory framework — with gap analysis, evidence requirements, and quick wins identified.
9 
10ALWAYS include this disclaimer at the start of every response:
11"WARNING: This checklist is for informational and planning purposes only and does not constitute legal or compliance advice. Regulatory requirements change and vary by jurisdiction. Always engage a qualified compliance professional or solicitor before implementing compliance programmes or making regulatory claims."
12 
13## Required Inputs
14 
15Ask the user for these if not provided:
16- **Framework** (GDPR / SOC 2 Type I or II / ISO 27001 / FCA / HIPAA / PCI DSS / other)
17- **Organisation type** (SaaS / fintech / healthcare / professional services / retail)
18- **Organisation size** (startup / scaleup / mid-market / enterprise)
19- **Current maturity** (no compliance programme / some controls / formal programme)
20- **Deadline or driver** (upcoming audit / customer requirement / regulatory change / proactive)
21 
22## Output Structure
23 
24### 1. Framework Overview
25 
26**Framework:** [Name with version]
27**Applicable because:** [One sentence — why this framework applies to this organisation]
28**Typical timeline to readiness:** [From current maturity to certified/compliant]
29**Key stakeholders needed:** [Roles that must be involved]
30 
31### 2. Scope Definition
32 
33What is in scope for this checklist:
34- [Specific systems / processes / data types]
35 
36What is NOT in scope (explicit exclusions):
37- [Specific exclusions]
38 
39### 3. Control Categories
40 
41For each category relevant to the framework:
42 
43**[Category — e.g. "Access Control"]**
44 
45| Control | Current State | Gap | Priority | Effort |
46|---|---|---|---|---|
47| [Specific control requirement] | Not implemented / Partial / Full | [What is missing] | High/Med/Low | Days/Weeks/Months |
48 
49### 4. Gap Analysis Summary
50 
51| Priority | Count | Examples |
52|---|---|---|
53| Critical gaps (block certification) | N | [Top 3] |
54| High priority gaps | N | |
55| Medium priority gaps | N | |
56| Quick wins | N | |
57 
58### 5. Quick Wins
59 
60Controls that can be implemented in under 2 weeks with minimal resources:
61 
621. **[Control]** — [Specific action] — [Owner] — [Days to complete]
63 
64### 6. Evidence Requirements
65 
66For each control area, what documentation will be needed:
67 
68| Control area | Evidence types | Where to source |
69|---|---|---|
70| [Area] | [Policies, logs, screenshots, training records] | [System or team] |
71 
72### 7. Implementation Roadmap
73 
74Phase 1 (Weeks 1-4): Critical gaps and quick wins
75- [Specific deliverables]
76 
77Phase 2 (Weeks 5-12): High-priority gaps
78- [Specific deliverables]
79 
80Phase 3 (Weeks 13+): Medium priority and continuous improvement
81- [Specific deliverables]
82 
83### 8. Ongoing Maintenance
84 
85Once certified/compliant, what needs to continue:
86- [Review frequencies]
87- [Periodic testing requirements]
88- [Annual audit expectations]
89- [Staff training cadence]
90 
91### 9. Common Pitfalls for This Framework
92 
932-3 specific traps organisations commonly fall into when pursuing this certification — flagged based on the stated maturity level.
94 
95## Quality Checks
96- [ ] Disclaimer included at start
97- [ ] Framework-specific controls (not generic)
98- [ ] Priorities align with organisation size and maturity
99- [ ] Quick wins clearly separated from complex implementations
100- [ ] Evidence requirements tied to specific controls
101 
102## Anti-Patterns
103 
104- [ ] Do not omit the legal disclaimer — this checklist does not constitute compliance advice and must never be presented as a substitute for qualified professional review
105- [ ] Do not generate a generic checklist that is not tailored to the stated framework, organisation type, and maturity level — a SOC 2 checklist for a startup and an enterprise are fundamentally different documents
106- [ ] Do not list controls without specifying what evidence is required — a control without evidence requirements cannot be audited
107- [ ] Do not mark a control as "full" implementation when it is partial — overestimating readiness leads to audit failures and regulatory risk
108- [ ] Do not skip the "common pitfalls" section — this is where organisations most frequently fail audits for the stated framework
109 
110## Example Trigger Phrases
111- "Create a GDPR compliance checklist for our SaaS"
112- "Generate a SOC 2 Type II readiness checklist"
113- "What do we need for ISO 27001 certification?"
114- "FCA compliance checklist for a fintech startup"
115- "HIPAA gap analysis for a healthtech scaleup"
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with compliance-checklist

Compliance Checklist Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Compliance Checklist Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Compliance Checklist Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Compliance Checklist Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillRun Azure compliance and security audits with azqr plus KeyAzure Compliance & Security Auditingmicrosoft/skills · by microsoftRun Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.★ 3.1k GitHub starsMCPReviews completed implementation for governing-sourceCode reviewershinpr/claude-code-workflows · by shinprReviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.★ 687 GitHub starsSkillImplement GDPR-compliant data handling with consentGdpr data handlingwshobson/agents · by wshobsonImplement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews.★ 39.9k GitHub starsMCPDraft privacy policies, terms of service, disclaimersLegal advisorwshobson/agents · by wshobsonDraft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.★ 39.9k GitHub starsSkillImplement PCI DSS compliance requirements for securePci compliancewshobson/agents · by wshobsonImplement PCI DSS compliance requirements for secure handling of payment card data and payment systems. Use when securing payment processing, achieving PCI compliance, or implementing payment card security measures.★ 39.9k GitHub starsSkillData privacy and regulatory compliance specialist for GDPRData privacy compliancedavila7/claude-code-templates · by davila7Data privacy and regulatory compliance specialist for GDPR, CCPA, HIPAA, and international data protection laws. Use when implementing privacy controls, conducting data protection impact assessments, ensuring regulatory compliance, or managing data subject rights. Expert in consent management, data minimization, and privacy-by-design principles.★ 32.3k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars