CtrlK
BlogDocsLog inGet started
Tessl Logo

privacy-engineering

Implement and audit privacy controls in product and infrastructure — GDPR, CCPA / CPRA, LGPD, PIPEDA. Covers data minimization, lawful basis, consent management, data subject access requests (DSARs — access, deletion, portability), data processing agreements, DPIA / TIA, breach notification timing, data classification, and the technical implementation of 'right to be forgotten' across backups, caches, analytics, and third parties. Use when the user mentions 'GDPR,' 'CCPA,' 'CPRA,' 'data privacy,' 'privacy engineering,' 'data subject access request,' 'DSAR,' 'right to deletion,' 'right to be forgotten,' 'data portability,' 'consent management,' 'cookie consent,' 'data minimization,' 'DPIA,' 'data protection impact assessment,' 'breach notification,' 'BAA,' 'DPA,' 'data processing agreement,' 'sub-processor,' 'cross-border data transfer,' 'SCCs,' or needs to implement or review privacy controls.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

A strong, practical audit skill with concrete grep patterns and a usable output template, weakened mainly by a reference-style structure that lacks a single validated workflow and by keeping all content inline in one long file rather than offloading detail to reference files.

Suggestions

Add a short sequenced 'Audit workflow' section (inventory → classify → minimization → DSAR simulation → report) with explicit validate/re-run checkpoints, so the eight practices hang together as one process rather than a reference list.

Move the grep-pattern catalogs and per-vendor DSAR deletion specifics into a references/ file (e.g. references/audit-patterns.md) and link to it from the body, reducing SKILL.md toward an overview and improving progressive disclosure.

Provide one or two concrete code snippets for the destructive core — e.g., a parameterized SQL soft-delete and a sample vendor deletion-API call — to close the actionability gap in the deletion fan-out.

DimensionReasoningScore

Conciseness

The body is dense and practical — tables, grep patterns, checklists, audit steps — with little concept padding, but the privacy-vs-security framing paragraphs and commentary sentences ('Engineering reality: build for the strictest regime...') could be trimmed, so it sits one notch below lean.

4 / 5

Actionability

Provides copy-paste-ready grep patterns ('log\..*\$\{user\.email\}', 'analytics\.track', 'segment\.identify'), per-data-store DSAR deletion guidance, and a full output template, but stops short of executable code for the core destructive operations (e.g., vendor deletion API calls), leaving minor gaps.

4 / 5

Workflow Clarity

Guidance is organized as eight reference practices with per-practice 'Audit step' notes plus a DSAR checklist and an end-to-end simulation checkpoint, but there is no single coherent sequenced workflow with validation gates tying the audit together — checkpoints are distributed and mostly implicit.

3 / 5

Progressive Disclosure

All ~230 lines live inline in one SKILL.md with no bundle files (references/, scripts/, assets/ absent); sections are clearly headed but content that could be split out — detailed grep-pattern catalogs, regulatory tables, the DSAR fan-out — remains inline, so structure is present but not appropriately分层.

3 / 5

Total

14

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

An exemplar description: it states concrete capabilities, covers the domain comprehensively, supplies an exhaustive list of natural trigger terms with synonyms, and gives an explicit 'Use when' clause. No gaps worth penalizing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Implement and audit privacy controls,' DSARs 'access, deletion, portability,' and 'right to be forgotten across backups, caches, analytics, and third parties' — with comprehensive coverage of the domain, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers both 'what' (the opening 'Implement and audit privacy controls...' sentence with enumerated coverage) and 'when' (the full 'Use when the user mentions...' trigger clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

The 'Use when' clause exhaustively enumerates natural user terms including synonyms and abbreviations — 'GDPR,' 'CCPA,' 'CPRA,' 'DSAR' + 'data subject access request,' 'DPIA' + 'data protection impact assessment,' 'DPA' + 'data processing agreement,' 'SCCs,' 'cookie consent' — giving comprehensive coverage with variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear privacy-engineering niche with triggers (GDPR, CCPA, DSAR, consent, right to be forgotten) that are specific to privacy and would not naturally fire a generic security or file-handling skill, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
briiirussell/cybersecurity-skills
Reviewed

Table of Contents

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.