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

Quality

77%

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-local-dev-loop/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 dev setup, test seeding, mocking, and E2E testing. Its main weaknesses are the lack of validation checkpoints in the workflow (no 'verify it works' steps between stages) and the monolithic structure that could benefit from splitting detailed code into referenced files. Some minor verbosity could be trimmed without losing clarity.

Suggestions

Add explicit validation checkpoints after key steps, e.g., 'Verify: visit localhost:3000/sign-in and confirm the Clerk widget loads' after Step 3, and 'Verify: run the seed script and confirm users appear in Clerk Dashboard' after Step 2.

Extract the mock helper (clerk-mock.ts) and Playwright fixture into separate bundle files and reference them from the SKILL.md to improve progressive disclosure and reduce body length.

Remove the bullet list under 'Clerk development instances provide' — Claude already knows these features and they don't add actionable guidance.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanations (e.g., listing what Clerk development instances provide, the 'Output' section restating what was already covered). The comments in code are mostly useful, but the overall content could be tightened—several sections explain things Claude would already know (e.g., what test keys look like, basic Next.js config patterns).	2 / 3
Actionability	The skill provides fully executable, copy-paste ready code throughout: seed scripts, Next.js config, Vitest mock helpers, Playwright fixtures, and concrete bash commands. Key details like error handling for duplicate users and specific package.json scripts are included.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints or feedback loops. For example, after seeding test users there's no verification step, and after configuring HTTPS there's no check that Clerk auth actually works. The error handling table partially compensates but is reactive rather than integrated into the workflow.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections, but it's quite long (~180 lines of substantive content) with no bundle files to offload detail into. The mock helpers, Playwright fixtures, and seed scripts could be separate referenced files. The 'Next Steps' reference to 'clerk-sdk-patterns' is good but the main body is monolithic.	2 / 3
	Total	9 / 12 Passed

Description

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 'what' portion could be more specific about the concrete actions performed (e.g., configuring environment variables, setting up webhook tunnels, configuring middleware). The explicit trigger phrases section is a strong addition for disambiguation.

Suggestions

Add more specific concrete actions to the description, e.g., 'Configures environment variables, sets up webhook tunnels, configures Clerk middleware, and enables hot reload for local Clerk authentication testing.'

Dimension	Reasoning	Score
Specificity	Names the domain (Clerk local development) and mentions some actions like 'configuring development environment', 'testing auth locally', and 'setting up hot reload', but these are fairly general and don't list concrete specific steps or outputs.	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' which are terms users would naturally say. Also includes broader terms like 'hot reload with Clerk' and 'testing auth locally'.	3 / 3
Distinctiveness Conflict Risk	Highly specific to Clerk local development workflow, which is a clear niche. The trigger terms are specific enough ('clerk local dev', 'clerk dev environment') to avoid conflicts with general development setup skills or other auth provider skills.	3 / 3
	Total	11 / 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: 3 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.