clerk-debug-bundle
Collect 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".
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-debug-bundle/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 with excellent trigger terms and completeness. It clearly identifies when to use the skill and provides natural language triggers. The main weakness is that the 'what' could be more specific about the concrete actions performed (e.g., checking environment variables, auth config, SDK versions).
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Collects environment variables, SDK versions, auth configuration, middleware setup, and error logs for Clerk issues.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Clerk issues) and a general action (collect comprehensive debug information), but doesn't list specific concrete actions like checking logs, inspecting auth tokens, verifying environment variables, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect comprehensive debug information for Clerk issues) and 'when' (troubleshooting complex problems, 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'. These are realistic terms a user would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Clerk debug/diagnostics collection. The combination of 'Clerk' + 'debug/diagnostics/support ticket' makes it highly unlikely to conflict with other 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 highly actionable skill with complete, executable code for every debug artifact. Its main weaknesses are length (five full code blocks inline make it token-heavy) and lack of explicit validation checkpoints between steps. The content would benefit from splitting detailed code into referenced files and adding verification steps after each script execution.
Suggestions
Add explicit validation checkpoints after each step, e.g., 'Verify the output contains apiConnectivity.status: ok before proceeding to Step 2'
Move the larger code blocks (support bundle script, debug component) into separate referenced files to reduce the main skill's token footprint
Remove the Prerequisites section—Claude doesn't need to be told about browser developer tools or that the SDK must be installed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with five substantial code blocks. Some content could be tightened—the prerequisites section states obvious things ('Browser with developer tools'), and the Overview restates what the description already covers. However, most code blocks earn their place as they provide distinct debug artifacts. | 2 / 3 |
Actionability | Every step provides fully executable, copy-paste-ready code with specific file paths, imports, and run commands. The bash script, TypeScript files, and curl one-liner are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints between steps. The skill doesn't specify when to verify each step's output before proceeding, and there's no feedback loop for when the debug script itself fails or returns unexpected results. The error handling table helps but is separate from the workflow. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic document with ~200 lines of inline code that could benefit from splitting into separate files (e.g., the support bundle script, the debug component). The 'Current State' dynamic commands at the top and the Resources/Next Steps sections show some structure, but the bulk of content is inline rather than referenced. | 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
c8a915c
- 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.