Conduct comprehensive GDPR compliance assessments by evaluating data processing activities against EU Regulation 2016/679, including Article 30 records of processing, lawful basis validation, data subject rights implementation, Data Protection Impact Assessments (DPIAs) under Article 35, breach notification procedures, international transfer safeguards (SCCs, adequacy decisions), and technical/organizational measures under Article 32. Use when processing personal data of EU residents, preparing for supervisory authority audits, implementing privacy-by-design for new systems, scoping compliance gaps for M&A due diligence, assessing third-party processors, or responding to data subject access requests at scale. Incorporates 2026 guidance from ICO, EDPB, and post-Data (Use and Access) Act 2025 UK-GDPR considerations. Do not use for implementing specific Article 32 controls — use implementing-gdpr-data-protection-controls; or for DSAR automation — use implementing-gdpr-data-subject-access-request.
The author's original description, preserved in English. It describes intent, not verified performance.
Conduct comprehensive GDPR compliance assessments by evaluating data processing activities against EU Regulation 2016/679, including Article 30 records of processing, lawful basis validation, data subject rights implementation, Data Protection Impact Assessments (DPIAs) under Article 35, breach notification procedures, international transfer safeguards (SCCs, adequacy decisions), and technical/organizational measures under Article 32. Use when processing personal data of EU residents, preparing for supervisory authority audits, implementing privacy-by-design for new systems, scoping compliance gaps for M&A due diligence, assessing third-party processors, or responding to data subject access requests at scale. Incorporates 2026 guidance from ICO, EDPB, and post-Data (Use and Access) Act 2025 UK-GDPR considerations. Do not use for implementing specific Article 32 controls — use implementing-gdpr-data-protection-controls; or for DSAR automation — use implementing-gdpr-data-subject-access-request.
developmentreferencesscripts
01 / OVERVIEW
Research summary
Machine-generated analysis; pending human review
These observations come from deterministic source parsing, not a human security review or controlled task evaluation.
Conduct comprehensive GDPR compliance assessments by evaluating data processing activities against EU Regulation 2016/679, including Article 30 records of processing, lawful basis validation, data subject rights implementation, Data Protection Impact Assessments (DPIAs) under Article 35, breach notification procedures, international transfer safeguards (SCCs, adequacy decisions), and technical/organizational measures under Article 32. Use when processing personal data of EU residents, preparing for supervisory authority audits, implementing privacy-by-design for new systems, scoping compliance gaps for M&A due diligence, assessing third-party processors, or responding to data subject access requests at scale. Incorporates 2026 guidance from ICO, EDPB, and post-Data (Use and Access) Act 2025 UK-GDPR considerations. Do not use for implementing specific Article 32 controls — use implementing-gdpr-data-protection-controls; or for DSAR automation — use implementing-gdpr-data-subject-access-request. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.
Review scope
Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.
Observable capabilities
Workflow [Source statement; provisional, not tested. Evidence: skills/conducting-gdpr-compliance-assessment/SKILL.md:L77]
Phase 2: Inventory Data Processing Activities (Article 30) [Source statement; provisional, not tested. Evidence: skills/conducting-gdpr-compliance-assessment/SKILL.md:L90]
Limitations & scope
Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
No commands, scripts, network requests, model calls, or controlled skill executions were performed.
Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.
Relevant for
Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/conducting-gdpr-compliance-assessment/SKILL.md:L1-L44]
02 / STRUCTURE
What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
{
"name": "conducting-gdpr-compliance-assessment",
"description": "Conduct comprehensive GDPR compliance assessments by evaluating data processing activities against EU Regulation 2016/679, including Article 30 records of processing, lawful basis validation, data subject rights implementation, Data Protection Impact Assessments (DPIAs) under Article 35, breach notification procedures, international transfer safeguards (SCCs, adequacy decisions), and technical/organizational measures under Article 32. Use when processing personal data of EU residents, preparing for supervisory authority audits, implementing privacy-by-design for new systems, scoping compliance gaps for M&A due diligence, assessing third-party processors, or responding to data subject access requests at scale. Incorporates 2026 guidance from ICO, EDPB, and post-Data (Use and Access) Act 2025 UK-GDPR considerations. Do not use for implementing specific Article 32 controls — use implementing-gdpr-data-protection-controls; or for DSAR automation — use implementing-gdpr-data-subject-access-request.",
"domain": "cybersecurity",
"subdomain": "compliance-governance",
"tags": [
"gdpr",
"data-protection",
"privacy",
"compliance",
"dpia",
"data-subject-rights",
"article-30",
"controller",
"processor",
"eu-regulation",
"ico",
"supervisory-authority"
],
"version": "1.0",
"author": "dakshverma23",
"license": "Apache-2.0",
"nist_csf": [
"GV.OC-02",
"GV.PO-01",
"GV.RM-04",
"PR.DS-01",
"PR.DS-02",
"ID.AM-05"
],
"mitre_attack": [
"T1530",
"T1567"
]
}
03 / WORKFLOW
A reading of the operating sequence
This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.
01
Decision
When to Use
Source-described decision candidate under “When to Use”; not verified execution.
Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.
Attention recommended
49 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.
Network accessObserved
File writesObserved
Credential useObserved
Note
File modification is described or implemented
24 occurrences
This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 24 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 22 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.
Exact token counts unavailable
All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.
No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.
06 / EVALUATION
Controlled evaluation
No controlled evaluation
This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.
Not tested
07 / USAGE
Use with the source in view
Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/conducting-gdpr-compliance-assessment/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.
Prerequisites
Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
No commands, scripts, network requests, model calls, or controlled skill executions were performed.
Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.
Example prompts
Not provided
08 / VERDICT
A decision, with its limits attached
Strengths
The snapshot contains 9 collected file(s), 5 Markdown file(s), and 3 script file(s), enabling source-level inspection. [Evidence: skills/conducting-gdpr-compliance-assessment/SKILL.md:L1]
Considerations
No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion
Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.
09 / PROVENANCE
Traceable by construction
The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.
Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.