General Counsel Advisor
alirezarezvani/claude-skills
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping.
Determines controller-processor relationships for AI services and conducts privacy due diligence.
Install AI Vendor Privacy Due
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill ai-vendor-privacy-due -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ai-vendor-privacy-due --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/ai-vendor-privacy-due .claude/skills/ai-vendor-privacy-due && 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 "ai-vendor-privacy-due" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ai-vendor-privacy-due into .claude/skills/ai-vendor-privacy-due/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-vendor-privacy-due", 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/ai-vendor-privacy-dueType 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 ai-vendor-privacy-due -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ai-vendor-privacy-due --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/ai-vendor-privacy-due .agents/skills/ai-vendor-privacy-due && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ai-vendor-privacy-due" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ai-vendor-privacy-due into .agents/skills/ai-vendor-privacy-due/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-vendor-privacy-due", 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 ai-vendor-privacy-due -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ai-vendor-privacy-due --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/ai-vendor-privacy-due .cursor/skills/ai-vendor-privacy-due && 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 "ai-vendor-privacy-due" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ai-vendor-privacy-due into .cursor/skills/ai-vendor-privacy-due/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-vendor-privacy-due", 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/ai-vendor-privacy-due--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 ai-vendor-privacy-due -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills ai-vendor-privacy-due --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/ai-vendor-privacy-due .gemini/skills/ai-vendor-privacy-due && 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 "ai-vendor-privacy-due" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ai-vendor-privacy-due into .gemini/skills/ai-vendor-privacy-due/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-vendor-privacy-due", 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 ai-vendor-privacy-dueInstalls 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 ai-vendor-privacy-due -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/ai-vendor-privacy-due .github/skills/ai-vendor-privacy-due && 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 "ai-vendor-privacy-due" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ai-vendor-privacy-due into .github/skills/ai-vendor-privacy-due/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-vendor-privacy-due", 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 ai-vendor-privacy-due -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 ai-vendor-privacy-due --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/ai-vendor-privacy-due .opencode/skills/ai-vendor-privacy-due && 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 "ai-vendor-privacy-due" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/ai-vendor-privacy-due into .opencode/skills/ai-vendor-privacy-due/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-vendor-privacy-due", 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
ai-vendor-privacy-due- GitHub stars
- 301
- Token cost
- ~2.4k tokens
- SKILL.md length
- 971 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Determines controller-processor relationships for AI services and conducts privacy due diligence.
- Works in 3 steps: Vendor AI Processing Inventory → Privacy Risk Assessment → Contractual Assessment
- Tasks that involve Fundraising and pitch decks
- SKILL.md covers Overview, Controller-Processor…, Due Diligence Assessment… and AI-Specific Contractual Clauses, plus 2 more sections
- Runs Python scripts from its folder
What it does
AI Vendor Privacy Due is an agent skill from mukul975/Privacy-Data-Protection-Skills. Determines controller-processor relationships for AI services and conducts privacy due diligence. Covers SaaS AI (processor), embedded AI (joint controller), API-based AI (assessment framework), and vendor risk assessment. Keywords: AI vendor, controller-processor, due diligence, SaaS AI, joint controller, Art. 28.
Its SKILL.md is about 2.4k 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 Fundraising and pitch decks and Privacy and GDPR. 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 Fundraising and pitch decks
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the ai-vendor-privacy-due skill to determine controller-processor relationships for AI services and conducts privacy due diligence”
- “/ai-vendor-privacy-due”
Requirements
- Python 3
Workflow steps
3 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
AI Vendor Privacy Due loads about 2.4k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 971 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). 971 words, ~2,359 tokens.
Download SKILL.mdSave it as
.claude/skills/ai-vendor-privacy-due/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- ai-vendor-privacy-due
- description
- Determines controller-processor relationships for AI services and conducts privacy due diligence. Covers SaaS AI (processor), embedded AI (joint controller), API-based AI (assessment framework), and vendor risk assessment. Keywords: AI vendor, controller-processor, due diligence, SaaS AI, joint controller, Art. 28.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- ai-privacy-governance
- metadata.tags
- ai-vendor, controller-processor, due-diligence, saas-ai, joint-controller, art-28
AI Vendor Privacy Due Diligence
Overview
AI services create complex controller-processor relationships that differ significantly from traditional data processing arrangements. Whether an AI vendor is a processor, joint controller, or independent controller depends on the degree of autonomy the vendor has over personal data processing — particularly regarding model training on customer data, data retention for model improvement, and the vendor's independent purposes for the data. This skill provides the framework for determining controller-processor roles in AI service relationships, conducting privacy due diligence on AI vendors, and establishing appropriate contractual protections.
Controller-Processor Determination for AI
Decision Framework
| AI Service Model | Typical Role | Key Factors | GDPR Article |
|---|---|---|---|
| SaaS AI — Customer data processed per instructions | Vendor = Processor | Vendor processes data solely on controller's instructions; no independent use | Art. 28 DPA required |
| SaaS AI — Customer data used for model training | Vendor = Joint Controller or Independent Controller | Vendor uses customer data for own model improvement beyond contracted service | Art. 26 JCA or separate controller notice |
| Embedded AI — Pre-trained model in customer infrastructure | Customer = Controller; Vendor = may be processor for support | Model runs in customer environment; vendor may access data for support/updates | Art. 28 if vendor accesses data |
| API-based AI — Customer sends data for inference | Vendor = Processor (if no data retention) or Joint Controller (if training on inputs) | Depends on whether vendor retains, uses, or trains on input data | Assessment required |
| AI Platform — Customer builds models on vendor platform | Vendor = Processor for infrastructure; Controller for platform data | Vendor provides compute; customer controls data and model | Art. 28 DPA + audit rights |
| AI Marketplace — Pre-built models with customer data | Depends on data flow | If customer data enters vendor model → joint controller assessment | Case-by-case |
Key Determination Questions
- Who determines the purpose of processing? — The entity deciding why personal data is processed
- Who determines the means of processing? — The entity deciding how data is processed (but "non-essential means" may be delegated to processor)
- Does the vendor use data for its own purposes? — Model training, benchmarking, product improvement using customer data
- Does the vendor retain data beyond service delivery? — Data kept after inference, stored for training, retained in logs
- Does the vendor make independent decisions about the data? — Choosing to train models, sharing with sub-processors not instructed by customer
Common AI Vendor Patterns
Pattern 1: Pure Inference API (Vendor = Processor)
- Customer sends data; receives inference result
- Vendor does not retain input data beyond processing
- Vendor does not train on customer data
- Vendor acts solely on customer's instructions
- Contractual: Art. 28 DPA with clear scope
Pattern 2: AI with Model Improvement (Vendor = Joint Controller)
- Customer sends data; receives inference result
- Vendor retains data to improve its models
- Vendor determines that model training is a purpose
- Both parties benefit from the model improvement
- Contractual: Art. 26 Joint Controller Agreement
Pattern 3: AI with Anonymised Analytics (Assessment Required)
- Customer sends data; receives inference result
- Vendor claims to anonymise data and use aggregated analytics
- If anonymisation is effective: no personal data processing for analytics
- If anonymisation is not effective (re-identification possible): vendor is controller for analytics
- Assessment: Verify anonymisation effectiveness per WP216
Pattern 4: Embedded AI with Telemetry (Vendor = Processor + may be Controller)
- AI model runs in customer environment
- Vendor collects telemetry data including model performance
- If telemetry contains personal data: vendor may be controller for telemetry processing
- Contractual: Art. 28 DPA for model support + separate arrangement for telemetry
Due Diligence Assessment Framework
Show full SKILL.md (408 more words)Show less
Phase 1: Vendor AI Processing Inventory
For each AI vendor, document:
| Element | Documentation Required |
|---|---|
| AI capabilities | What AI functions does the vendor provide? |
| Personal data inputs | What personal data is sent to the vendor? |
| Personal data outputs | What personal data does the vendor return? |
| Data retention | Does the vendor retain input data? For how long? |
| Model training | Does the vendor train on customer data? |
| Sub-processors | Does the vendor use sub-processors for AI processing? Where? |
| Data location | Where is AI processing performed? What jurisdictions? |
| Security measures | What security controls protect data during AI processing? |
| Human review | Does vendor personnel access customer data? |
Phase 2: Privacy Risk Assessment
| Risk Factor | Assessment | Risk Level |
|---|---|---|
| Data sensitivity | Special category data sent to AI vendor? | |
| Data volume | Volume of personal data processed by vendor | |
| Vendor data use | Vendor uses customer data for own purposes? | |
| International transfers | Data processed outside EU/EEA? | |
| Sub-processor chain | Number and location of sub-processors | |
| Security posture | Certifications (ISO 27001, SOC 2)? | |
| Incident history | Prior data breaches or enforcement actions? | |
| AI-specific risks | Model memorization, output leakage, bias? |
Phase 3: Contractual Assessment
| Contractual Element | Required? | Status |
|---|---|---|
| Art. 28 DPA or Art. 26 JCA | Yes | |
| Processing scope and purpose limitation | Yes | |
| Prohibition on data use beyond instructions (if processor) | Yes | |
| Model training opt-out | Yes (if vendor trains on data) | |
| Sub-processor notification and approval | Yes | |
| International transfer safeguards | If applicable | |
| Data deletion on termination | Yes | |
| Audit rights | Yes | |
| Breach notification obligations | Yes | |
| AI-specific: model privacy testing | Recommended | |
| AI-specific: bias assessment obligations | Recommended for high-risk | |
| AI-specific: output accuracy warranties | Recommended |
AI-Specific Contractual Clauses
Model Training Restrictions
The Processor shall not use Customer Data to train, improve, fine-tune, or
otherwise develop any machine learning model, algorithm, or AI system,
whether for the Customer's benefit or for any other purpose, without prior
written consent from the Customer. Any consent granted shall specify the
scope of permitted training, the data categories involved, and the privacy
safeguards to be applied.AI Output Accuracy
The Provider acknowledges that AI system outputs about identifiable data
subjects must comply with the accuracy principle under Art. 5(1)(d) GDPR.
The Provider shall implement measures to minimise inaccurate outputs about
data subjects and shall promptly correct inaccurate outputs upon
notification.Model Privacy and Bias Obligations
The Provider shall conduct periodic privacy audits of AI models processing
Customer Data, including membership inference testing and training data
extraction testing, and shall make results available to the Customer upon
request. The Provider shall monitor AI systems for discriminatory outcomes
and shall implement bias mitigation measures as required.Enforcement Relevance
- EDPB Guidelines 07/2020 on Controller-Processor: Determination depends on factual circumstances, not contractual labels. A vendor labelled "processor" that uses data for its own purposes is factually a controller.
- Garante v. OpenAI (2023): OpenAI's role as controller for ChatGPT training data confirmed — processing personal data for model training is an independent controller purpose.
- CJEU C-40/17 (Fashion ID): Joint controller status can arise when a party has influence over the purpose and means of processing, even without access to the data.
- DPC v. Meta (WhatsApp, 2023): EUR 5.5M fine — processor-controller determination must reflect actual data use, not just contractual terms.
Integration Points
- ai-dpia: Vendor AI processing must be included in DPIA scope
- ai-training-lawfulness: Vendor training on customer data requires lawful basis assessment
- ai-transparency-reqs: Data subjects must be informed about AI vendor processing
- ai-deployment-checklist: Vendor due diligence is a pre-deployment checklist item
© 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/ai-vendor-privacy-due 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
AI Vendor Privacy Due 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 |
|---|---|---|---|---|---|---|
| AI Vendor Privacy Due this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| General Counsel Advisoralirezarezvani/claude-skills | 28k | — | ~2.3k | Automated safety check: Pass | MIT | |
| TprmSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Cross Regulatory Impact Analyzer Patrick Munrolawve-ai/awesome-legal-skills | 847 | — | ~3.1k | Automated safety check: Pass | AGPL-3.0 | |
| Vendor Due Diligence Patrick Munrolawve-ai/awesome-legal-skills | 847 | — | ~4.1k | Automated safety check: Pass | AGPL-3.0 | |
| Preparing Launch AssetsGTM-Strategist/gtm-strategist-skills | 264 | — | ~5k | Automated safety check: Pass | MIT |
Similar skills
Tprm
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert third-party risk management (TPRM) advisor — a vendor risk analyst for the full lifecycle: risk-based vendor tiering, tailored due-diligence questionnaires (SIG-style or mapped to ISO 27001…
Cross Regulatory Impact Analyzer Patrick Munro
lawve-ai/awesome-legal-skills
Analyzes how multiple regulations interact for a specific product, service, or business model.
Vendor Due Diligence Patrick Munro
lawve-ai/awesome-legal-skills
Risk-based vendor assessment framework for IT service providers, technology vendors, and third-party partners under DORA, NIS2, GDPR.
Preparing Launch Assets
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user needs to build launch assets like a website, pitch deck, press release, product demo, or media kit.
Privacy Data Security
JoelLewis/finance_skills
Design and operate privacy and data security programs for SEC-registered firms under Reg S-P, Reg S-ID, and SEC cybersecurity expectations.
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 AI Vendor Privacy Due
What does AI Vendor Privacy Due do?
Determines controller-processor relationships for AI services and conducts privacy due diligence. AI Vendor Privacy Due is an agent skill from mukul975/Privacy-Data-Protection-Skills. Determines controller-processor relationships for AI services and conducts privacy due diligence.
When should I use AI Vendor Privacy Due?
AI Vendor Privacy Due fits situations like: tasks that involve Fundraising and pitch decks; tasks that involve Privacy and GDPR.
How do I install AI Vendor Privacy Due in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill ai-vendor-privacy-due -a claude-code`. Or copy the skill folder (skills/privacy/ai-vendor-privacy-due in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/ai-vendor-privacy-due in your project. Claude Code loads it when a task matches its description.
How do I install AI Vendor Privacy Due in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill ai-vendor-privacy-due -a codex`. Or copy the skill folder (skills/privacy/ai-vendor-privacy-due in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/ai-vendor-privacy-due in your project. Codex loads it when a task matches its description.
Can I use AI Vendor Privacy Due 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 ai-vendor-privacy-due -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ai-vendor-privacy-due, .gemini/skills/ai-vendor-privacy-due, .github/skills/ai-vendor-privacy-due and .opencode/skills/ai-vendor-privacy-due in your project.
What does AI Vendor Privacy Due need to run?
Going by SKILL.md and its folder, AI Vendor Privacy Due needs Python for the scripts in its folder. Our summary lists: Python 3.
Does AI Vendor Privacy Due 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 AI Vendor Privacy Due 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 AI Vendor Privacy Due use?
AI Vendor Privacy Due 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 AI Vendor Privacy Due use?
About 2.4k tokens (SKILL.md is roughly 9.4k 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.1k tokens, read only when the agent opens those files.
What are the alternatives to AI Vendor Privacy Due?
Skills that share tags, products or a category with AI Vendor Privacy Due: General Counsel Advisor (alirezarezvani/claude-skills, 28k stars), Tprm (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Cross Regulatory Impact Analyzer Patrick Munro (lawve-ai/awesome-legal-skills, 847 stars) and Vendor Due Diligence Patrick Munro (lawve-ai/awesome-legal-skills, 847 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains AI Vendor Privacy Due?
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.