ai-disclosure-policy

Featured

Decide when and how your product and communications must (or should) label AI-generated content, and write the disclosure policy — surface-by-surface rules, exact label wording, and the review trigger for regulations like the EU AI Act's transparency obligations. Use when asked 'do we have to label AI content', 'write our AI disclosure policy', 'are we covered for the AI Act', or when marketing/support/product start shipping AI-generated output. Produces a disclosure policy with a per-surface matrix and ready-to-use label copy. Not legal advice.

AI & Automation 1,231 stars 221 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# AI Disclosure Policy Skill Every company now ships AI-generated content somewhere — support replies, marketing images, chatbot conversations, synthetic voices — and most have no rule for when to say so. Meanwhile transparency regulation is arriving (the EU AI Act's transparency obligations for chatbots, synthetic media, and deepfakes being the headline example, with obligations phasing in through 2026–2027), and the trust cost of an *undisclosed* AI surface being discovered is higher than the disclosure ever was. This skill produces the policy: what you label, where, in what words — with the honest line that final regulatory judgment belongs to your lawyer, and this document is what makes that conversation short. ## What This Skill Produces - A **surface inventory**: every place AI-generated content reaches users or the public, with today's disclosure state - A **disclosure matrix**: per surface — required (regulatory), expected (platform/industry norm), or chosen (trust) — with the reasoning - **Label copy** ready to ship: UI strings, footer lines, image/video marks, chatbot self-identification wording - The **review triggers**: what changes (new surface, new market, new regulation phase) forces a policy re-read, and who owns it ## Required Inputs Ask for (if not already provided): - Where AI output ships today or soon: chatbots, support, marketing content, images/video/voice, code, docs — and which are fully automated vs human-reviewed - Markets served (E...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
6 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

ai-usage-policy

Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog. Use when asked for a company AI policy, acceptable-use rules for ChatGPT/Claude/Copilot at work, guidance on what data may go into AI tools, or to fix a policy nobody reads. Produces a one-page usable policy plus the decision log behind it. Not a substitute for legal advice; pairs with compliance-checklist for regulatory mapping and ai-ethics-review for system-level assessments.

1,231 Updated today
mohitagw15856
AI & Automation Solid

employee-ai-policy

Use when reviewing a draft internal employee AI-use policy — or drafting review criteria when no policy exists — to identify gaps, inconsistencies, and priority issues for attorney and HR review.

15 Updated 4 days ago
zgbrenner
AI & Automation Listed

usage-policy-writer

Generate a human-facing AI usage policy with approved tools, data classification, risk model explanations, and exception processes — saved to $HOME/.ai-first-kit/. Produces a policy document for HUMANS (not agents) that explains what AI tools are approved, what data can be used with AI, and the reasoning behind each decision. Use when the user says 'AI usage policy', 'AI handbook', 'what tools are approved', 'data classification for AI', 'AI rules for the team', 'usage guidelines', 'AI policy', 'human AI rules', 'acceptable use policy', or 'what can we use AI for'. Also use when the user describes people unsure what they're allowed to do with AI, different teams having different answers about approved tools, no clear policy about client data and AI, or needing to explain the 'why' behind AI rules — even if they don't use the word 'policy'. This skill MUST be consulted because it produces a structured human-facing policy with risk model reasoning and exception processes; a conversational answer cannot create t

6 Updated today
synaptiai