CtrlK
BlogDocsLog inGet started
Tessl Logo

clerk-performance-tuning

Optimize Clerk authentication performance. Use when improving auth response times, reducing latency, or optimizing Clerk SDK usage. Trigger with phrases like "clerk performance", "clerk optimization", "clerk slow", "clerk latency", "optimize clerk".

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/clerk-pack/skills/clerk-performance-tuning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

A highly actionable, code-first skill body with executable examples throughout, but it lacks validation/measurement checkpoints in its workflow and fails to signal its own bundle reference file, which duplicates the inline content.

Suggestions

Add a validation checkpoint after each optimization step (e.g., measure auth() time before and after with measureAuthTime) so the workflow has an explicit verify-and-rollback loop.

Link references/implementation-guide.md from the body (e.g., under an 'Advanced' or 'Resources' section) and split the detailed code into it, keeping SKILL.md as a concise overview to remove the duplication.

Drop or trim the 'Output' section, which restates what the preceding code blocks already demonstrate, to recover tokens.

DimensionReasoningScore

Conciseness

The body is mostly lean, code-dense TypeScript with brief useful comments, but the 'Output' section restates what each code block already does and the inline Steps 1-6 are duplicated in references/implementation-guide.md, so it could be tightened.

2 / 3

Actionability

Every step ships complete, executable TypeScript with imports and real Clerk/Next.js APIs (clerkMiddleware, unstable_cache, dynamic imports, Suspense), plus a concrete Error Handling table mapping cause to solution — copy-paste ready.

3 / 3

Workflow Clarity

The six optimization steps are clearly numbered and sequenced, but there are no validation checkpoints or before/after measurement feedback loops to confirm each change actually improved performance; the measureAuthTime snippet sits in Examples unconnected to the workflow.

2 / 3

Progressive Disclosure

The body is well-sectioned but references/implementation-guide.md is never linked or signaled from the body (Resources only lists external URLs), and that file duplicates the same six steps inline rather than splitting detail one level deep.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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, well-structured description that explicitly covers what, when, and natural trigger phrases with a clear Clerk-specific niche. Its only weakness is that the named actions are all flavors of 'optimize' rather than a list of distinct concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and a few actions ('improving auth response times, reducing latency, or optimizing Clerk SDK usage') but these are all variants of one action ('Optimize') rather than multiple distinct concrete actions like extract/fill/merge, so it stops short of anchor 3.

2 / 3

Completeness

Clearly states what ('Optimize Clerk authentication performance') and when ('Use when improving auth response times, reducing latency...') plus explicit trigger phrases, answering both what and when.

3 / 3

Trigger Term Quality

Lists natural phrases a user would actually say ('clerk performance', 'clerk optimization', 'clerk slow', 'clerk latency', 'optimize clerk'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Clerk-authentication-performance niche is clear and every trigger is Clerk-prefixed, making it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 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

Total

14

/

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.