CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable skill body with executable code and a clear 5-step structure, undermined by verbosity from inlining implementations that already exist in an unreferenced bundle file and by missing explicit validation checkpoints. Offloading the duplicated detail to the reference and adding verification gates would lift the weaker dimensions.

Suggestions

Replace the inline full implementations with concise summaries and link to references/implementation-guide.md (e.g., 'See [implementation-guide.md](references/implementation-guide.md) for full scripts') to remove duplication and make the reference discoverable.

Add explicit validation checkpoints between steps, such as verifying '/api/clerk-health' returns healthy before running the support-bundle script.

Tighten the inline code blocks to the minimal executable snippets and move the verbose variants into the reference file.

DimensionReasoningScore

Conciseness

The body is mostly code (little concept padding), but it inlines five full implementations that largely duplicate references/implementation-guide.md, so it is verbose and could be tightened by offloading detail to the reference.

2 / 3

Actionability

Fully executable, copy-paste-ready TypeScript and bash blocks with explicit run commands ('npx tsx scripts/clerk-debug.ts') and a concrete curl example; no pseudocode.

3 / 3

Workflow Clarity

Five numbered steps plus an Error Handling table give a clear sequence, but there are no explicit validation checkpoints between steps (e.g., verify the health endpoint before running the bundle script), so checkpoints are only implicit.

2 / 3

Progressive Disclosure

The body is well-sectioned, but references/implementation-guide.md exists and is never linked or signaled from the body while its content is duplicated inline — content that should be separate is inline and the reference is not discoverable.

2 / 3

Total

9

/

12

Passed

Description

90%

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, third-person description that covers what and when with explicit, natural trigger phrases and a clear Clerk-specific niche. Its only weakness is that the primary stated action ('comprehensive debug information') is somewhat abstract rather than enumerating concrete capabilities.

DimensionReasoningScore

Specificity

Names the Clerk domain and several actions ('collect debug information', 'preparing support tickets', 'diagnosing intermittent issues'), but the headline action 'comprehensive debug information' is abstract rather than a list of multiple concrete actions.

2 / 3

Completeness

Clearly answers both what ('Collect comprehensive debug information for Clerk issues') and when ('Use when troubleshooting complex problems, preparing support tickets, or diagnosing intermittent issues') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases a user would actually say are listed: 'clerk debug', 'clerk diagnostics', 'clerk support ticket', 'clerk troubleshooting'.

3 / 3

Distinctiveness Conflict Risk

Clearly Clerk-specific niche with distinct Clerk-prefixed triggers; unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.