Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Manages responses to regulatory complaints lodged with supervisory authorities under GDPR Article 77, covering internal escalation procedures, DPA response coordination, remediation tracking, and…
Install Regulatory Complaints
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill regulatory-complaints -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills regulatory-complaints --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/regulatory-complaints .claude/skills/regulatory-complaints && 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 "regulatory-complaints" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/regulatory-complaints into .claude/skills/regulatory-complaints/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-complaints", 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/regulatory-complaintsType 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 regulatory-complaints -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills regulatory-complaints --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/regulatory-complaints .agents/skills/regulatory-complaints && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "regulatory-complaints" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/regulatory-complaints into .agents/skills/regulatory-complaints/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-complaints", 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 regulatory-complaints -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills regulatory-complaints --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/regulatory-complaints .cursor/skills/regulatory-complaints && 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 "regulatory-complaints" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/regulatory-complaints into .cursor/skills/regulatory-complaints/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-complaints", 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/regulatory-complaints--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 regulatory-complaints -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills regulatory-complaints --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/regulatory-complaints .gemini/skills/regulatory-complaints && 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 "regulatory-complaints" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/regulatory-complaints into .gemini/skills/regulatory-complaints/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-complaints", 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 regulatory-complaintsInstalls 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 regulatory-complaints -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/regulatory-complaints .github/skills/regulatory-complaints && 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 "regulatory-complaints" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/regulatory-complaints into .github/skills/regulatory-complaints/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-complaints", 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 regulatory-complaints -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 regulatory-complaints --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/regulatory-complaints .opencode/skills/regulatory-complaints && 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 "regulatory-complaints" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/regulatory-complaints into .opencode/skills/regulatory-complaints/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-complaints", 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
regulatory-complaints- GitHub stars
- 301
- Token cost
- ~2k tokens
- SKILL.md length
- 975 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Manages responses to regulatory complaints lodged with supervisory authorities under GDPR Article 77, covering internal escalation procedures, DPA response coordination, remediation tracking, and…
- Works in 8 steps: Receive and Log the Complaint → Internal Escalation → Internal Investigation → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Regulatory Complaint Response… and DPA-Specific Response…
- Runs Python scripts from its folder
What it does
Regulatory Complaints is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages responses to regulatory complaints lodged with supervisory authorities under GDPR Article 77, covering internal escalation procedures, DPA response coordination, remediation tracking, and compliance documentation. Activate for regulatory complaint, supervisory authority complaint, Art. 77, DPA response, ICO complaint queries.
Its SKILL.md is about 2k 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 and Regulatory compliance. 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
- Tasks that involve Regulatory compliance
Example prompts
- “Use the regulatory-complaints skill to manage responses to regulatory complaints lodged with supervisory authorities under GDPR Article 77, covering…”
- “/regulatory-complaints”
Requirements
- Python 3
Workflow steps
8 steps, taken from the step headings in SKILL.md.
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
Regulatory Complaints loads about 2k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 975 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). 975 words, ~2,003 tokens.
Download SKILL.mdSave it as
.claude/skills/regulatory-complaints/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- regulatory-complaints
- description
- Manages responses to regulatory complaints lodged with supervisory authorities under GDPR Article 77, covering internal escalation procedures, DPA response coordination, remediation tracking, and compliance documentation. Activate for regulatory complaint, supervisory authority complaint, Art. 77, DPA response, ICO complaint queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- regulatory-complaint, gdpr-article-77, supervisory-authority, dpa-response, ico-complaint
Responding to Regulatory Complaints
Overview
Under GDPR Article 77, data subjects have the right to lodge a complaint with a supervisory authority (Data Protection Authority / DPA) if they consider that the processing of their personal data infringes the GDPR. When a DPA receives a complaint and contacts the controller, the controller must respond promptly, cooperate fully, and demonstrate compliance. This skill provides the operational procedure for managing regulatory complaints from receipt through resolution.
Legal Foundation
GDPR Article 77 — Right to Lodge a Complaint
Every data subject has the right to lodge a complaint with a supervisory authority, in particular in the Member State of their habitual residence, place of work, or place of the alleged infringement, if the data subject considers that the processing of personal data relating to them infringes the GDPR.
GDPR Article 31 — Cooperation with the Supervisory Authority
The controller and the processor, and where applicable the controller's or the processor's representative, shall cooperate, on request, with the supervisory authority in the performance of its tasks.
GDPR Article 58 — Powers of Supervisory Authorities
Supervisory authorities have investigative powers (Art. 58(1)), corrective powers (Art. 58(2)), and authorisation and advisory powers (Art. 58(3)), including the power to:
- Order the controller to provide information (Art. 58(1)(a))
- Carry out investigations in the form of data protection audits (Art. 58(1)(b))
- Issue warnings, reprimands, and orders (Art. 58(2)(a)-(d))
- Impose administrative fines (Art. 58(2)(i) and Art. 83)
GDPR Article 78 — Right to an Effective Judicial Remedy Against a Supervisory Authority
Data subjects (and controllers) have the right to an effective judicial remedy against legally binding decisions of a supervisory authority.
Regulatory Complaint Response Workflow
Step 1: Receive and Log the Complaint
- Log the complaint with reference REG-YYYY-NNNN.
- Record:
- Supervisory authority (e.g., ICO, CNIL, BfDI, DPC)
- DPA reference number
- Date of DPA correspondence
- Complainant identity (if disclosed by the DPA)
- Summary of the complaint allegations
- DPA's specific requests or questions
- Response deadline set by the DPA
- Immediately notify the Data Protection Officer.
- Escalate to the General Counsel if the complaint involves potential enforcement action or fines.
Step 2: Internal Escalation
| Complaint Severity | Escalation Level | Response Lead | Timeline |
|---|---|---|---|
| Routine (individual rights exercise issue) | DPO | Privacy Analyst | DPA deadline (typically 28 days) |
| Significant (systemic compliance issue) | DPO + General Counsel | DPO | DPA deadline, with internal briefing within 48 hours |
| Critical (potential enforcement/fine) | DPO + General Counsel + CEO | DPO + External Counsel | DPA deadline, with board notification within 24 hours |
Step 3: Internal Investigation
- Review the complaint allegations against internal records:
- DSAR/rights request register (was the request handled correctly?)
- Processing records (Art. 30 register)
- Consent records
- Data breach register
- Privacy impact assessments
- Interview relevant staff members and document their accounts.
- Collect all supporting evidence (emails, system logs, decision records).
- Identify any compliance gaps or procedural failures.
- Assess whether the complaint is substantiated, partially substantiated, or unsubstantiated.
Step 4: Prepare the Response
The DPA response must be:
- Factual: Address each specific allegation or question raised by the DPA.
- Evidenced: Attach supporting documentation.
- Cooperative: Demonstrate willingness to engage per Art. 31.
- Proportionate: Address the complaint scope without volunteering unrelated issues.
Response Structure
- Acknowledgement: Confirm receipt of the DPA's correspondence, cite the DPA reference number.
- Background: Provide a brief factual overview of the processing activity and the controller's relationship with the complainant.
- Response to each allegation: Address each point raised by the DPA with facts and evidence.
- Compliance evidence: Attach relevant documentation (privacy notice, consent records, DSAR response copies, DPIAs, processing records).
- Remediation: If any issue is identified, describe the remediation steps taken or planned, with timelines.
- Cooperation: Confirm willingness to provide any further information the DPA requires.
Show full SKILL.md (366 more words)Show less
Step 5: DPO Review and Approval
- The DPO reviews the draft response for accuracy and completeness.
- If the complaint involves potential enforcement, external legal counsel reviews the response.
- Obtain sign-off from the appropriate authority level per Step 2.
- Submit the response to the DPA before the deadline.
Step 6: Remediation Tracking
If the investigation identifies compliance gaps:
- Create remediation actions with:
- Description of the gap
- Root cause analysis
- Corrective action
- Owner (name and role)
- Target completion date
- Verification method
- Track remediation in the compliance action tracker.
- Report progress to the DPO monthly until all actions are closed.
- Include remediation status in the next DPA communication if the DPA follows up.
Step 7: DPA Decision and Follow-Up
| DPA Outcome | Controller Action |
|---|---|
| Complaint dismissed / no further action | File and close. Update complaint register. |
| Informal resolution recommended | Implement DPA's recommendations. Confirm completion to DPA. |
| Formal reprimand issued (Art. 58(2)(b)) | Record on compliance register. Implement required changes. Report to board. |
| Order to comply issued (Art. 58(2)(c)-(g)) | Implement the order within the specified timeframe. Confirm compliance to DPA. |
| Administrative fine imposed (Art. 83) | Engage external legal counsel. Assess appeal options (Art. 78). Pay or appeal within deadline. |
| Investigation initiated | Cooperate fully. Appoint response team. Preserve all relevant records. |
Step 8: Close and Record
- Update the complaint register with the final outcome.
- Record any lessons learned.
- Feed findings into the compliance improvement programme.
- Retain all complaint documentation for 6 years from the date of the DPA's final decision.
- Report complaint outcomes in the annual privacy compliance report to the board.
DPA-Specific Response Requirements
ICO (United Kingdom)
- The ICO typically sends a preliminary enquiry letter requesting the controller's account of events.
- Standard response timeframe: 28 calendar days.
- Correspondence via the ICO's online case management portal or email.
- The ICO may request a formal response under section 142 of the Data Protection Act 2018 (assessment notice).
CNIL (France)
- Initial questionnaire or formal mise en demeure.
- Response timeframe specified in the correspondence (typically 1-3 months).
- Formal responses must be in French.
DPC (Ireland)
- Relevant for organisations with main establishment in Ireland (one-stop-shop mechanism under Art. 56).
- Response timeframe specified in the correspondence.
© 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/regulatory-complaints 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
Regulatory Complaints 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 |
|---|---|---|---|---|---|---|
| Regulatory Complaints this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Regulatory Audit Generatorzebbern/claude-code-guide | 4.7k | 1 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Reg Gap Analysisanthropics/claude-for-legal | 9.6k | 2 repos | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Policy OpaAgentSecOps/SecOpsAgentKit | 220 | 1 repos | ~3.5k | Automated safety check: Pass | Custom licence | |
| Compliance Checkjosstei/maestro-orchestrate | 465 | — | ~237 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Regulatory Audit Generator
zebbern/claude-code-guide
Builds compliance checklists for business scenarios involving GDPR, PIPL, or advertising/data laws.
- Official
Reg Gap Analysis
anthropics/claude-for-legal
Diff a new or changed regulation against current privacy policy and practice — outputs a gap list and a remediation plan with owners and dates.
Policy Opa
AgentSecOps/SecOpsAgentKit
Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).
Compliance Check
josstei/maestro-orchestrate
Run a Maestro-style regulatory compliance review for GDPR/CCPA, cookie consent, data handling, and licensing
Implementing Compliance
ancoleman/ai-design-components
Implement and maintain compliance with SOC 2, HIPAA, PCI-DSS, and GDPR using unified control mapping, policy-as-code enforcement, and automated evidence collection.
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 Regulatory Complaints
What does Regulatory Complaints do?
Manages responses to regulatory complaints lodged with supervisory authorities under GDPR Article 77, covering internal escalation procedures, DPA response coordination, remediation tracking, and…. Regulatory Complaints is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages responses to regulatory complaints lodged with supervisory authorities under GDPR Article 77, covering internal escalation procedures, DPA response coordination, remediation tracking, and compliance documentation.
When should I use Regulatory Complaints?
Regulatory Complaints fits situations like: tasks that involve Privacy and GDPR; tasks that involve Regulatory compliance.
How do I install Regulatory Complaints in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill regulatory-complaints -a claude-code`. Or copy the skill folder (skills/privacy/regulatory-complaints in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/regulatory-complaints in your project. Claude Code loads it when a task matches its description.
How do I install Regulatory Complaints in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill regulatory-complaints -a codex`. Or copy the skill folder (skills/privacy/regulatory-complaints in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/regulatory-complaints in your project. Codex loads it when a task matches its description.
Can I use Regulatory Complaints 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 regulatory-complaints -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/regulatory-complaints, .gemini/skills/regulatory-complaints, .github/skills/regulatory-complaints and .opencode/skills/regulatory-complaints in your project.
What does Regulatory Complaints need to run?
Going by SKILL.md and its folder, Regulatory Complaints needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Regulatory Complaints 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 Regulatory Complaints 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 Regulatory Complaints use?
Regulatory Complaints 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 Regulatory Complaints use?
About 2k tokens (SKILL.md is roughly 8k 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 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Regulatory Complaints?
Skills that share tags, products or a category with Regulatory Complaints: Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Regulatory Audit Generator (zebbern/claude-code-guide, 4.7k stars), Reg Gap Analysis (anthropics/claude-for-legal, 9.6k stars) and Policy Opa (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Regulatory Complaints?
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.