CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Executable and token-efficient, with concrete code throughout. The main gaps are missing explicit validation checkpoints in the setup workflow and an undiscoverable bundle reference - the implementation guide exists but is never linked from the body.

Suggestions

Add explicit validation checkpoints after each step (e.g., verify seeded users appear in the Clerk dashboard, confirm the HTTPS dev server returns 200) so the workflow has clear verify gates.

Link to references/implementation-guide.md from the body - e.g., add a 'See [implementation-guide.md](references/implementation-guide.md) for extended code patterns' line under Resources - so the bundle file is discoverable.

Consider moving the longer code blocks (seed script, mock helper) into the reference file and keeping SKILL.md as a tighter overview to reduce inline bulk.

DimensionReasoningScore

Conciseness

Lean body of executable code with minimal framing; no padded explanations of concepts Claude already knows. Not a 2 because there is no significant unnecessary prose to tighten.

3 / 3

Actionability

Every step ships copy-paste-ready, executable code or commands (seed script, next.config, package.json scripts, vitest mock, Playwright fixture). Not a 2 because none of it is pseudocode or missing key details.

3 / 3

Workflow Clarity

Steps 1-5 are clearly sequenced and the seed script has a feedback loop (422 -> already exists), but there are no explicit validation checkpoints after each step (e.g., verify users in dashboard, confirm HTTPS dev server responds). Capped at 2 because batch/destructive setup lacks explicit verify gates.

2 / 3

Progressive Disclosure

Sections are organized, but the body never signals or links to the bundled references/implementation-guide.md (Resources only points to external docs), leaving that file orphaned, and most content is inline rather than split out.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong description: third-person, concise, with concrete actions, explicit "Use when" guidance, and natural trigger phrases scoped tightly to Clerk local development. No verbosity or over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete actions - "configuring development environment, testing auth locally, or setting up hot reload with Clerk" - rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Set up local development workflow with Clerk") and when ("Use when configuring development environment..." plus a "Trigger with phrases like" clause).

3 / 3

Trigger Term Quality

Provides good coverage of natural phrases users would say: "clerk local dev", "clerk development", "test clerk locally", "clerk dev environment".

3 / 3

Distinctiveness Conflict Risk

Clerk-specific niche with distinct, branded trigger phrases; unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.