CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/ccpa-test-patterns

Reference catalog of CCPA + CPRA-aligned test patterns - do-not-sell-or-share opt-out via Global Privacy Control (GPC) signal; data-disclosure category tests per Cal. Civ. Code §1798.110; sensitive personal information (SPI) handling per CPRA §1798.121; deletion-request workflows per §1798.105; CPRA's right to correct (§1798.106) + limit-use (§1798.121). Use when authoring CCPA/CPRA-readiness tests for any product processing California consumer data.

77

Quality

97%

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

92%

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

A high-quality, dense reference catalog with executable per-statute test patterns, concrete reference data, and a useful anti-patterns table. The only weakness is progressive disclosure: everything lives in one monolithic file with no split into reference materials.

Suggestions

Split the per-statute test patterns into a references/ file (e.g. references/test-patterns.md) and keep SKILL.md as a concise overview pointing to it, so the catalog is progressively disclosed rather than monolithic.

Move the SPI categories table (CPRA §1798.140(ae)) into its own reference file and link to it from the §1798.121 pattern, reducing inline length while keeping the data one level deep.

Add a short table of contents or 'Quick reference' section at the top mapping each Cal. Civ. Code section to its heading anchor for faster in-file navigation.

DimensionReasoningScore

Conciseness

Dense, information-rich prose that assumes competence: penalty dollar amounts, thresholds, and the SPI category table are concrete reference data needed for the test patterns, not generic explanations of what privacy law is. Not the level-2 anchor because there is no padded 'CCPA is a law that...' fluff to tighten.

3 / 3

Actionability

Each section provides complete, copy-paste-ready Python test functions with real assertions (cookie checks, ORM queries, feature-attribution sets), meeting the 'fully executable code; specific examples; copy-paste ready' anchor rather than pseudocode.

3 / 3

Workflow Clarity

Organized by Cal. Civ. Code section with a 'When to use' trigger list, an anti-patterns table mapping each failure to a fix that cross-references the relevant section, plus limitations and references — clear navigation for a single-purpose catalog, which the simple-skills note allows to score 3 even without a multi-step validation sequence.

3 / 3

Progressive Disclosure

Well-organized single SKILL.md with clear headers and a clearly signaled References section, but the entire catalog (all test patterns + the SPI category table) is inline in one ~180-line file with no content split into separate reference files and no bundle files provided — matching 'some structure, content that should be separate is inline' rather than 'content appropriately split'.

2 / 3

Total

11

/

12

Passed

Description

100%

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

A strong, specific, third-person description that enumerates concrete test-pattern capabilities by statute and carries an explicit 'Use when' trigger with a clear, non-conflicting niche. No fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete test-pattern capabilities (do-not-sell-or-share opt-out via GPC, data-disclosure category tests per §1798.110, SPI handling per §1798.121, deletion workflows per §1798.105, right to correct §1798.106, limit-use §1798.121) rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (reference catalog of CCPA/CPRA-aligned test patterns enumerated by section) and 'when' via a literal 'Use when authoring CCPA/CPRA-readiness tests for any product processing California consumer data' trigger, satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Uses natural compliance-engineer vocabulary a user would actually say — 'CCPA', 'CPRA', 'do-not-sell-or-share', 'GPC', 'sensitive personal information', 'right to correct', 'California consumer data' — giving good coverage rather than jargon-only or generic terms.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (California CCPA/CPRA readiness tests) with distinct triggers and even names its EU sister skill gdpr-test-patterns, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

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