C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Guides audit follow-up and verification processes including follow-up scheduling, remediation effectiveness testing, finding closure criteria, re-testing procedures, status reporting, and escalation…
Install Audit Follow Up Verify
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills audit-follow-up-verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/audit-follow-up-verify .claude/skills/audit-follow-up-verify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "audit-follow-up-verify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/audit-follow-up-verify into .claude/skills/audit-follow-up-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-follow-up-verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/audit-follow-up-verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills audit-follow-up-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/audit-follow-up-verify .agents/skills/audit-follow-up-verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "audit-follow-up-verify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/audit-follow-up-verify into .agents/skills/audit-follow-up-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-follow-up-verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills audit-follow-up-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/audit-follow-up-verify .cursor/skills/audit-follow-up-verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "audit-follow-up-verify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/audit-follow-up-verify into .cursor/skills/audit-follow-up-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-follow-up-verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/audit-follow-up-verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills audit-follow-up-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/audit-follow-up-verify .gemini/skills/audit-follow-up-verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "audit-follow-up-verify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/audit-follow-up-verify into .gemini/skills/audit-follow-up-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-follow-up-verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills audit-follow-up-verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/audit-follow-up-verify .github/skills/audit-follow-up-verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "audit-follow-up-verify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/audit-follow-up-verify into .github/skills/audit-follow-up-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-follow-up-verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills audit-follow-up-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/audit-follow-up-verify .opencode/skills/audit-follow-up-verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "audit-follow-up-verify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/audit-follow-up-verify into .opencode/skills/audit-follow-up-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit-follow-up-verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
audit-follow-up-verify- GitHub stars
- 301
- Token cost
- ~1.5k tokens
- SKILL.md length
- 636 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides audit follow-up and verification processes including follow-up scheduling, remediation effectiveness testing, finding closure criteria, re-testing procedures, status reporting, and escalation…
- Works in 6 steps: Remediation actions completed: All… → Evidence provided: Remediation Owner… → Independent verification: Verification… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Follow-Up Scheduling, Verification Testing Methods and Closure Criteria, plus 4 more sections
- Runs Python scripts from its folder
What it does
Audit Follow Up Verify is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides audit follow-up and verification processes including follow-up scheduling, remediation effectiveness testing, finding closure criteria, re-testing procedures, status reporting, and escalation of unremediated findings. Implements IIA Standard 2500 monitoring requirements and ISO 19011 follow-up guidance for privacy audit engagements. Keywords: audit follow-up, verification testing, finding closure, remediation effectiveness, re-testing, follow-up audit.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the audit-follow-up-verify skill to guide audit follow-up and verification processes including follow-up scheduling, remediation effectiveness…”
- “/audit-follow-up-verify”
Requirements
- Python 3
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Remediation actions completed: All planned actions documented as complete by the Remediation Owner
- Evidence provided: Remediation Owner provides documentary evidence of completion
- Independent verification: Verification Owner (auditor or independent party) confirms effectiveness through testing
- Root cause addressed: Verification confirms the underlying root cause is resolved, not just the symptom
- Sustainable: The fix is embedded in ongoing processes (not a one-time manual correction)
- Documented: Working papers document the verification procedure, evidence reviewed, and conclusion
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Audit Follow Up Verify loads about 1.5k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 636 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 636 words, ~1,549 tokens.
Download SKILL.mdSave it as
.claude/skills/audit-follow-up-verify/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- audit-follow-up-verify
- description
- Guides audit follow-up and verification processes including follow-up scheduling, remediation effectiveness testing, finding closure criteria, re-testing procedures, status reporting, and escalation of unremediated findings. Implements IIA Standard 2500 monitoring requirements and ISO 19011 follow-up guidance for privacy audit engagements. Keywords: audit follow-up, verification testing, finding closure, remediation effectiveness, re-testing, follow-up audit.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- privacy-audit-certification
- metadata.tags
- audit-follow-up, verification-testing, finding-closure, remediation-effectiveness, re-testing
Audit Follow-Up and Verification
Overview
Audit follow-up is the process by which the audit function monitors and verifies that management has effectively implemented remediation actions in response to audit findings. IIA Standard 2500 requires the Chief Audit Executive to establish and maintain a system to monitor the disposition of results communicated to management. Follow-up is not merely tracking whether actions were completed — it requires independent verification that the remediation actually addresses the root cause and reduces the identified risk to an acceptable level.
In privacy audits, effective follow-up is critical because unremediated findings represent ongoing regulatory non-compliance. A GDPR Art. 5(2) accountability failure, an unpatched consent mechanism, or a persistent DSAR processing delay exposes the organization to supervisory authority enforcement, data subject complaints, and reputational harm.
Follow-Up Scheduling
Follow-up timing is driven by finding severity:
| Severity | Initial Follow-Up | Re-test if Partial | Maximum Extensions |
|---|---|---|---|
| Critical | 30 days after target date | 15 days | 1 (requires CPO approval) |
| High | 60 days after target date | 30 days | 2 (requires DPO approval) |
| Medium | 90 days after target date | 45 days | 2 |
| Low | 180 days after target date | 90 days | 3 |
| Advisory | Next scheduled audit | N/A | N/A |
Verification Testing Methods
Re-Performance
The auditor independently repeats the control activity to verify it produces the expected result. Used for procedural controls (e.g., re-performing a DSAR response to verify the process meets the 30-day deadline).
Inspection
The auditor examines records, documents, or system configurations produced after remediation to verify the control is operating as designed. Used for documentary controls (e.g., inspecting updated DPAs for Art. 28 compliance).
Observation
The auditor observes the remediated process in real-time to verify it functions correctly. Used for operational controls (e.g., observing the updated breach notification workflow during a tabletop exercise).
Inquiry and Corroboration
The auditor interviews process owners about the remediated control and corroborates statements with independent evidence. Used when direct testing is impractical.
Data Analytics
The auditor analyzes post-remediation data to verify the control is producing expected outcomes. Used for measurable controls (e.g., analyzing DSAR response times post-remediation to verify improvement).
Show full SKILL.md (297 more words)Show less
Closure Criteria
A finding may be closed only when ALL of the following are satisfied:
- Remediation actions completed: All planned actions documented as complete by the Remediation Owner
- Evidence provided: Remediation Owner provides documentary evidence of completion
- Independent verification: Verification Owner (auditor or independent party) confirms effectiveness through testing
- Root cause addressed: Verification confirms the underlying root cause is resolved, not just the symptom
- Sustainable: The fix is embedded in ongoing processes (not a one-time manual correction)
- Documented: Working papers document the verification procedure, evidence reviewed, and conclusion
Finding Status Lifecycle
New → In Progress → Remediation Complete → Pending Verification → Closed
↓
Partial Pass → Re-remediation → Pending Verification
↓
Fail → Reopened → EscalationEscalation for Unremediated Findings
| Trigger | Escalation Level | Action |
|---|---|---|
| Finding overdue 30+ days (Critical) | CPO and CISO | Mandatory management meeting within 5 days |
| Finding overdue 45+ days (High) | Audit Committee | Report to next Audit Committee meeting |
| Finding failed verification twice | DPO and CPO | Root cause review and revised plan required |
| Finding open 12+ months (any severity) | Board Audit Committee | Include in annual audit opinion |
| Repeated finding (same root cause, 3+ occurrences) | Audit Committee | Systemic issue investigation |
Reporting
Individual Finding Follow-Up Report
Produced for each verification event: finding reference, verification method, evidence reviewed, test results, conclusion (pass/partial/fail), and recommended next steps.
Periodic Follow-Up Summary
Monthly report to DPO and CPO summarizing: total open findings by severity, overdue findings, findings closed in period, verification pass rate, aging analysis, and escalation status.
Annual Audit Opinion Impact
Unremediated findings at year-end are factored into the annual audit opinion. Persistent critical or high findings may result in an "Unsatisfactory" or "Needs Improvement" rating.
Integration Points
- audit-remediation-program: Follow-up verifies the effectiveness of remediation managed by the remediation program
- audit-evidence-collect: Follow-up requires fresh evidence collection using the same quality standards
- audit-report-writing: Follow-up results feed into periodic and annual audit reports
- records-of-processing: Follow-up may verify corrections to ROPA entries
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/audit-follow-up-verify of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
Compare with similar skills
Audit Follow Up Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Audit Follow Up Verify this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
AI Dpia
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
Pia Threshold Screening
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Related
Categories
Questions about Audit Follow Up Verify
What does Audit Follow Up Verify do?
Guides audit follow-up and verification processes including follow-up scheduling, remediation effectiveness testing, finding closure criteria, re-testing procedures, status reporting, and escalation…. Audit Follow Up Verify is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides audit follow-up and verification processes including follow-up scheduling, remediation effectiveness testing, finding closure criteria, re-testing procedures, status reporting, and escalation of unremediated findings.
When should I use Audit Follow Up Verify?
Audit Follow Up Verify fits situations like: tasks that involve Privacy and GDPR.
How do I install Audit Follow Up Verify in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a claude-code`. Or copy the skill folder (skills/privacy/audit-follow-up-verify in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/audit-follow-up-verify in your project. Claude Code loads it when a task matches its description.
How do I install Audit Follow Up Verify in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a codex`. Or copy the skill folder (skills/privacy/audit-follow-up-verify in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/audit-follow-up-verify in your project. Codex loads it when a task matches its description.
Can I use Audit Follow Up Verify in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill audit-follow-up-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-follow-up-verify, .gemini/skills/audit-follow-up-verify, .github/skills/audit-follow-up-verify and .opencode/skills/audit-follow-up-verify in your project.
What does Audit Follow Up Verify need to run?
Going by SKILL.md and its folder, Audit Follow Up Verify needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Audit Follow Up Verify access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Audit Follow Up Verify safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Audit Follow Up Verify use?
Audit Follow Up Verify is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Audit Follow Up Verify use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Audit Follow Up Verify?
Skills that share tags, products or a category with Audit Follow Up Verify: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Audit Follow Up Verify?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.