use-case-triage

Quickly determine whether a processing activity needs a PIA, a mandatory GDPR DPIA, or can proceed — surfaces privacy policy conflicts and routes to the right next step. Use when the user asks "does this need a PIA", "triage this feature", "privacy check on X", "is this okay from a privacy perspective", or describes a new data processing activity, product feature, or vendor relationship.

Quality

88%

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.

A well-sequenced, highly actionable triage workflow with strong validation checkpoints and feedback loops. Its main weaknesses are some explanatory padding Claude could infer and a monolithic structure with no progressive disclosure into separate bundle files.

Suggestions

Tighten inferable rationale: condense the CCPA-exemption/GLBA mechanics explanation and trim the verbose blockquoted bounce messages to only the user-facing essentials.

Split the monolithic body: move the federal-overlay reference detail, the full output/conditions templates, and the edge-case catalog into one-level-deep reference files (e.g., references/federal-overlays.md, references/output-templates.md) with clearly signaled links from SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and purposeful, but includes explanatory rationale Claude can infer (e.g., the restated CCPA §1798.145(e)/GLBA exemption mechanics, verbose blockquoted bounce messages) that could be tightened.	2 / 3
Actionability	Provides concrete, executable guidance: named config paths, a six-step triage with explicit trigger checks, a full output template, a conditions table, and copy-ready handoff commands like /privacy-legal:pia-generation.	3 / 3
Workflow Clarity	Clear sequenced workflow (understand → house triggers → mandatory check → policy conflict → classification → handoffs) with explicit validation checkpoints: read-config-first, surface a bounce on [PLACEHOLDER], researched-trigger → DPIA, policy-conflict → STOP.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the ~290-line body is monolithic; the federal-overlay detail, output templates, and edge cases are all inline rather than split into one-level-deep referenced files.	2 / 3
	Total	10 / 12 Passed

Description

100%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 exemplary: it states concrete capabilities, provides explicit natural-language triggers covering multiple phrasings, answers both 'what' and 'when', and occupies a distinct niche. It is third-person, concise, and free of fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'determine whether a processing activity needs a PIA, a mandatory GDPR DPIA, or can proceed', 'surfaces privacy policy conflicts', and 'routes to the right next step'.	3 / 3
Completeness	Explicitly answers both what it does (PIA/DPIA/proceed determination, conflict surfacing, routing) and when to use it via a clear 'Use when the user asks...' trigger clause.	3 / 3
Trigger Term Quality	Quotes natural phrasings users would actually say — 'does this need a PIA', 'triage this feature', 'privacy check on X', 'is this okay from a privacy perspective' — giving strong keyword coverage.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (privacy PIA/DPIA triage) with distinctive triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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/use-case-triage/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.