CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/gdpr-test-patterns

Reference catalog of GDPR-aligned test patterns - data-subject-rights workflows (Art. 15 access, Art. 16 rectification, Art. 17 erasure / "right to be forgotten", Art. 18 restriction, Art. 20 portability, Art. 21 objection); consent recording + revocation per Art. 7; data-residency assertions per Art. 44 - 50 international transfers; breach-notification timing tests per Art. 33 (72 hours); data-minimization assertions in fixtures per Art. 5(1)(c). The California analogue - CCPA/CPRA patterns by Cal. Civ. Code section, including Global Privacy Control (GPC) opt-out, right-to-know, deletion, right-to-correct, and sensitive-PI limits - lives in references/ccpa.md. Use when authoring GDPR- or CCPA/CPRA-readiness tests for any product processing EU or California personal data.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

86%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.

The body delivers executable, well-organized per-Article test patterns with a sequenced workflow and clean reference splitting. It is slightly less lean due to restated examples in the Worked example and tables.

DimensionReasoningScore

Conciseness

Largely lean executable test code with minimal concept padding, though the Worked example and gap/anti-pattern tables lightly restate patterns already shown above.

4 / 5

Actionability

Each Article is a copy-paste-ready Python test function with concrete assertions covering the common cases (consent grant/revoke, multi-system SAR/erasure, 72h breach timing, region assertions, fixture allowlists).

5 / 5

Workflow Clarity

The 7-step 'How to use' sequence includes checkpoints (assert across ALL systems, pin timelines to the policy doc, wire CI to fail the build) with anti-pattern/gap tables as recovery guidance; minor validation gaps remain for a destructive/batch domain.

4 / 5

Progressive Disclosure

Overview keeps the per-Article catalog inline while the CCPA analogue is cleanly split into a real one-level-deep references/ccpa.md, signaled repeatedly in the body and References.

5 / 5

Total

18

/

20

Passed

Description

92%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.

The description is specific, complete, and distinctive, with a concrete 'Use when' clause and comprehensive per-Article coverage in third person. Trigger-term coverage is strong but a few natural synonyms could be added.

DimensionReasoningScore

Specificity

Enumerates many concrete actions per Article (access, rectification, erasure, restriction, portability, objection, consent recording/revocation, breach-notification timing, data-residency and minimization assertions), giving comprehensive coverage.

5 / 5

Completeness

Clearly states what the skill is ('Reference catalog of GDPR-aligned test patterns' with the full Article breakdown) and gives an explicit 'Use when...' clause naming concrete triggering situations.

5 / 5

Trigger Term Quality

Includes natural trigger phrases ('GDPR- or CCPA/CPRA-readiness tests', 'processing EU or California personal data'), but is missing some common synonyms/extensions a user might say.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (per-Article GDPR/CCPA test-pattern catalog) with distinct triggers unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents