clerk-local-dev-loop
Set up local development workflow with Clerk. Use when configuring development environment, testing auth locally, or setting up hot reload with Clerk. Trigger with phrases like "clerk local dev", "clerk development", "test clerk locally", "clerk dev environment".
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-local-dev-loop/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 skill description with excellent trigger terms and completeness, clearly specifying both what the skill does and when to use it. The main weakness is that the specificity of capabilities could be improved — the description mentions general activities like 'configuring development environment' rather than listing concrete actions the skill performs. Overall it would perform well in skill selection scenarios.
Suggestions
Add more specific concrete actions like 'configure Clerk API keys, set up ngrok for webhook testing, configure hot reload for auth components' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk local development) and mentions some actions like 'configuring development environment', 'testing auth locally', 'setting up hot reload', but these are fairly general and don't list concrete specific steps or outputs (e.g., 'configure environment variables', 'set up ngrok tunnels', 'configure webhook forwarding'). | 2 / 3 |
Completeness | Clearly answers both 'what' (set up local development workflow with Clerk) and 'when' (configuring development environment, testing auth locally, setting up hot reload) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'clerk local dev', 'clerk development', 'test clerk locally', 'clerk dev environment', plus contextual terms like 'hot reload', 'auth locally'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Clerk local development workflow. The combination of 'Clerk' + 'local dev' creates a distinct trigger space that is unlikely to conflict with other skills like general auth setup or general local dev environment 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 skill provides highly actionable, executable code examples covering the full local dev workflow with Clerk, which is its primary strength. However, it's somewhat verbose for a SKILL.md — it reads more like a tutorial than a concise reference, and lacks validation checkpoints between steps. The content would benefit from splitting detailed code (mocks, fixtures, seed scripts) into referenced files and adding explicit verification steps.
Suggestions
Add validation checkpoints after key steps (e.g., 'Verify test keys work: `curl -H "Authorization: Bearer sk_test_..." https://api.clerk.com/v1/users`' after Step 1, or 'Confirm seed succeeded by checking user count' after Step 2).
Move the Vitest mock helper and Playwright fixture code into referenced files (e.g., 'See [test/helpers/clerk-mock.ts](test/helpers/clerk-mock.ts)') to keep SKILL.md as a concise overview.
Remove the bullet list of what Clerk development instances provide — Claude already knows this, and it doesn't add actionable guidance.
Trim the 'Output' section which merely restates what the steps already accomplish.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary context (e.g., listing what Clerk development instances provide, the 'Prerequisites' section with obvious items, and the 'Output' section restating what was already covered). The code examples are useful but the surrounding prose could be tighter. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for every step: env configuration, seed scripts, Next.js config, package.json scripts, Vitest mocks, and Playwright fixtures. Commands are specific and complete. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no validation checkpoints between steps. For example, there's no verification that test users were seeded correctly, no check that the dev server is running with HTTPS properly, and no feedback loop for common setup failures. | 2 / 3 |
Progressive Disclosure | The content is fairly long and monolithic — the mock auth helpers, Playwright fixtures, and seed scripts could be referenced as separate files rather than inlined. The 'Resources' and 'Next Steps' sections provide some navigation, but the main body packs too much inline content for a SKILL.md overview. | 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
3e83543
- 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.