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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clerk-data-handling78
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-structured skill description that excels at trigger term coverage and completeness with explicit 'Use when' and 'Trigger with' clauses. The main weakness is moderate specificity - it describes the domain well but could benefit from listing more concrete actions like specific Clerk API methods or compliance workflows.
Suggestions
Add more specific concrete actions such as 'export user data via Clerk API', 'implement right-to-erasure requests', or 'configure data retention policies' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk, GDPR compliance) and some actions (data export, user deletion, privacy compliance features), but doesn't list comprehensive concrete actions like specific API calls or implementation steps. | 2 / 3 |
Completeness | Clearly answers both what (handle user data, privacy, GDPR compliance with Clerk) and when (implementing data export, user deletion, privacy compliance) with explicit 'Use when' clause and trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clerk user data', 'clerk GDPR', 'clerk privacy', 'clerk data export', 'clerk delete user'. Good coverage of common variations combining the product name with relevant concepts. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by combining Clerk-specific context with GDPR/privacy domain. The explicit 'clerk' prefix on all trigger terms creates a clear niche unlikely to conflict with generic privacy or other auth provider 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 skill provides highly actionable, production-ready TypeScript code for GDPR compliance with Clerk. The main weaknesses are its length (could benefit from splitting into multiple files) and the lack of explicit validation checkpoints in the destructive deletion workflow. The code quality is excellent but the document structure doesn't optimize for token efficiency.
Suggestions
Add explicit validation checkpoints in the deletion workflow (e.g., 'Verify database deletion succeeded before proceeding to Clerk deletion')
Split into separate files: SKILL.md overview + data-export.md, user-deletion.md, consent.md, and audit.md for detailed implementations
Remove the Privacy Checklist section - this is project management content, not actionable guidance for Claude
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides comprehensive code examples but includes some unnecessary verbosity like the full interface definitions that could be inferred, and the checklist/resources sections add bulk without critical value for Claude's execution. | 2 / 3 |
Actionability | Excellent executable TypeScript code throughout with complete, copy-paste ready implementations for data export, deletion, consent management, and API endpoints. All code is fully typed and production-ready. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but the deletion workflow lacks explicit validation checkpoints between steps. For destructive operations like user deletion, there should be explicit verify-before-proceed gates rather than just try-catch error handling. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is monolithic at ~300 lines. The data export, deletion, retention, and consent management could be split into separate reference files with SKILL.md providing an overview and links. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.