Legal Privacy Impact Assessment Guide

v1.0.0

Provides structured checklists, templates, and prompts to guide privacy teams in conducting legal privacy impact assessments and documenting reviews.

0· 49·1 current·1 all-time
byhaidong@harrylabsj

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for harrylabsj/legal-privacy-impact-assessment-guide.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Legal Privacy Impact Assessment Guide" (harrylabsj/legal-privacy-impact-assessment-guide) from ClawHub.
Skill page: https://clawhub.ai/harrylabsj/legal-privacy-impact-assessment-guide
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install legal-privacy-impact-assessment-guide

ClawHub CLI

Package manager switcher

npx clawhub@latest install legal-privacy-impact-assessment-guide
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (privacy impact assessment guidance) matches the contents: SKILL.md, README, and skill.json are all descriptive and focused on templates, checklists, and prompts. There are no unrelated permissions, binaries, or cloud credentials requested.
Instruction Scope
Runtime instructions are limited to asking for context/facts and producing checklists, memos, and matrices. The skill explicitly disclaims legal advice and forbids external calls, code execution, or retrieval of records. It does ask the user to supply facts/documents (which is appropriate for the task) — users should avoid pasting confidential or privileged material into an LLM.
Install Mechanism
No install spec and no code files are present (instruction-only). That is the lowest-risk install profile and consistent with the acceptance criteria in ACCEPTANCE.md.
Credentials
The package requests no environment variables, credentials, or config paths. This is proportionate for a descriptive, non-integrated guidance skill.
Persistence & Privilege
always is false and the default autonomous invocation is allowed (disable-model-invocation=false). This is the platform default and is not problematic here because the skill has no external access or credentials. The skill does not attempt to modify other skills or system settings.
Assessment
This skill is a document-only guide for running privacy impact assessments and appears internally consistent. It does not execute code or request credentials. Before using it, remember: (1) this is informational only and not legal advice — verify anything important with qualified counsel; (2) do not paste privileged, confidential, or sensitive data into the skill/agent prompts; (3) if you require the agent not to act autonomously, disable autonomous invocation in your agent settings even though this skill itself is harmless.

Like a lobster shell, security has layers — review code before you run it.

latestvk976m6appk063pdw1cf3d9fq0h85kmxt
49downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0

Legal Privacy Impact Assessment Guide

Overview

Guides privacy teams through data mapping, processing purposes, risks, safeguards, vendor issues, and privacy review documentation. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.

When to Use

  • Launching products using personal data
  • Assessing vendors
  • Documenting privacy reviews

Target Users

  • Privacy counsel
  • Data protection officers
  • Product legal teams
  • Compliance teams

Inputs to Collect

  • Matter or project context, including jurisdiction if known
  • Relevant facts, documents, parties, dates, and constraints
  • Desired output format, audience, and level of detail
  • Known deadlines, risk concerns, or review priorities

Core Modules

  1. Data inventory prompts — provides structured prompts, checklists, and review fields for this area.
  2. Purpose and lawful-basis fields — provides structured prompts, checklists, and review fields for this area.
  3. Risk and safeguard checklist — provides structured prompts, checklists, and review fields for this area.
  4. Vendor/data transfer considerations — provides structured prompts, checklists, and review fields for this area.
  5. Privacy review memo template — provides structured prompts, checklists, and review fields for this area.

Workflow

  1. Confirm the user's legal workflow goal and the relevant practice context.
  2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.
  3. Apply the modules below as a structured thinking framework.
  4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.
  5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.

Expected Outputs

  • PIA/DPIA-style checklist
  • Data flow summary
  • Risk/safeguard matrix
  • Review memo outline

Example Prompts

  • "Create a privacy impact assessment template for a mobile app."
  • "Help map privacy risks for a vendor using customer data."

Safety and Legal Limitations

  • This skill provides informational workflow support only and is not legal advice.
  • It does not create an attorney-client relationship and does not replace review by a qualified attorney.
  • Laws, court rules, deadlines, ethics duties, privilege, confidentiality, and professional responsibility rules vary by jurisdiction and matter.
  • Users must verify all legal authorities, filing requirements, deadlines, facts, citations, and strategic decisions with qualified counsel.
  • The skill must not be used to fabricate evidence, coach false testimony, evade regulation, access data unlawfully, or bypass confidentiality obligations.
  • Specific limitation for this skill: Privacy laws vary widely; this does not replace GDPR/CCPA/PIPL or local legal analysis.

Acceptance Criteria

  • Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.
  • SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.
  • Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.
  • Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.
  • skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.

Comments

Loading comments...