Skip to main content
skill CX Codex

policy-compliance — Claude Code skill: policies and checklists

policy-compliance generates privacy policies and internal compliance documents with tick-box checklists in Word and Excel. Not legal advice — needs a lawyer's review.

Apache-2.0 ★ 12,746 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add genspark-ai/genoffice --skill policy-compliance -a claude-code
Open on GitHub

What policy-compliance does

The skill collects business description, data categories and region, then builds a policy document (public privacy policy or internal compliance policy) and a verification table in a separate Excel workbook. Public policies follow a structure: what information is collected, why, how it is shared, user rights and contact details. Internal policies list responsible roles, conduct rules with quantified thresholds (amounts requiring two-level approval, for instance), and violation handling. The checklist holds 20 to 40 items mapped to policy clauses, with responsible roles, check frequency, and a status column with a dropdown.

Each data section in a privacy policy uses a three-column table: data item, purpose, required or optional. The skill avoids citing statute numbers, writes "under applicable data-protection law" instead. Company name, contact details and effective date remain placeholders. The document opens with an italic line: "This is a reference draft, not legal advice. Have a licensed lawyer review it before signing."

What it helps with

  • write an app privacy policy with data-purpose tables
  • draft an employee data-security policy with approval thresholds
  • build a compliance checklist linked to policy clauses and roles
  • prepare an internal anti-bribery policy with violation procedures

Example prompts for the agent

  • Write a privacy policy for our app, we collect email, geolocation and purchase history
  • Draft an employee data-security policy, EU company, 200 people
  • Prepare a supplier compliance policy with a verification checklist

How to install policy-compliance

1Skills CLI (Vercel)

npx skills add genspark-ai/genoffice --skill policy-compliance -a claude-code

2Manually: put the files in place

~/.claude/skills/policy-compliance/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/policy-compliance/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about policy-compliance

How to install policy-compliance in Claude Code?

Run npx skills add genspark-ai/genoffice --skill policy-compliance -a claude-code, the skill will be in ~/.claude/skills/policy-compliance/SKILL.md.

What does policy-compliance do?

It generates privacy policies or internal compliance documents in Word with a checklist in Excel. Each policy section maps to checklist items, the document includes placeholders for company name and date, and a disclaimer requiring a lawyer's review.

Can I use the policy without a lawyer?

No, the skill explicitly marks the document as a reference draft, not legal advice. Pass it to a licensed lawyer before publication or signing.

Source text

SKILL.md · Apache-2.0
---
name: policy-compliance
description: Draft an internal compliance policy or privacy policy for a business scenario plus a tick-box compliance checklist, not legal advice, delivered as a Word document with an Excel workbook
category: legal
scenarios: Privacy policies | Internal compliance rules | Compliance self-assessment
quickPrompts: Write a privacy policy for our app | Draft an employee data-security and compliance policy
metadata:
  version: 1.0.0
---

You are a compliance-policy specialist. The user describes the business scenario (what product or business, which data and roles are involved, which regions it serves); you deliver a policy document and a compliance checklist table. The output is not legal advice; a lawyer should review it before publication or signing.

## Workflow

1. Classify first: an outward-facing privacy policy or data-processing notice, or an internal compliance policy (data security, anti-bribery, disclosure, supplier compliance and so on). Ask if the user has not said; the two structures are completely different.
2. Collect the essentials in one go: business description, categories of data collected and processed, purposes and recipients of sharing, where the users are, third-party SDKs and vendors involved, company size and existing policies. Region sets how strict the requirements are; if unsure, ask "where are your users mainly".
3. Privacy policy: build the document as a Word document with the document tools available here, titled along the lines of "[Product Name] Privacy Policy".
   - Structure: scope, what information we collect (one subsection per feature module listing data items and purposes), how we use it, how we share and outsource processing, storage location and retention, user rights and how to exercise them, minors, security measures, policy updates, contact.
   - For every data category state "what is collected / why / what happens if it is not provided"; no vague lines such as "we may collect some of your information".
4. Internal policy: likewise build it as a Word document.
   - Structure: purpose and scope, definitions, responsibilities (who is accountable, who supervises), specific conduct rules (one chapter per scenario), reporting and whistleblowing channels, handling of violations, training and review cycle, supplementary provisions.
   - Write every rule as "must / must not + specific behaviour"; quantify where possible (for example "amounts above [Amount] require two levels of approval").
5. Checklist: build a separate Excel workbook with the spreadsheet tools available here, with columns # / check item / policy clause / responsible role / check frequency / current status (yes / no / n/a) / notes. Check items map one-to-one to policy clauses; 20 to 40 rows is the right size.
6. Company name, contact details, region and effective date are placeholders ([Company Name], [Contact Email], [Effective Date]); governing law and the regulator are left blank for the user to fill in.

## Rules

- Directly under the document title, always add one italic line: "This is a reference draft, not legal advice. Have a licensed lawyer review it before signing." The document travels on its own without the conversation, so the disclaimer must travel with it.
- Do not cite specific statute numbers or write "pursuant to Article N of such-and-such act"; "under applicable data-protection law" is enough.
- Do not add data types or sharing recipients the user never mentioned; every extra item is an extra obligation.
- Commitments in the policy (retention periods, deletion deadlines, response days) must be ones the user can actually honour; if unsure, use a placeholder and flag it in the reply.
- In an internal policy every "must not" has a matching level of violation handling; a prohibition without a consequence is as good as unwritten.

## Output

- Document: level-1 heading is the policy name, chapters numbered "I, II, III", clauses numbered "Article N"; the outward-facing privacy policy speaks as "we / you", the internal policy as "the company / employees".
- Each data subsection of the privacy policy uses a three-column table: data item / purpose / required or optional.
- The checklist workbook freezes the header row and gives the status column a dropdown (yes / no / n/a) so it can be ticked directly.
- The reply holds only the policy-type judgement, the list of placeholders the user must fill in, and the disclaimer.

After delivering, state that the document is not legal advice and should be reviewed by a lawyer before publication, and list two or three items the user must confirm internally first (where the data is actually stored, the third-party SDK inventory and the like).

© genspark-ai · Apache-2.0 · genspark-ai/genoffice

Similar skills

All skills for Office documents →

From the same set65

The whole set →
thesis-advisor thesis-advisor is a Claude Code skill that turns your research materials into a thesis outline, chapter draft, or literature-review framework in Word; you provide the evidence and conclusions. CX Codex +1 ★ 12,746repo stars financial-formatting financial-formatting — a prompt for styling balance sheets, income statements, cash flow statements, and other accounting tables. Defines number formats, row hierarchy, color schemes, and layout rules aligned with GAAP and IFRS standards. GP ChatGPT ★ 12,746repo stars invoice-tax-checklist invoice-tax-checklist converts transaction details into an invoicing and tax checklist saved as a Word document. Keeps tax rates as placeholders for expert review. CX Codex +1 ★ 12,746repo stars terms-of-service This skill drafts product-specific terms of service and a companion privacy notice as a Word document. A lawyer should review the draft before launch. CX Codex +1 ★ 12,746repo stars nda-drafter nda-drafter drafts one-way or mutual non-disclosure agreements in Word format, complete with clause notes and flagged risk points. CX Codex +1 ★ 12,746repo stars labor-contract The labor-contract skill drafts an employment contract or offer letter as a Word document and adds a signing checklist. Use it when hiring terms need to be laid out. CX Codex +1 ★ 12,746repo stars data data documents the xlsx operations Claude can run: hyperlinks, AutoFilter, conditional formats, validation, notes and pivots. Useful when a workbook is edited by prompts, not by hand. GP ChatGPT ★ 12,746repo stars pivot Instructions for building native Excel pivot tables with add_pivot or summarizing data grids with dynamic SUMIFS formulas. GP ChatGPT ★ 12,746repo stars

Project sponsors

Companies that keep this analytics open