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".
76
72%
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-performance-tuning/SKILL.mdQuality
Discovery
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 of when/what clauses, and distinctiveness due to its narrow focus on Clerk performance optimization. However, it is weak on specificity — it fails to enumerate concrete actions or techniques, making it hard to know what the skill actually does beyond the vague notion of 'optimizing'. Adding specific capabilities would significantly strengthen it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures middleware caching, reduces redundant token verification calls, optimizes session management, and tunes Clerk SDK initialization.'
Replace the vague 'Optimize Clerk authentication performance' 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 | Highly distinctive — targets a specific product (Clerk) combined with a specific concern (performance/optimization). Unlikely to conflict with general auth skills or general performance optimization skills. | 3 / 3 |
Total | 10 / 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 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 in Examples), and the monolithic structure that could benefit from splitting detailed patterns into separate files. Some minor verbosity in the Overview, Prerequisites, and Output sections could be trimmed.
Suggestions
Integrate performance measurement as an explicit first and last step in the workflow (e.g., 'Step 0: Baseline measurement' and 'Step 7: Verify improvements'), creating a feedback loop.
Remove the 'Prerequisites' and 'Overview' sections — Claude already knows what Clerk is and the title conveys the purpose.
Consider splitting detailed code patterns (token caching, lazy loading) into a referenced bundle file to keep SKILL.md as a concise overview with quick-reference patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' (Claude knows these), the 'Overview' paragraph restating the title, and the 'Resources' links which add little value. The 'Output' section is a bullet list restating what each step does, which is redundant. | 2 / 3 |
Actionability | Every step includes fully executable, copy-paste-ready TypeScript code with clear file paths and inline comments. The code examples are complete and specific, covering middleware config, caching patterns, token handling, lazy loading, and performance measurement. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints between steps. For performance optimization, there should be explicit 'measure before/after' verification steps — the measurement utility is buried in Examples rather than integrated into the workflow. No feedback loop for verifying improvements. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and a logical flow, but it's a long monolithic file (~150+ lines of code) with no bundle files to offload detail into. The token caching, lazy loading, and edge runtime sections could be separate reference files. The reference to 'clerk-cost-tuning' at the end is good but the skill itself could benefit from splitting. | 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
3a2d27d
- 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.