clerk-data-handling
Handle user data, privacy, and GDPR compliance with Clerk. Use when implementing data export, user deletion, or privacy compliance features. Trigger with phrases like "clerk user data", "clerk GDPR", "clerk privacy", "clerk data export", "clerk delete user".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-data-handling/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Clerk + GDPR/privacy), provides explicit trigger guidance, and answers both what and when. The main weakness is that the 'what' portion could be more specific about the concrete actions beyond 'handle'—listing specific operations like generating data export reports, processing deletion requests, or managing consent records would strengthen it.
Suggestions
Replace the vague 'Handle user data, privacy, and GDPR compliance' with more specific concrete actions, e.g., 'Generates user data exports, processes account deletion requests, and implements GDPR consent management with Clerk.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (user data, privacy, GDPR compliance with Clerk) and some actions (data export, user deletion, privacy compliance features), but doesn't list multiple concrete specific actions in detail—e.g., it doesn't specify what 'handle' means beyond export and deletion. | 2 / 3 |
Completeness | Clearly answers both 'what' (handle user data, privacy, GDPR compliance with Clerk) and 'when' (explicit 'Use when' clause for data export, user deletion, privacy compliance, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'clerk user data', 'clerk GDPR', 'clerk privacy', 'clerk data export', 'clerk delete user'—these are terms users would naturally say when needing this skill, with good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of Clerk-specific context with GDPR/privacy/data export creates a clear niche. The trigger terms are all prefixed with 'clerk', making it unlikely to conflict with generic privacy or data handling skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with comprehensive executable code covering the full GDPR/privacy compliance workflow with Clerk. Its main weaknesses are verbosity (the consent UI and cleanup script could be externalized) and missing explicit validation checkpoints in the destructive deletion workflow. The error handling table is a nice touch but doesn't compensate for the lack of inline verification steps.
Suggestions
Add explicit validation checkpoints in the deletion workflow, e.g., verify each deletion step succeeded before proceeding to the next, with a rollback or halt strategy on failure.
Move the ConsentManager UI component and bulk cleanup script to separate referenced files to reduce the main skill's token footprint.
Remove the Prerequisites section—'Understanding of GDPR/CCPA requirements' is not actionable guidance for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with some unnecessary elements (e.g., 'Prerequisites' listing 'Understanding of GDPR/CCPA requirements' is not actionable, the UI component is verbose). However, most content is code-focused and relevant. The consent UI component could be trimmed or referenced externally. | 2 / 3 |
Actionability | All guidance is concrete with fully executable TypeScript code examples covering data export, deletion, consent management, UI components, audit logging, and a cleanup script. Code is copy-paste ready with proper imports and types. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (export → deletion → consent → UI → audit), and the deletion step includes an audit trail and partial failure handling. However, there are no explicit validation checkpoints between steps—e.g., no 'verify deletion completed before logging' or 'test export endpoint before proceeding.' For destructive operations like user deletion, the lack of explicit validate-then-proceed feedback loops caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and an error handling table, plus links to external resources. However, at ~170 lines of code-heavy content, the consent UI component and bulk cleanup script could be split into referenced files. The skill is somewhat monolithic for its scope. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3e83543
- 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.