Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
Vendor certification acceptance criteria and equivalence mapping.
Install Vendor Cert Acceptance
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill vendor-cert-acceptance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-cert-acceptance --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/vendor-cert-acceptance .claude/skills/vendor-cert-acceptance && 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 "vendor-cert-acceptance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-cert-acceptance into .claude/skills/vendor-cert-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-cert-acceptance", 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/vendor-cert-acceptanceType 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 vendor-cert-acceptance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-cert-acceptance --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/vendor-cert-acceptance .agents/skills/vendor-cert-acceptance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vendor-cert-acceptance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-cert-acceptance into .agents/skills/vendor-cert-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-cert-acceptance", 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 vendor-cert-acceptance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-cert-acceptance --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/vendor-cert-acceptance .cursor/skills/vendor-cert-acceptance && 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 "vendor-cert-acceptance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-cert-acceptance into .cursor/skills/vendor-cert-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-cert-acceptance", 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/vendor-cert-acceptance--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 vendor-cert-acceptance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills vendor-cert-acceptance --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/vendor-cert-acceptance .gemini/skills/vendor-cert-acceptance && 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 "vendor-cert-acceptance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-cert-acceptance into .gemini/skills/vendor-cert-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-cert-acceptance", 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 vendor-cert-acceptanceInstalls 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 vendor-cert-acceptance -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/vendor-cert-acceptance .github/skills/vendor-cert-acceptance && 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 "vendor-cert-acceptance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-cert-acceptance into .github/skills/vendor-cert-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-cert-acceptance", 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 vendor-cert-acceptance -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 vendor-cert-acceptance --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/vendor-cert-acceptance .opencode/skills/vendor-cert-acceptance && 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 "vendor-cert-acceptance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/vendor-cert-acceptance into .opencode/skills/vendor-cert-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-cert-acceptance", 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
vendor-cert-acceptance- GitHub stars
- 301
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,141 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Vendor certification acceptance criteria and equivalence mapping.
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Recognized Certification…, Certification Equivalence Matrix and Gap Supplementation Requirements, plus 2 more sections
- Runs Python scripts from its folder
- Tasks that involve User stories
What it does
Vendor Cert Acceptance is an agent skill from mukul975/Privacy-Data-Protection-Skills. Vendor certification acceptance criteria and equivalence mapping. Covers ISO 27701, SOC 2 Privacy, APEC CBPR, EU Code of Conduct evaluation, certification scope analysis, gap supplementation requirements, and cross-framework equivalence assessment.
Its SKILL.md is about 2.7k 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, User stories and SOC 2 and security compliance. 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 User stories
- Tasks that involve SOC 2 and security compliance
Example prompts
- “/vendor-cert-acceptance”
Requirements
- Python 3
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
Vendor Cert Acceptance loads about 2.7k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 1,141 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). 1,141 words, ~2,695 tokens.
Download SKILL.mdSave it as
.claude/skills/vendor-cert-acceptance/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- vendor-cert-acceptance
- description
- Vendor certification acceptance criteria and equivalence mapping. Covers ISO 27701, SOC 2 Privacy, APEC CBPR, EU Code of Conduct evaluation, certification scope analysis, gap supplementation requirements, and cross-framework equivalence assessment.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- vendor-privacy-management
- metadata.tags
- vendor-certification, iso-27701, soc-2-privacy, apec-cbpr, certification-equivalence
Vendor Certification Acceptance Criteria
Overview
GDPR Article 42 establishes a framework for data protection certification mechanisms, and Article 28(5) notes that a processor's adherence to an approved certification mechanism may be used as an element to demonstrate sufficient guarantees. The EDPB Guidelines 07/2020 (paragraph 86) confirm that certifications may serve as indicators of processor reliability, though they do not discharge the controller's obligation to conduct its own assessment.
Vendor certifications and attestations provide structured evidence of control implementation, but their value depends on scope coverage, certification body credibility, recency, and relevance to the specific processing relationship. Summit Cloud Partners maintains a Certification Acceptance Framework that defines which certifications are recognized, how they are evaluated, and what supplementary measures are needed when certification coverage has gaps.
Recognized Certification Frameworks
Tier A: Strong Privacy Certifications
Certifications specifically designed for privacy/data protection management, independently audited.
ISO/IEC 27701:2019 — Privacy Information Management System (PIMS)
| Aspect | Detail |
|---|---|
| Standard | Extension to ISO 27001/27002 for PII management |
| Scope | PII controller (Annex A) and PII processor (Annex B) controls |
| Certification body | Accredited ISO certification bodies |
| Audit type | Third-party certification audit (Stage 1 + Stage 2) |
| Validity | 3-year cycle with annual surveillance audits |
| GDPR relevance | High — maps directly to GDPR requirements per Annex D |
| Acceptance criteria | Certificate scope must cover processing services provided to Summit |
| Verification | Check accreditation body registry; verify scope statement |
| Supplementation needed | Verify that Annex B (processor) controls are in scope; if only Annex A (controller), supplementary processor assessment required |
GDPR Certification per Article 42
| Aspect | Detail |
|---|---|
| Standard | Certification per criteria approved by supervisory authority or EDPB |
| Certification body | Accredited per Article 43 by national accreditation body and supervisory authority |
| GDPR relevance | Maximum — specifically designed for GDPR compliance demonstration |
| Acceptance criteria | Certificate issued by Article 43 accredited body; scope covers processing |
| Current status | Very few Article 42 certifications currently available (as of March 2026) |
| Supplementation needed | Minimal if scope covers all processing activities |
Tier B: Strong Security Certifications with Privacy Elements
Certifications primarily security-focused but including privacy-relevant controls.
SOC 2 Type II with Privacy Trust Services Criterion
| Aspect | Detail |
|---|---|
| Standard | AICPA Trust Services Criteria — Privacy criterion |
| Scope | Notice, choice, collection, use/retention/disposal, access, disclosure, security, quality, monitoring |
| Audit type | Independent CPA examination over minimum 6-month period |
| GDPR relevance | Moderate-High — covers many Article 28/32 requirements but US-centric |
| Acceptance criteria | Type II (not Type I); Privacy criterion included; no qualified opinions; scope covers relevant services |
| Verification | Request full report under NDA; review scope, findings, exceptions |
| Supplementation needed | GDPR-specific gap assessment required: cross-border transfer controls, DPA-specific obligations, sub-processor cascade |
SOC 2 Type II (Security Criterion Only)
| Aspect | Detail |
|---|---|
| Acceptance criteria | Type II; no qualified opinions; scope covers relevant services |
| GDPR relevance | Moderate — covers Article 32 security measures |
| Supplementation needed | Full privacy assessment required for non-security GDPR obligations |
ISO/IEC 27001:2022 — Information Security Management System
| Aspect | Detail |
|---|---|
| Acceptance criteria | Current version (2022 preferred); scope covers processing services; accredited certification body |
| GDPR relevance | Moderate — strong for Article 32 security; does not address privacy-specific requirements |
| Supplementation needed | Privacy gap assessment covering Art. 28(3) obligations, DSR assistance, breach notification, data handling |
Tier C: Domain-Specific Certifications
ISO/IEC 27018:2019 — Cloud Privacy
| Aspect | Detail |
|---|---|
| Scope | Cloud-specific PII protection controls |
| Acceptance | Relevant only for cloud service providers; supplements ISO 27001 |
| Supplementation | Must be combined with ISO 27001; does not stand alone |
CSA STAR Level 2 — Cloud Security
| Aspect | Detail |
|---|---|
| Scope | Cloud Controls Matrix (CCM) third-party audit |
| Acceptance | Level 2 (third-party audit) required; Level 1 (self-assessment) insufficient as standalone |
| Supplementation | Cloud security focus; privacy gap assessment required |
APEC Cross-Border Privacy Rules (CBPR) System
| Aspect | Detail |
|---|---|
| Scope | Asia-Pacific cross-border data transfer framework |
| Acceptance | Recognized for APEC economy vendors; does not substitute for GDPR compliance |
| GDPR relevance | Limited — different legal framework; may indicate privacy program maturity |
| Supplementation | Full GDPR compliance assessment still required |
EU Cloud Code of Conduct (SCOPE Europe)
| Aspect | Detail |
|---|---|
| Standard | GDPR Article 40 approved code of conduct for cloud services |
| Scope | Cloud service provider GDPR compliance |
| Acceptance | Approved by Belgian DPA as monitoring body (2021) |
| GDPR relevance | High — specifically mapped to GDPR obligations |
| Supplementation | Minimal for in-scope cloud processing; verify monitoring body oversight |
Show full SKILL.md (469 more words)Show less
Tier D: Self-Assessments and Basic Certifications
| Certification | Acceptance Level |
|---|---|
| CSA STAR Level 1 (self-assessment) | Accepted as supplementary evidence only; not standalone |
| Vendor privacy policy / self-declaration | Not accepted as certification; supplementary only |
| HITRUST CSF | Accepted for healthcare contexts; GDPR gap assessment required |
| Cyber Essentials (UK) | Basic security only; full assessment required |
Certification Equivalence Matrix
Maps certification coverage against GDPR Article 28 requirements:
| GDPR Requirement | ISO 27701 | SOC 2 Privacy | SOC 2 Security | ISO 27001 | ISO 27018 | Art. 42 Cert |
|---|---|---|---|---|---|---|
| Art. 28(3)(a) Documented instructions | Full | Partial | None | None | Full | Full |
| Art. 28(3)(b) Confidentiality | Full | Full | Partial | Full | Full | Full |
| Art. 28(3)(c) Security (Art. 32) | Full | Full | Full | Full | Full | Full |
| Art. 28(3)(d) Sub-processor mgmt | Full | Partial | None | Partial | Full | Full |
| Art. 28(3)(e) DSR assistance | Full | Partial | None | None | Partial | Full |
| Art. 28(3)(f) Compliance assistance | Full | Partial | None | None | None | Full |
| Art. 28(3)(g) Deletion/return | Full | Full | None | Partial | Full | Full |
| Art. 28(3)(h) Audit rights | Full | Partial | None | Partial | Full | Full |
| Art. 33(2) Breach notification | Full | Full | Partial | Partial | Partial | Full |
| Ch. V International transfers | Partial | None | None | None | None | Full |
Legend: Full = requirement addressed, Partial = partially addressed, None = not addressed
Gap Supplementation Requirements
When a vendor holds certifications that do not fully cover GDPR requirements, Summit Cloud Partners requires supplementary evidence for uncovered obligations:
| Gap | Supplementation Method |
|---|---|
| DSR assistance capability | Vendor provides DSR handling procedure documentation and SLA commitments |
| Sub-processor management | Vendor provides sub-processor list, notification mechanism, and flow-down DPA sample |
| Breach notification process | Vendor provides incident response plan with notification timeframes |
| International transfer controls | Vendor provides Transfer Impact Assessment and supplementary measures documentation |
| Deletion/return capabilities | Vendor demonstrates deletion procedure and provides sample deletion certificate |
| Audit facilitation | DPA audit rights clause verified; vendor confirms practical audit access |
Certification Verification Process
| Step | Activity | Evidence |
|---|---|---|
| 1 | Obtain copy of certificate and audit report | PDF certificate; SOC 2 report under NDA |
| 2 | Verify certification body accreditation | Check national accreditation body registry |
| 3 | Verify certificate validity (not expired) | Certificate dates; annual surveillance confirmation |
| 4 | Verify scope covers relevant services | Scope statement includes services provided to Summit |
| 5 | Review exceptions or qualified opinions (SOC 2) | No material exceptions affecting Summit data |
| 6 | Identify gaps per equivalence matrix | Document uncovered requirements |
| 7 | Request supplementary evidence for gaps | Per gap supplementation table |
| 8 | Document acceptance decision | Record in vendor assessment file |
Key Regulatory References
- GDPR Article 42 — Data protection certification mechanisms
- GDPR Article 43 — Certification bodies
- GDPR Article 40 — Codes of conduct
- GDPR Article 28(5) — Adherence to certifications as element of sufficient guarantees
- EDPB Guidelines 07/2020 — Paragraph 86 on certifications as sufficiency indicators
- EDPB Guidelines 1/2018 — Certification and identifying certification criteria per Article 42
- ISO/IEC 27701:2019 — Privacy information management system
- AICPA Trust Services Criteria — Privacy criterion (2017 revision with 2022 updates)
- APEC Cross-Border Privacy Rules System — Policies, Rules, and Guidelines
- EU Cloud Code of Conduct — SCOPE Europe (approved 2021)
© 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/vendor-cert-acceptance 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
Vendor Cert Acceptance 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 |
|---|---|---|---|---|---|---|
| Vendor Cert Acceptance this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Pii Contract Analyzegregmos/PII-Shield | 150 | — | ~8.9k | Automated safety check: Notes | MIT | |
| Privacy Eukimlawtech/korean-privacy-terms | 587 | — | ~968 | Automated safety check: Pass | Apache-2.0 | |
| Nist 800 53Sushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Audit Reportharness/harness-skills | 115 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Terms Of Service Generatorzubair-trabzada/ai-legal-claude | 1.8k | — | ~2.9k | Automated safety check: Pass | None |
Similar skills
Privacy Eu
kimlawtech/korean-privacy-terms
EU 사용자 대상 서비스용 Privacy Notice·Terms of Service·Consent Modal·Cookie Banner 자동 생성.
Nist 800 53
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200…
Audit Report
harness/harness-skills
Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.
Terms Of Service Generator
zubair-trabzada/ai-legal-claude
Generates complete, GDPR/CCPA-compliant Terms of Service for a website or SaaS product, with plain English summaries for each section
Cis Controls
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert CIS Controls v8 (CIS Top 18) advisor — implementation group scoping (IG1/IG2/IG3), control gap assessments, safeguard-level guidance, asset inventory, software inventory, data protection…
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 Vendor Cert Acceptance
What does Vendor Cert Acceptance do?
Vendor certification acceptance criteria and equivalence mapping. Vendor Cert Acceptance is an agent skill from mukul975/Privacy-Data-Protection-Skills. Vendor certification acceptance criteria and equivalence mapping.
When should I use Vendor Cert Acceptance?
Vendor Cert Acceptance fits situations like: tasks that involve Privacy and GDPR; tasks that involve User stories; tasks that involve SOC 2 and security compliance.
How do I install Vendor Cert Acceptance in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill vendor-cert-acceptance -a claude-code`. Or copy the skill folder (skills/privacy/vendor-cert-acceptance in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/vendor-cert-acceptance in your project. Claude Code loads it when a task matches its description.
How do I install Vendor Cert Acceptance in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill vendor-cert-acceptance -a codex`. Or copy the skill folder (skills/privacy/vendor-cert-acceptance in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/vendor-cert-acceptance in your project. Codex loads it when a task matches its description.
Can I use Vendor Cert Acceptance 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 vendor-cert-acceptance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vendor-cert-acceptance, .gemini/skills/vendor-cert-acceptance, .github/skills/vendor-cert-acceptance and .opencode/skills/vendor-cert-acceptance in your project.
What does Vendor Cert Acceptance need to run?
Going by SKILL.md and its folder, Vendor Cert Acceptance needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Vendor Cert Acceptance 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 Vendor Cert Acceptance 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 Vendor Cert Acceptance use?
Vendor Cert Acceptance 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 Vendor Cert Acceptance use?
About 2.7k tokens (SKILL.md is roughly 11k 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 2.7k tokens, read only when the agent opens those files.
What are the alternatives to Vendor Cert Acceptance?
Skills that share tags, products or a category with Vendor Cert Acceptance: Pii Contract Analyze (gregmos/PII-Shield, 150 stars), Privacy Eu (kimlawtech/korean-privacy-terms, 587 stars), Nist 800 53 (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars) and Audit Report (harness/harness-skills, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vendor Cert Acceptance?
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.