clerk-hello-world
Create your first authenticated request with Clerk. Use when making initial API calls, testing authentication, or verifying Clerk integration works correctly. Trigger with phrases like "clerk hello world", "first clerk request", "test clerk auth", "verify clerk setup".
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-hello-world/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 description with excellent trigger terms and clear 'when' guidance, making it highly distinguishable from other skills. Its main weakness is that the 'what' portion is somewhat thin — it describes a single general action rather than listing multiple concrete steps or outputs. Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Creates a sample authenticated API request, validates JWT tokens, and confirms Clerk middleware configuration.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Clerk authentication) and a general action ('Create your first authenticated request'), but doesn't list multiple specific concrete actions beyond making an initial API call. 'Testing authentication' and 'verifying integration' are somewhat vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (create first authenticated request with Clerk) and 'when' (making initial API calls, testing authentication, verifying Clerk integration) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases like 'clerk hello world', 'first clerk request', 'test clerk auth', 'verify clerk setup' which are terms users would naturally say. Also includes broader terms like 'API calls', 'authentication', and 'Clerk integration'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Clerk-specific hello world / first authenticated request. The trigger terms are highly distinctive ('clerk hello world', 'test clerk auth') and 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 solid, highly actionable skill with complete, executable code examples covering multiple Clerk integration patterns. Its main weaknesses are the lack of explicit verification/validation steps between stages (critical for a 'verify clerk setup' skill) and the length — five full code examples plus enterprise considerations in a single 'hello world' file is more than necessary. Trimming redundant explanations and adding verification checkpoints would significantly improve it.
Suggestions
Add explicit verification checkpoints after each step (e.g., 'Visit /dashboard — you should see your name and email. If you see the redirect, check that you're signed in.').
Consider moving the Express.js example to a separate file or making it optional, since it's a different framework from the Next.js focus of Steps 1-4.
Remove inline comments that restate what the 'Key distinction' paragraph already explains, or vice versa — pick one location for that information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-written but includes some unnecessary explanations (e.g., inline comments explaining what auth() and currentUser() do, the 'Key distinction' paragraph restating what comments already say). The Enterprise Considerations and five full code examples make it longer than needed for a 'hello world' skill. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | Every step provides fully executable, copy-paste-ready TypeScript code with correct file paths, imports, and complete component implementations. The error handling table gives specific causes and solutions. This is highly actionable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints — no instructions to verify each step works before proceeding (e.g., 'visit /dashboard and confirm you see your name', 'curl /api/hello and verify 200 response'). For an integration verification skill, explicit verification steps after each code block would be expected. | 2 / 3 |
Progressive Disclosure | The skill has good section structure and links to external docs, but all five code examples are inline in a single file, making it quite long. The Express.js example could be a separate reference since it's a different framework entirely. The Resources and Next Steps sections are well-done, but the monolithic body 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.