CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-gdpr-deepening

Generates GDPR Article 30 processing registers and Article 35 DPIAs for Belgian and EU SMEs, prefilled with common SME processing activities. Use when: Draft Article 30 records for controllers and processors; Run a 3-gate DPIA obligation test for new projects; Create risk-scored DPIA documents with mitigation steps.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-compliance/skills/nex-gdpr-deepening/SKILL.md

The canonical home for this skill is nex-gdpr-deepening in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

36%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 reads as a well-written product landing page rather than an operational skill: it competently describes what the skill would do, its limits, and a sample result, but contains none of the executable material (legal criteria lists, risk matrix, Article 30 field requirements, templates) needed to actually perform the work, which it acknowledges is not in the folder. It works only as marketing documentation of a skill whose substance lives elsewhere.

Suggestions

Inline or ship as bundle files the actual operational content: the eight Belgian GBA processing types, the Article 35.3 criteria, the nine EDPB criteria, the likelihood-times-impact matrix scale, and the mandatory Article 30.1/30.2 field lists — currently all are named but none are provided.

Add a sequenced workflow with checkpoints, e.g. 1) gather processing facts, 2) run each of the three DPIA gates and record per-gate results, 3) document the negative conclusion or proceed to draft, 4) score risks before/after measures, 5) flag for DPO/legal review before delivery.

Remove the '## Questions' FAQ (it restates 'What it does') and the promotional footer links, which spend tokens without adding instructional value.

DimensionReasoningScore

Conciseness

The body is lean and does not re-explain GDPR concepts Claude already knows, but the '## Questions' FAQ ('How is risk scoring calculated?', 'What criteria does it use for DPIA checks?') merely repeats 'What it does', and the promotional footer ('More skills, including the paid catalog: https://...') is pure noise. That is 'some unnecessary explanation or could be tightened' — the 3 anchor — rather than the minor-trim case of 4.

3 / 5

Actionability

The body names its machinery — 'the Belgian GBA list of eight mandatory processing types, Article 35.3, and the nine EDPB criteria', 'a likelihood-times-impact risk scoring matrix' — but never supplies any of it: no GBA list, no EDPB criteria, no matrix scale, no mandatory Article 30 field list, and it openly states 'Scripts, extension source, and templates from the original package are not in this folder.' The sample output gives a hint of the result format, lifting it above 'entirely vague' (1), but it is high-level description with the specific steps to execute missing — the 2 anchor.

2 / 5

Workflow Clarity

Running a 3-gate obligation test and then drafting a risk-scored DPIA is inherently multi-step, yet the only sequencing is implied ('Next: Should we perform a DPIA check for the cameras?'); no ordered steps are given for either the gate test or the DPIA drafting, and there are no validation or review checkpoints even though legal-document output warrants them. This is a rough implied sequence with many gaps and no validation — the 2 anchor.

2 / 5

Progressive Disclosure

The ~50-line body is cleanly sectioned (What it does, Use cases, Known limitations, Example, Questions), but the operational content that clearly belongs in reference or script files (templates, the GBA/EDPB lists, the risk matrix) is entirely absent rather than moved to a bundle, and the only pointers given lead outside the skill (the Agensi page and a paid catalog) rather than to navigable files. 'Some structure but could be better organized' — the 3 anchor — fits better than 4, where references would be present and mostly clear.

3 / 5

Total

10

/

20

Passed

Description

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

A strong description: concrete third-person capability list, explicit multi-clause 'Use when' triggers, and a well-defined niche. The only gaps are a few natural synonyms (ROPA, verwerkingsregister, spelled-out 'data protection impact assessment') and an unstated boundary against the related nex-gdpr DSR skill.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — 'Generates GDPR Article 30 processing registers and Article 35 DPIAs', 'prefilled with common SME processing activities', 'Run a 3-gate DPIA obligation test', 'risk-scored DPIA documents with mitigation steps' — with comprehensive coverage of its niche, matching the score-5 anchor rather than the 'minor gaps' of 4. Voice is third person throughout.

5 / 5

Completeness

Explicitly answers both questions: a clear 'what' ('Generates GDPR Article 30 processing registers and Article 35 DPIAs... prefilled with common SME processing activities') followed by an explicit 'Use when:' with three concrete trigger clauses ('Draft Article 30 records...', 'Run a 3-gate DPIA obligation test...', 'Create risk-scored DPIA documents...'). This matches the score-5 anchor; it is not 4 because the when-guidance is explicit rather than only weakly specified.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('GDPR', 'Article 30', 'Article 35', 'DPIA', 'controllers', 'processors', 'records'), but common user phrasings are missing: 'records of processing activities', 'ROPA', 'data protection impact assessment' spelled out, and 'verwerkingsregister' (which the skill's own body example uses). Fits the 4 anchor 'good keyword coverage; a few natural terms missing', not the synonym-complete 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Belgian/EU SME GDPR Article 30/35 work) with distinct triggers gives low conflict risk, but the description never states the boundary with the sibling 'nex-gdpr' skill that handles Articles 15–21 data subject requests, so a DSAR-type request could mis-trigger this skill. That is minor overlap risk with a closely related skill — the 4 anchor — rather than the minimal-conflict 5.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-compliance/skills/nex-gdpr-deepening/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.