К основному содержанию
скилл CX Codex

regulatory-audit-generator — скилл для Claude Code

Собирает чек-лист требований для бизнес-сценария: указывает применимые нормы, уровни риска и рекомендации по устранению проблем. Пригодится для проверки функции перед запуском.

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add zebbern/claude-code-guide --skill regulatory-audit-generator -a claude-code
Открыть на GitHub

Что делает regulatory-audit-generator

Опишите сервис или функцию, и скилл определит, какие правила могут относиться к сценарию: например, GDPR для пользователей из ЕС, PIPL для обработки персональных данных в Китае или Advertising Law для рекламного контента. В чек-листе будут пункты проверки, правовые основания, уровень риска и рекомендации. Скилл также группирует риски по приоритету устранения.

Перед оценкой агент уточняет детали, если их не хватает: географию и состав пользователей, типы данных, их передачу и хранение, этап проекта и уже принятые меры. Он не должен угадывать недостающие обстоятельства. Среди проверяемых ситуаций — трансграничная передача данных, автоматизированные решения и обработка финансовых данных; для последних указана JR/T 0171.

Какие задачи решает

  • составить чек-лист требований для запуска функции
  • определить, какие нормы затрагивают обработку данных пользователей
  • расставить приоритеты по рискам и мерам исправления
  • подготовить вопросы о хранении и передаче данных

Примеры запросов агенту

  • Составь чек-лист для запуска функции рекомендаций по истории просмотров пользователей из ЕС.
  • Проверь, какие требования затрагивает передача персональных данных рекламным платформам.
  • Подготовь оценку рисков для мобильного приложения, которым пользуются несовершеннолетние в Китае.

Как установить regulatory-audit-generator

1Через Skills CLI (Vercel)

npx skills add zebbern/claude-code-guide --skill regulatory-audit-generator -a claude-code

2Вручную: положить файлы

~/.claude/skills/regulatory-audit-generator/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/regulatory-audit-generator/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о regulatory-audit-generator

Как установить regulatory-audit-generator в Claude Code?

Выполните npx skills add zebbern/claude-code-guide --skill regulatory-audit-generator -a claude-code. Файл скилла находится по пути ~/.claude/skills/regulatory-audit-generator/SKILL.md.

Что делает regulatory-audit-generator?

По описанию бизнес-сценария он подбирает применимые нормы и формирует чек-лист с правовыми основаниями, уровнями риска и рекомендациями по устранению проблем.

Какие сведения нужно подготовить для проверки?

Агент уточняет описание функции, географию и состав пользователей, типы данных, их хранение и передачу, этап проекта и уже принятые меры. Если сведений не хватает, он задаёт дополнительные вопросы, а не делает предположения.

Исходный текст

SKILL.md · MIT
---
name: regulatory-audit-generator
description: "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."
license: MIT
---

# 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

| Regulation | Abbreviation | Scope | Key Focus Areas |
|------------|-------------|-------|-----------------|
| Personal Information Protection Law | PIPL | Processing personal information within China | Informed consent, data minimization, cross-border data transfer |
| General Data Protection Regulation | GDPR | Involving EU user data | Lawful basis, data subject rights, DPO, DPIA |
| Data Security Law | DSL | Data processing activities within China | Data classification & grading, security assessment, important data export |
| Cybersecurity Law | CSL | Network operators | Multi-Level Protection Scheme (MLPS), log retention, security incident reporting |
| Advertising Law | — | Advertising publishing and operations | Prohibited superlative claims, false advertising, medical advertising |
| E-Commerce Law | — | E-commerce operators | Information disclosure, user reviews, bundled sales |
| Anti-Unfair Competition Law | — | Market business activities | Commercial bribery, false advertising, trade secret infringement |
| Consumer Protection Law | — | Consumer rights related | Right to know, fair trade rights, personal information |

### Industry-Specific Regulations

| Industry | Relevant Regulations / Standards |
|----------|--------------------------------|
| Finance | Technical Specification for Personal Financial Information Protection (JR/T 0171), Data Security Management Measures for Banking and Insurance Institutions |
| Healthcare | Population Health Information Management Measures, Medical Big Data Standards |
| Education | Online Protection Chapter of the Minors Protection Law, Provisions on Protection of Children's Personal Information Online |
| Automotive | Several Provisions on Automobile Data Security Management |
| Mobile Apps | Methods 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:

| Dimension | Information to Confirm | Example |
|-----------|----------------------|---------|
| Business Description | Specific content of the feature/service | "User profiling feature that recommends products based on behavioral data" |
| User Group | Geographic region and demographics of target audience | "Mainland China users, including minors" |
| Data Types | What data is collected/processed | "Name, phone number, browsing history, location data" |
| Data Flow | Data storage, transmission, and sharing details | "Stored on Alibaba Cloud East China nodes, shared with third-party ad platforms" |
| Business Stage | New launch / existing system needing remediation / M&A due diligence | "New feature, planned for launch next month" |
| Existing Measures | Current 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:

| Priority | Criteria | Description |
|----------|----------|-------------|
| P0 — Immediate Action | High risk + currently non-compliant | May face administrative penalties, service shutdown |
| P1 — Complete This Week | High risk + to be confirmed, or medium risk + non-compliant | Significant compliance exposure |
| P2 — Complete This Month | Medium risk + to be confirmed | Requires further assessment and improvement |
| P3 — Ongoing Optimization | Low risk | Recommended improvement but not urgent |

---

## 3. Common Business Scenario Check Points

### Scenario 1: User Registration and Login

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

### Scenario 2: Marketing and Advertising

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

### Scenario 3: Cross-Border Data Transfer

| Check Item | Legal Basis | Description |
|-----------|-------------|-------------|
| Does it meet the security assessment filing threshold? | Measures for Security Assessment of Data Export Art. 4 | Processing 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 Export | Can sign the standard contract if below the filing threshold |
| Has a Personal Information Protection Impact Assessment been completed? | PIPL Art. 55 | PIIA must be completed before data export |
| Has the user been informed and separate consent obtained? | PIPL Art. 39 | Must disclose overseas recipient information |
| Overseas recipient's data protection capability | PIPL Art. 38 | Must assess the recipient's data protection standards |

### Scenario 4: User Profiling and Personalized Recommendations

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

### Scenario 5: GDPR Compliance (for EU Users)

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

---

## 4. Risk Level Criteria

| Risk Level | Criteria | Potential Consequences |
|-----------|----------|----------------------|
| High | Violation of mandatory legal provisions; unlawful processing of sensitive personal information; lack of lawful basis; data export without assessment | Administrative penalties (fines), service shutdown, criminal liability |
| Medium | Compliance measures incomplete but foundational; insufficient notice; flawed consent mechanism; partial security measure gaps | Regulatory interview, ordered remediation within deadline, user complaints |
| Low | Best practices not met but not unlawful; incomplete documentation; processes can be optimized | Audit 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

© zebbern · MIT · zebbern/claude-code-guide

Похожие скиллы

Все скиллы по теме «Безопасность» →
git-guardrails-claude-code Matt Pocock Скилл ставит хук Claude Code, который останавливает опасные Git-команды до их запуска. Нужен, если агент не должен делать push или удалять изменения. 499 069установок ponytail-review DietrichGebert Скилл проверяет изменения глубже обычного diff: читает связанный код, ищет ошибки, риски, проблемы нагрузки и недостающие тесты. Пригодится для ревью PR и коммитов. CX Codex +1 57 000установок ponytail-audit DietrichGebert Проверяет репозиторий и ранжирует ошибки, риски и лишний код. Подойдёт, если нужен разовый разбор без автоматических правок. CX Codex +1 45 400установок security-audit cloudflare Проверяет кодовую базу на уязвимости и ищет нарушения границ доверия. Пригодится перед релизом или для точечного разбора опасных участков кода. CX Codex +1 54 800установок security-and-hardening addyosmani Помогает проектировать защиту и проверять код на уязвимости при работе с вводом, авторизацией, сессиями и внешними сервисами. Подойдёт перед релизом и при создании функций, которые обрабатывают недоверенные данные. CX Codex +1 70 200установок supabase официальный supabase Скилл помогает настраивать базу данных, аутентификацию и RLS в Supabase без скрытых дыр в безопасности. CX Codex GP ChatGPT 8установок

Из того же набора40

scholarly-writing-refiner Редактирует научные статьи на английском языке абзац за абзацем. Скилл проверяет грамматику, лексику и связность текста перед подачей в журнал. CX Codex +1 ★ 4 679звёзд репо scanning-tools Скилл помогает выбрать и применять инструменты для проверки сетей, веб-приложений и систем на уязвимости. Пригодится для планирования сканирования и подготовки отчётов. CX Codex +1 ★ 4 679звёзд репо route-to-openapi Сканирует определения маршрутов в исходниках и собирает спецификацию OpenAPI 3.0.3. Пригодится, когда документация API нужна, а писать её руками не хочется. CX Codex +1 ★ 4 679звёзд репо repo-audit Анализирует историю Git: находит частые изменения в файлах, распределение авторов и утечки секретов в коммитах. CX Codex +1 ★ 4 679звёзд репо regression-modeler Считает линейную или логистическую регрессию по вашей таблице и объясняет коэффициенты простыми словами. Пригодится, когда надо проверить значимость признаков без ручного кода. CX Codex +1 ★ 4 679звёзд репо r3f-animation Скилл помогает писать 3D-анимации в React Three Fiber: от циклов useFrame до микширования клипов GLTF и пружин. CX Codex +1 ★ 4 679звёзд репо r2-upload Загружает файлы в Cloudflare R2, AWS S3 и совместимые хранилища, затем создаёт временную ссылку на скачивание. Пригодится, когда нужно передать файл по ссылке с ограниченным сроком действия. CX Codex +1 ★ 4 679звёзд репо project-sizing-guide Считает трудозатраты по PERT, T-shirt sizing и Function Point Analysis. Пригодится, когда нужно ответить, сколько займёт фича. CX Codex +1 ★ 4 679звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой