Content
51%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.
The body is a well-structured overview with excellent progressive disclosure, but it spends much of its budget restating GDPR fundamentals Claude already knows and offers no sequenced, executable workflow for the processes it covers. Moving the textbook article listings into the reference and adding a short DSR/consent step sequence with validation checkpoints would lift the weakest dimensions.
Suggestions
Trim the Article 6 lawful-bases tree and Article 15-21 rights listing to a compact non-obvious summary (or move them to references/details.md), keeping only guidance Claude would not already know such as the protection-level table.
Add a short numbered workflow in the body for the highest-frequency process — e.g. handling a data subject request from intake to response — with explicit validation checkpoints, since erasure and restriction are destructive operations.
Make the body's guidance more executable by including a few concrete specifics (e.g. consent record fields to store, retention-policy enforcement approach) rather than deferring all implementation detail to the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The Article 6 lawful-bases tree and the Article 15-21 rights listing restate standard GDPR knowledge Claude already has, so the body includes unnecessary explanation even though the protection-level table and Do's/Don'ts add value. Matches the "mostly efficient but includes some unnecessary explanation" anchor; not 2 because there is no heavy padding, not 4 because the core-concepts section could be trimmed to non-obvious details. | 3 / 5 |
Actionability | The Do's/Don'ts give concrete policy directives ("Don't pre-check consent boxes", "30-day response required", "SCCs or adequacy decisions") but the body contains no executable steps, commands, or implementation specifics — all of those are deferred to references/details.md. Fits the "some concrete guidance but incomplete; missing key details" anchor rather than the mostly-executable anchor 4. | 3 / 5 |
Workflow Clarity | The body presents no sequenced workflow at all — no consent-capture flow, no DSR response steps, no validation checkpoints — despite covering destructive operations like erasure. It scores above the incoherent anchor 1 only because process constraints ("Must respond within 1 month") are present; it lacks even the rough sequence of anchor 3. | 2 / 5 |
Progressive Disclosure | The body is a well-sectioned overview that points to a single one-level-deep reference ("Detailed sections (starting with `## Implementation Patterns`) live in `references/details.md`"), which was verified to exist and to contain the promised section header. Clear split, easy navigation, well-signaled reference — matches the top anchor. | 5 / 5 |
Total | 13 / 20 Passed |