Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, actionable test-pattern catalog: concrete per-Article Python patterns, a clear 7-step workflow, and genuinely useful gap and anti-pattern tables. It falls short of top marks on small executable flaws in examples, implicit rather than explicit test-validation checkpoints in the workflow, a few sentences of GDPR background Claude doesn't need, and a monolithic inline catalog where selective offloading to references/ would help.
Suggestions
Fix the non-executable assertion in the Art. 15 pattern (comparing the 'X-Processing-Time' header string to a timedelta) and the undefined `user` variable in test_consent_revocable so examples are copy-paste runnable.
Trim the GDPR background paragraph (in-force date, fine amounts) that Claude already knows, keeping only the regulation citation pointer.
Add an explicit validation checkpoint to 'How to use' (e.g. 'run the new test and confirm it fails against the current code before fixing the gap') to strengthen the feedback loop for the multi-system assertions.
Consider moving the less-common per-Article patterns (e.g. Art. 20, Art. 44-50) into references/ alongside ccpa.md, keeping the highest-value patterns inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and code-dominated with purposeful comments and dense gap/anti-pattern tables, but includes a few sentences of background Claude already knows ("GDPR (General Data Protection Regulation, in force 2018-05-25)... fines up to €20M or 4% of global annual turnover"), matching level 4 (minor trimmable over-explanation) rather than level 5. | 4 / 5 |
Actionability | Concrete per-Article Python test code is provided and its template nature is explicitly justified ("Copy the matching per-Article pattern below and point it at your framework's client + models"), but there are minor executable gaps: "assert response.headers['X-Processing-Time'] < timedelta(days=30)" compares a header string to a timedelta, and test_consent_revocable references an undefined `user` — level 4, not the fully copy-paste-ready level 5. | 4 / 5 |
Workflow Clarity | "How to use" gives a clear 7-step numbered sequence (inventory PII systems, pick Articles, copy pattern, generate synthetic fixtures, assert across all systems, wire into CI), with validation present but implicit — the CI step is a checkpoint yet there is no explicit run-and-confirm (e.g. verify the new test fails before the fix) checkpoint, matching level 4 rather than the explicit feedback loops of level 5. | 4 / 5 |
Progressive Disclosure | Well-organized sections with the CCPA catalog correctly split into the real one-level-deep references/ccpa.md, signaled both inline and in the References section; however the full ~150-line GDPR per-Article pattern catalog is inlined in SKILL.md where some patterns could live in reference files, matching level 4 (most content appropriately placed) rather than the clean overview-plus-references split of level 5. | 4 / 5 |
Total | 16 / 20 Passed |