clerk-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clerk-debug-bundleCollect comprehensive debug information for Clerk issues. Use when troubleshooting complex problems, preparing support tickets, or diagnosing intermittent issues. Trigger with phrases like "clerk debug", "clerk diagnostics", "clerk support ticket", "clerk troubleshooting".
Validation
75%| 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 | |
Implementation
65%This skill provides highly actionable, executable debug tooling for Clerk troubleshooting with comprehensive code examples. However, it's somewhat verbose for a skill file, lacks validation checkpoints between steps, and could benefit from better progressive disclosure by moving detailed scripts to referenced files.
Suggestions
Add explicit validation steps after each script creation (e.g., 'Run the script and verify output shows expected fields before proceeding')
Move the longer code blocks to separate referenced files (e.g., 'See scripts/clerk-debug.ts') and keep only essential snippets inline
Remove the Prerequisites section - Claude knows these are needed from context
Add a troubleshooting flow: 'If health check fails at step X, check Y before proceeding'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides useful debug scripts but includes some unnecessary verbosity like the 'Prerequisites' section and explanatory comments that Claude doesn't need. The code examples are comprehensive but could be more condensed. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code, a complete bash script, and copy-paste ready implementations. Each step provides concrete, working code that can be immediately used. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints between steps. No guidance on verifying each debug component works before proceeding to the next, and no error recovery workflow if a step fails. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the skill is quite long with all code inline. The debug scripts could be referenced as separate files rather than embedded, and the error handling table at the end feels disconnected from the workflow. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear when/what guidance. The main weakness is the lack of specific concrete actions - it says 'collect comprehensive debug information' but doesn't specify what that entails (logs, config, environment variables, etc.).
Suggestions
Add specific actions to improve specificity, e.g., 'Collects environment variables, SDK versions, authentication state, and error logs for Clerk issues.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk issues) and a general action (collect debug information), but doesn't list specific concrete actions like what information is collected or what diagnostic steps are performed. | 2 / 3 |
Completeness | Clearly answers both what (collect comprehensive debug information for Clerk issues) and when (troubleshooting, preparing support tickets, diagnosing intermittent issues) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clerk debug', 'clerk diagnostics', 'clerk support ticket', 'clerk troubleshooting'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Clerk debugging with distinct triggers. The combination of 'Clerk' + 'debug/diagnostics/support ticket' creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 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.