Content
36%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 lean and well-sectioned but nearly empty of substance: instructions are generic boilerplate rather than actionable GDPR guidance, there is no concrete workflow, and the single referenced resource file is missing from the bundle. The skill reads as a template skeleton rather than a usable implementation guide.
Suggestions
Replace the generic instruction bullets with concrete GDPR guidance, e.g., a DSR intake-to-response workflow, consent-record data model, and lawful-basis checklist.
Fix or remove the dangling reference: `resources/implementation-playbook.md` is cited twice but does not exist in the bundle.
Delete the tautological 'Do not use this skill when the task is unrelated to gdpr data handling' section and instead fold the trigger list into the description's Use-when guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and free of concept-explanation padding, but the generic instruction bullets ("Clarify goals, constraints, and required inputs") and the tautological "Do not use when the task is unrelated to gdpr data handling" section are filler that could be trimmed. This matches anchor 3: mostly efficient with some unnecessary content. | 3 / 5 |
Actionability | The Instructions section is placeholder-level generic ("Apply relevant best practices and validate outcomes") with no concrete GDPR guidance — no consent-record patterns, DSR handling steps, or retention rules. The only concrete pointer, "open resources/implementation-playbook.md", targets a file that does not exist in the bundle. This matches anchor 2: high-level hints missing the specific steps to execute. | 2 / 5 |
Workflow Clarity | The bullets imply a rough generic sequence (clarify goals, apply best practices, validate) but contain no GDPR-specific steps, no sequencing of a real workflow, and no validation checkpoints for risky operations like data deletion or batch erasure. This matches anchor 2: rough sequence with many gaps and no real validation. | 2 / 5 |
Progressive Disclosure | Sections are clearly labeled and the reference to `resources/implementation-playbook.md` is signaled one level deep under Resources. However, that file does not exist anywhere in the bundle, making it a dangling reference that breaks navigation — more than the minor organization gaps of anchor 4, so it lands at anchor 3. | 3 / 5 |
Total | 10 / 20 Passed |