pia-generation

Generate a Privacy Impact Assessment in house format for a new feature, product, or processing activity, using the structure learned from your seed PIA. Use when the user says "write a PIA", "privacy impact assessment for", "do we need a PIA for this", "privacy review this feature", or describes a new data processing activity.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a complete PIA template, strong validation checkpoints, and useful feedback loops, but it is a long monolithic single file with inline material that could be split into references and some repetitive config-path phrasing.

Suggestions

Move the full PIA markdown template and the intake question bank into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Tighten the repeated '~/.claude/plugins/config/claude-for-legal/privacy-legal/CLAUDE.md' path references by defining the path once and referring to it with a short alias.

Consider a brief table of contents or explicit step ordering between the top-level numbered workflow and the topical sections below it so the overall flow is easier to follow.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows and gives genuinely domain-specific guidance, but at ~283 lines it repeats config-CLAUDE.md path references and could be tightened, matching the score-2 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides a copy-paste-ready fill-in PIA markdown template, exact source-attribution tag formats ('[Westlaw]', '[web search — verify]'), specific intake questions, and concrete routing commands, matching the score-3 'fully executable' anchor.	3 / 3
Workflow Clarity	The body has a numbered workflow with explicit validation checkpoints ('Verify currency', prior-output reconciliation), a feedback loop ('No silent supplement' → stop and ask), and a regulator-submission gate requiring an explicit yes, matching the score-3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist and the body is a well-sectioned but monolithic ~283-line document with the PIA template and intake question bank kept inline that could be split into reference files, matching the score-2 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, answers both what and when with an explicit Use-when clause, and packs several natural trigger phrases. Its only weakness is that it describes essentially one action rather than a list of multiple concrete actions, capping specificity at 2.

Dimension	Reasoning	Score
Specificity	It names the domain and one concrete action — 'Generate a Privacy Impact Assessment in house format for a new feature, product, or processing activity' — but lists a single action rather than multiple specific concrete actions, matching the score-2 anchor.	2 / 3
Completeness	It clearly answers both what (generate a PIA in house format) and when with an explicit 'Use when the user says…' trigger clause, matching the score-3 anchor.	3 / 3
Trigger Term Quality	It gives good coverage of natural phrases users would say — 'write a PIA', 'privacy impact assessment for', 'do we need a PIA for this', 'privacy review this feature' — matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	PIA generation is a clear niche with distinct triggers ('write a PIA', 'privacy impact assessment'), unlikely to conflict with other skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: anthropics/claude-for-legal
Path: privacy-legal/skills/pia-generation/SKILL.md
Commit: 4a6c651

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.