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.
Conducts Privacy Impact Assessment for vendor and third-party data processing arrangements.
Install Pia Vendor Processing
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill pia-vendor-processing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills pia-vendor-processing --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/pia-vendor-processing .claude/skills/pia-vendor-processing && 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 "pia-vendor-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/pia-vendor-processing into .claude/skills/pia-vendor-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pia-vendor-processing", 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/pia-vendor-processingType 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 pia-vendor-processing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills pia-vendor-processing --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/pia-vendor-processing .agents/skills/pia-vendor-processing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pia-vendor-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/pia-vendor-processing into .agents/skills/pia-vendor-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pia-vendor-processing", 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 pia-vendor-processing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills pia-vendor-processing --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/pia-vendor-processing .cursor/skills/pia-vendor-processing && 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 "pia-vendor-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/pia-vendor-processing into .cursor/skills/pia-vendor-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pia-vendor-processing", 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/pia-vendor-processing--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 pia-vendor-processing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills pia-vendor-processing --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/pia-vendor-processing .gemini/skills/pia-vendor-processing && 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 "pia-vendor-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/pia-vendor-processing into .gemini/skills/pia-vendor-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pia-vendor-processing", 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 pia-vendor-processingInstalls 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 pia-vendor-processing -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/pia-vendor-processing .github/skills/pia-vendor-processing && 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 "pia-vendor-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/pia-vendor-processing into .github/skills/pia-vendor-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pia-vendor-processing", 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 pia-vendor-processing -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 pia-vendor-processing --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/pia-vendor-processing .opencode/skills/pia-vendor-processing && 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 "pia-vendor-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/pia-vendor-processing into .opencode/skills/pia-vendor-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pia-vendor-processing", 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
pia-vendor-processing- GitHub stars
- 295
- Token cost
- ~2k tokens
- SKILL.md length
- 911 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 278
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Conducts Privacy Impact Assessment for vendor and third-party data processing arrangements.
- Works in 5 steps: Vendor Inventory and Classification… → Due Diligence Assessment (Week 2) → Data Processing Agreement Review (Week 3) → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Regulatory Framework, Vendor Risk Categories and PIA Methodology for Vendor…, plus 1 more section
- Runs Python scripts from its folder
What it does
Pia Vendor Processing is an agent skill from mukul975/Privacy-Data-Protection-Skills. Conducts Privacy Impact Assessment for vendor and third-party data processing arrangements. Covers processor due diligence, Data Processing Agreement (DPA) requirements under GDPR Article 28, sub-processor management, cross-border vendor transfers, cloud service provider assessments, and ongoing vendor monitoring. Keywords: vendor PIA, processor assessment, DPA, Article 28, sub-processor, cloud privacy, third-party risk.
Its SKILL.md is about 2k 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 Privacy and GDPR and Fundraising and pitch decks. 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 Privacy and GDPR
- Tasks that involve Fundraising and pitch decks
Example prompts
- “Use the pia-vendor-processing skill to conduct Privacy Impact Assessment for vendor and third-party data processing arrangements”
- “/pia-vendor-processing”
Requirements
- Python 3
Workflow steps
5 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
Pia Vendor Processing loads about 2k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 911 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). 911 words, ~1,969 tokens.
Download SKILL.mdSave it as
.claude/skills/pia-vendor-processing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- pia-vendor-processing
- description
- Conducts Privacy Impact Assessment for vendor and third-party data processing arrangements. Covers processor due diligence, Data Processing Agreement (DPA) requirements under GDPR Article 28, sub-processor management, cross-border vendor transfers, cloud service provider assessments, and ongoing vendor monitoring. Keywords: vendor PIA, processor assessment, DPA, Article 28, sub-processor, cloud privacy, third-party risk.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- privacy-impact-assessment
- metadata.tags
- vendor-pia, processor-assessment, dpa, article-28, sub-processor, cloud-privacy
Privacy Impact Assessment for Vendor Processing
Overview
When a controller engages a processor (vendor) to process personal data on its behalf, GDPR Article 28 imposes specific obligations on the controller to ensure that the processor provides sufficient guarantees to implement appropriate technical and organisational measures. The EDPB has repeatedly emphasized that the controller remains accountable for the processing regardless of delegation to a vendor. This skill provides a structured PIA methodology for assessing and managing the privacy risks of vendor data processing arrangements.
Regulatory Framework
GDPR Article 28 — Processor Obligations
| Requirement | Description |
|---|---|
| Art. 28(1) | Controller shall use only processors providing sufficient guarantees |
| Art. 28(2) | Processor shall not engage another processor (sub-processor) without prior specific or general written authorisation |
| Art. 28(3) | Processing governed by a contract or legal act setting out subject matter, duration, nature, purpose, data types, categories of data subjects, and controller obligations/rights |
| Art. 28(3)(a)-(h) | Mandatory DPA clauses: process only on documented instructions, confidentiality, security measures, sub-processor conditions, assist with data subject rights, assist with security/breach/DPIA, delete or return data, provide audit information |
| Art. 28(4) | Sub-processor must be bound by the same data protection obligations |
| Art. 28(5) | Adherence to approved codes of conduct or certification (Art. 42) as elements to demonstrate sufficient guarantees |
Processor Selection Criteria (EDPB Guidance)
The controller must assess the processor's:
- Technical expertise and security measures
- Track record and reputation (including enforcement history)
- Ability to ensure data subject rights can be exercised
- Data location and cross-border transfer implications
- Sub-processor chain management capability
- Business continuity and data recovery capability
- Willingness to submit to audits
Vendor Risk Categories
| Risk Category | Examples | Risk Level |
|---|---|---|
| Cloud infrastructure (IaaS/PaaS) | AWS, Azure, GCP — hosting personal data | High (data at rest and in transit under vendor control) |
| SaaS applications | CRM, HRIS, email marketing — processing personal data in vendor application | High (vendor application logic and access controls) |
| Analytics providers | Website analytics, marketing attribution — processing behavioural data | Medium-High (data sharing, profiling, cookie compliance) |
| IT support / managed services | Helpdesk, system administration — access to personal data during support | Medium (access-based risk, not purpose-based) |
| Payment processors | Card processing, billing — financial personal data | High (PCI DSS intersection, financial data sensitivity) |
| Sub-processors | Vendor's own vendors processing controller's data | High (reduced visibility and control) |
PIA Methodology for Vendor Processing
Phase 1: Vendor Inventory and Classification (Week 1)
- Inventory all vendors processing personal data on behalf of the organisation.
- For each vendor, document: personal data categories processed, data subject categories, processing purposes, data volumes, data locations.
- Classify each vendor by risk category based on data sensitivity, processing scope, and access level.
- Identify the vendor's sub-processors and their roles.
- Determine cross-border transfer implications for each vendor.
Phase 2: Due Diligence Assessment (Week 2)
- Request and review the vendor's security certifications (ISO 27001, SOC 2, CSA STAR).
- Review the vendor's privacy certifications and GDPR compliance evidence (ISO 27701, APEC CBPR).
- Check the vendor's enforcement history with supervisory authorities.
- Assess the vendor's technical and organisational security measures against the controller's requirements.
- Evaluate the vendor's data breach notification capability and track record.
- Review the vendor's sub-processor management process.
- Assess the vendor's ability to assist with data subject rights requests.
Show full SKILL.md (386 more words)Show less
Phase 3: Data Processing Agreement Review (Week 3)
- Verify the DPA covers all Art. 28(3) mandatory provisions.
- Check that processing instructions are specific and documented (not generic catch-all clauses).
- Verify sub-processor authorisation mechanism: specific or general with notification and objection rights.
- Ensure data deletion or return obligations at contract termination are clear and enforceable.
- Verify audit rights: right to conduct or commission audits of the processor.
- Check cross-border transfer mechanisms (SCCs, BCRs, adequacy) for international vendors.
- Assess liability and indemnification provisions for data protection breaches.
Phase 4: Risk Assessment and Mitigation (Week 4)
- For each vendor, assess the risk to data subjects from the vendor's processing.
- Consider: data breach at vendor, unauthorised access by vendor employees, sub-processor chain risk, vendor lock-in, business continuity failure.
- Score risks on likelihood and severity matrix.
- Identify mitigation measures: encryption (controller-managed keys), pseudonymisation before transfer to vendor, access restrictions, monitoring, contractual controls.
- Assess residual risk after mitigation.
Phase 5: Ongoing Monitoring Framework (Week 5)
- Define vendor review frequency based on risk classification (high-risk: annual; medium: biennial).
- Establish vendor security questionnaire process for periodic reassessment.
- Monitor vendor sub-processor changes (notification process, assessment of new sub-processors).
- Track vendor incidents and breach notifications.
- Conduct or commission periodic audits for high-risk vendors.
- Define vendor exit strategy: data return, deletion verification, transition plan.
Enforcement Precedents
- CJEU Wirtschaftsakademie (C-210/16, 2018): Facebook fan page administrator held to be joint controller with Facebook; controllers cannot avoid responsibility by using a vendor platform.
- CJEU Fashion ID (C-40/17, 2019): Website operator embedding Facebook Like button held to be joint controller for the collection and transmission of data; responsibility for vendor components on own website.
- Belgian DPA vs IAB Europe (2022): EUR 250,000 fine; TCF framework operator held to be controller, not processor; demonstrates that contractual designation does not determine controller/processor status.
- Spanish AEPD vs Vodafone (2021): EUR 8.15 million fine for failure to adequately manage processors and sub-processors handling customer data; insufficient DPA controls.
- Finnish DPA vs Posti Group (2020): EUR 100,000 fine for inadequate processor management; controller failed to verify processor's compliance with data processing instructions.
- Dutch DPA guidance on cloud services (2022): Detailed assessment methodology for cloud vendor privacy compliance, including requirement to conduct DPIA for cloud migrations involving personal data.
© 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/pia-vendor-processing 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
Pia Vendor Processing 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 |
|---|---|---|---|---|---|---|
| Pia Vendor Processing this skillmukul975/Privacy-Data-Protection-Skills | 295 | — | ~2k | 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 | 942 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Cross Regulatory Impact Analyzer Patrick Munrolawve-ai/awesome-legal-skills | 836 | — | ~3.1k | Automated safety check: Pass | AGPL-3.0 | |
| Vendor Due Diligence Patrick Munrolawve-ai/awesome-legal-skills | 836 | — | ~4.1k | Automated safety check: Pass | AGPL-3.0 | |
| Preparing Launch AssetsGTM-Strategist/gtm-strategist-skills | 261 | — | ~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 278 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.
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.
Retention Schedule
mukul975/Privacy-Data-Protection-Skills
Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.
Related
Categories
Questions about Pia Vendor Processing
What does Pia Vendor Processing do?
Conducts Privacy Impact Assessment for vendor and third-party data processing arrangements. Pia Vendor Processing is an agent skill from mukul975/Privacy-Data-Protection-Skills. Conducts Privacy Impact Assessment for vendor and third-party data processing arrangements.
When should I use Pia Vendor Processing?
Pia Vendor Processing fits situations like: tasks that involve Privacy and GDPR; tasks that involve Fundraising and pitch decks.
How do I install Pia Vendor Processing in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill pia-vendor-processing -a claude-code`. Or copy the skill folder (skills/privacy/pia-vendor-processing in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/pia-vendor-processing in your project. Claude Code loads it when a task matches its description.
How do I install Pia Vendor Processing in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill pia-vendor-processing -a codex`. Or copy the skill folder (skills/privacy/pia-vendor-processing in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/pia-vendor-processing in your project. Codex loads it when a task matches its description.
Can I use Pia Vendor Processing 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 pia-vendor-processing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pia-vendor-processing, .gemini/skills/pia-vendor-processing, .github/skills/pia-vendor-processing and .opencode/skills/pia-vendor-processing in your project.
What does Pia Vendor Processing need to run?
Going by SKILL.md and its folder, Pia Vendor Processing needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Pia Vendor Processing 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 Pia Vendor Processing 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 Pia Vendor Processing use?
Pia Vendor Processing 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 Pia Vendor Processing use?
About 2k tokens (SKILL.md is roughly 7.9k 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.7k tokens, read only when the agent opens those files.
What are the alternatives to Pia Vendor Processing?
Skills that share tags, products or a category with Pia Vendor Processing: General Counsel Advisor (alirezarezvani/claude-skills, 28k stars), Tprm (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 942 stars), Cross Regulatory Impact Analyzer Patrick Munro (lawve-ai/awesome-legal-skills, 836 stars) and Vendor Due Diligence Patrick Munro (lawve-ai/awesome-legal-skills, 836 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pia Vendor Processing?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 295 GitHub stars. The repository holds 278 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.