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

Quality

72%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

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 solid, actionable skill with excellent executable code examples covering multiple Clerk performance optimization strategies. Its main weaknesses are the lack of validation/measurement checkpoints integrated into the workflow (the perf measurement is an afterthought rather than a verification step), and the monolithic structure that could benefit from splitting advanced patterns into referenced files. Some minor verbosity in prerequisites and output sections could be trimmed.

Suggestions

Integrate the performance measurement utility as an explicit 'Step 0: Baseline' and 'Final Step: Verify improvements' to create a proper feedback loop in the workflow.

Remove the Prerequisites section (Claude already knows these) and trim the Output section which merely restates what was covered in the steps.

Consider splitting advanced patterns (cross-request caching, token optimization) into a referenced file to improve progressive disclosure and reduce the main file's length.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' (Claude knows these), the 'Resources' links, and some comments that explain obvious things. The 'Output' section is a bullet list restating what was already covered. Could be tightened by ~20-30%.	2 / 3
Actionability	Every step includes fully executable TypeScript code with proper imports, file paths, and usage comments. The code is copy-paste ready and covers concrete patterns like middleware matchers, React cache(), dynamic imports, and Suspense boundaries.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced, but there are no validation checkpoints or feedback loops. For performance optimization, there should be explicit 'measure before/after' steps integrated into the workflow rather than a standalone measurement example at the end. The measurement utility is provided but not woven into the workflow as a verification step.	2 / 3
Progressive Disclosure	The content is a single monolithic file with all details inline. At ~150 lines, some of the more advanced patterns (cross-request caching, token optimization) could be referenced out. The 'Next Steps' reference to 'clerk-cost-tuning' is good, but no bundle files exist to support progressive disclosure. The error handling table and examples section add bulk that could be separate.	2 / 3
	Total	9 / 12 Passed

Description

79%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at trigger term coverage, completeness (both what and when), and distinctiveness due to its focus on a specific product (Clerk). However, it is weak on specificity of capabilities — it says 'optimize' without describing what concrete actions or techniques the skill actually performs (e.g., caching, middleware tuning, token refresh strategies).

Suggestions

Add specific concrete actions the skill performs, e.g., 'Configures caching for Clerk tokens, optimizes middleware placement, reduces redundant API calls to Clerk backend, and tunes SDK initialization.'

Replace the vague 'Optimize Clerk authentication performance' opener with a list of 2-4 specific techniques or outputs the skill provides.

Dimension	Reasoning	Score
Specificity	The description says 'Optimize Clerk authentication performance' but does not list any concrete actions. It lacks specifics like caching strategies, middleware configuration, token handling, or SDK-specific optimizations. 'Optimize' and 'improving' are vague verbs.	1 / 3
Completeness	Explicitly answers both 'what' (optimize Clerk authentication performance) and 'when' (improving auth response times, reducing latency, optimizing SDK usage) with explicit trigger phrases. Both clauses are present and clear.	3 / 3
Trigger Term Quality	Includes good natural trigger terms: 'clerk performance', 'clerk optimization', 'clerk slow', 'clerk latency', 'optimize clerk'. These are phrases users would naturally say when experiencing Clerk performance issues.	3 / 3
Distinctiveness Conflict Risk	Very specific niche: Clerk authentication performance optimization. The combination of 'Clerk' (a specific product) and 'performance/optimization' creates a distinct trigger space unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.