Regulatory Audit Generator logo

Regulatory Audit Generator

CommunityPopular
zebbern
regulatory-audit-generator

Builds compliance checklists for business scenarios involving GDPR, PIPL, or advertising/data laws. Outputs a structured checklist with check items, legal basis, risk levels, and actionable recommendations. Triggered by requests like "run a compliance check," "GDPR/PIPL compliance," "pre-launch review," "privacy impact assessment (PIA/DPIA)," or asking if a feature is compliant.

Overview

Publisherzebbern
Repositoryclaude-code-guide
Skill nameregulatory-audit-generator
Stars
4.6K
Forks
464
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by zebbern on GitHub. Read the source before you install it.

Installation

Install the Regulatory Audit Generator AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zebbern/claude-code-guide.git /tmp/claude-code-guide
mkdir -p .claude/skills
cp -r /tmp/claude-code-guide/skills/regulatory-audit-generator .claude/skills/regulatory-audit-generator
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Regulatory Audit Generator in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Regulatory Audit Generator on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Regulatory Audit Generator is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Regulatory Audit Generator — Business Scenario Compliance Checklist Builder

Identifies applicable laws and regulations based on the user's business scenario description, and outputs a structured compliance checklist covering major regulations such as GDPR, PIPL (Personal Information Protection Law), Advertising Law, Cybersecurity Law, and Data Security Law.

Quick Start

Users simply describe their business scenario, and the Agent will:

  1. Identify applicable regulations: Determine which laws and regulations apply based on the business scenario
  2. Generate a checklist: Output a structured list of check items
  3. Label risk levels: Prioritize by severity, marking high/medium/low risk
  4. Provide remediation recommendations: Offer actionable remediation guidance for each compliance risk

Users just need to say:

"We're launching a user profiling feature — help me create a compliance checklist."

The Agent will guide the user to provide necessary information, then output a complete compliance checklist.


1. Supported Regulatory Frameworks

Core Regulations

RegulationAbbreviationScopeKey Focus Areas
Personal Information Protection LawPIPLProcessing personal information within ChinaInformed consent, data minimization, cross-border data transfer
General Data Protection RegulationGDPRInvolving EU user dataLawful basis, data subject rights, DPO, DPIA
Data Security LawDSLData processing activities within ChinaData classification & grading, security assessment, important data export
Cybersecurity LawCSLNetwork operatorsMulti-Level Protection Scheme (MLPS), log retention, security incident reporting
Advertising LawAdvertising publishing and operationsProhibited superlative claims, false advertising, medical advertising
E-Commerce LawE-commerce operatorsInformation disclosure, user reviews, bundled sales
Anti-Unfair Competition LawMarket business activitiesCommercial bribery, false advertising, trade secret infringement
Consumer Protection LawConsumer rights relatedRight to know, fair trade rights, personal information

Industry-Specific Regulations

IndustryRelevant Regulations / Standards
FinanceTechnical Specification for Personal Financial Information Protection (JR/T 0171), Data Security Management Measures for Banking and Insurance Institutions
HealthcarePopulation Health Information Management Measures, Medical Big Data Standards
EducationOnline Protection Chapter of the Minors Protection Law, Provisions on Protection of Children's Personal Information Online
AutomotiveSeveral Provisions on Automobile Data Security Management
Mobile AppsMethods for Identifying Illegal Collection and Use of Personal Information by Apps, Provisions on the Scope of Necessary Personal Information for Common Types of Mobile Applications

2. Compliance Check Procedure (SOP)

Step 1: Gather Business Scenario Information

Confirm the following key information with the user:

DimensionInformation to ConfirmExample
Business DescriptionSpecific content of the feature/service"User profiling feature that recommends products based on behavioral data"
User GroupGeographic region and demographics of target audience"Mainland China users, including minors"
Data TypesWhat data is collected/processed"Name, phone number, browsing history, location data"
Data FlowData storage, transmission, and sharing details"Stored on Alibaba Cloud East China nodes, shared with third-party ad platforms"
Business StageNew launch / existing system needing remediation / M&A due diligence"New feature, planned for launch next month"
Existing MeasuresCurrent compliance measures already in place"Has a privacy policy, but no DPIA completed"

If the user has not provided certain information, the Agent should proactively ask follow-up questions rather than assume or skip.

Step 2: Identify Applicable Regulations

Based on collected information, determine applicable regulations using the following rules:

IF processing personal information → PIPL
IF involving EU users → GDPR
IF involving data storage/transmission → Data Security Law + Cybersecurity Law
IF involving advertising/marketing content → Advertising Law
IF involving e-commerce transactions → E-Commerce Law
IF involving minors → Minors Protection Law + Provisions on Protection of Children's Personal Information Online
IF cross-border data transfer (overseas storage/transmission/access) → PIPL Chapter 3 + Measures for Security Assessment of Data Export
IF involving sensitive personal information → PIPL Chapter 2 Section 2 (separate consent + PIIA)
IF involving automated decision-making → PIPL Article 24 (transparency + right to refuse)
IF involving financial data → JR/T 0171

Step 3: Generate the Compliance Checklist

Output the checklist in the following structure:

Checklist Output Format
markdown
# [Business Scenario Name] Compliance Checklist

**Assessment Date**: YYYY-MM-DD
**Business Description**: [Brief description]
**Applicable Regulations**: [List of regulations]

## Checklist

| No. | Check Item | Legal Basis | Risk Level | Current Status | Remediation Advice |
|-----|-----------|-------------|------------|----------------|-------------------|
| 1 | [Check item description] | [Regulation name + article number] | High/Medium/Low | Compliant/Non-compliant/To be confirmed | [Specific advice] |

## Risk Summary

- High-risk items: X items
- Medium-risk items: X items
- Low-risk items: X items

## Priority Remediation Recommendations

1. [Highest priority remediation item and rationale]
2. [Second highest priority item and rationale]

Step 4: Output Remediation Priorities

Prioritize remediation actions according to the following rules:

PriorityCriteriaDescription
P0 — Immediate ActionHigh risk + currently non-compliantMay face administrative penalties, service shutdown
P1 — Complete This WeekHigh risk + to be confirmed, or medium risk + non-compliantSignificant compliance exposure
P2 — Complete This MonthMedium risk + to be confirmedRequires further assessment and improvement
P3 — Ongoing OptimizationLow riskRecommended improvement but not urgent

3. Common Business Scenario Check Points

Scenario 1: User Registration and Login

Check ItemLegal BasisDescription
Is there a privacy policy / user agreement?PIPL Art. 17Must be displayed and consent obtained before registration
Is only necessary personal information collected?PIPL Art. 6Registration stage should only require phone number/email; should not mandate ID numbers, etc.
Does third-party login disclose data sharing?PIPL Art. 23Login via WeChat/Alipay must disclose what information is shared
Are passwords stored encrypted?CSL Art. 21Plaintext password storage is prohibited
Is account deletion supported?PIPL Art. 47A convenient account deletion channel must be provided

Scenario 2: Marketing and Advertising

Check ItemLegal BasisDescription
Is consent obtained for marketing SMS/emails?PIPL Art. 13, Advertising Law Art. 43Explicit user consent is required
Is an unsubscribe mechanism provided?Advertising Law Art. 43Each marketing message must include an opt-out method
Does ad copy contain prohibited superlative terms?Advertising Law Art. 9Absolute terms like "best," "number one," "national-level" are prohibited
Can profiling-based recommendations be disabled?PIPL Art. 24An option for non-personalized content must be provided
Are advertisements clearly labeled as "Ad"?Advertising Law Art. 14Mass media channels must clearly mark advertisements

Scenario 3: Cross-Border Data Transfer

Check ItemLegal BasisDescription
Does it meet the security assessment filing threshold?Measures for Security Assessment of Data Export Art. 4Processing personal information of 1M+ individuals, or cumulative export of 100K individuals / 10K sensitive records
Has the standard contract been signed?Standard Contract Measures for Personal Information ExportCan sign the standard contract if below the filing threshold
Has a Personal Information Protection Impact Assessment been completed?PIPL Art. 55PIIA must be completed before data export
Has the user been informed and separate consent obtained?PIPL Art. 39Must disclose overseas recipient information
Overseas recipient's data protection capabilityPIPL Art. 38Must assess the recipient's data protection standards

Scenario 4: User Profiling and Personalized Recommendations

Check ItemLegal BasisDescription
Is the automated decision-making logic disclosed?PIPL Art. 24Must be transparent to users
Is an option to disable personalized recommendations provided?PIPL Art. 24Users have the right to refuse
Has a PIIA been conducted for user profiling?PIPL Art. 55Assessment is required when using personal information for automated decision-making
Do profiling tags involve sensitive information?PIPL Art. 28Tags related to religion, health, finance, etc. are classified as sensitive information
Is the use scope of profiling results restricted?PIPL Art. 24Must not impose unreasonable differential treatment in areas such as transaction pricing

Scenario 5: GDPR Compliance (for EU Users)

Check ItemLegal BasisDescription
Has a lawful basis for processing been established?GDPR Art. 6One of six bases: consent, contract, legal obligation, legitimate interest, etc.
Has a DPO been appointed?GDPR Art. 37Required for large-scale processing or processing of special category data
Has a DPIA been completed?GDPR Art. 35Required for high-risk processing activities
Is the right to data portability supported?GDPR Art. 20Data must be provided in a structured, machine-readable format
Can data breaches be reported within 72 hours?GDPR Art. 33Supervisory authority must be notified within 72 hours of discovering a breach
Is the cookie banner compliant?GDPR + ePrivacyActive consent required; pre-checked boxes are not permitted
Are records of processing activities maintained?GDPR Art. 30Required for organizations with 250+ employees or non-occasional processing

4. Risk Level Criteria

Risk LevelCriteriaPotential Consequences
HighViolation of mandatory legal provisions; unlawful processing of sensitive personal information; lack of lawful basis; data export without assessmentAdministrative penalties (fines), service shutdown, criminal liability
MediumCompliance measures incomplete but foundational; insufficient notice; flawed consent mechanism; partial security measure gapsRegulatory interview, ordered remediation within deadline, user complaints
LowBest practices not met but not unlawful; incomplete documentation; processes can be optimizedAudit findings, internal improvements

5. Deliverables

The Agent should ultimately deliver the following to the user:

  1. Compliance Checklist Table: All check items with legal basis, risk levels, current status, and remediation advice
  2. Risk Summary: Count of high/medium/low risk items
  3. Priority Remediation Roadmap: Remediation action list ordered by P0–P3
  4. Supplementary Notes: Plain-language explanations of key compliance requirements to help non-legal staff understand

6. Disclaimers

  1. Regulatory Currency: Laws and regulations are continuously updated. Regulation references in the checklist should be verified against the latest versions. The Agent should remind users to check for the most recent regulatory developments.
  2. Not Legal Advice: This checklist is for reference only and does not constitute legal advice. For significant compliance decisions, consultation with a qualified attorney is recommended.
  3. Industry Variations: Different industries have specific regulatory requirements. The checklist should be adapted to account for industry-specific considerations.
  4. Ongoing Compliance: Compliance is not a one-time effort. Regular reassessment (at least every six months) is recommended.

References

  • Personal Information Protection Law of the People's Republic of China (PIPL, 2021)
  • Data Security Law of the People's Republic of China (DSL, 2021)
  • Cybersecurity Law of the People's Republic of China (CSL, 2017)
  • Advertising Law of the People's Republic of China (2018 Amendment)
  • EU General Data Protection Regulation (GDPR, 2018)
  • Measures for Standard Contracts for Personal Information Export (2023)
  • Measures for Security Assessment of Data Export (2022)
  • GB/T 35273-2020 Information Security Technology — Personal Information Security Specification

Frequently asked questions

What does the Regulatory Audit Generator AI skill do?

Builds compliance checklists for business scenarios involving GDPR, PIPL, or advertising/data laws. Outputs a structured checklist with check items, legal basis, risk levels, and actionable recommendations. Triggered by requests like "run a compliance check," "GDPR/PIPL compliance," "pre-launch review," "privacy impact assessment (PIA/DPIA)," or asking if a feature is compliant.

Why use Regulatory Audit Generator on TypingMind?

Because you install it once and use it with any model. Regulatory Audit Generator is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Regulatory Audit Generator in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zebbern/claude-code-guide/tree/main/skills/regulatory-audit-generator. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Regulatory Audit Generator?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Regulatory Audit Generator?

As many as you like. As long as a model supports skills, you can use Regulatory Audit Generator with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Regulatory Audit Generator AI skill free?

Yes. It is published on GitHub by zebbern under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇