CtrlK
BlogDocsLog inGet started
Tessl Logo

clerk-install-auth

Install and configure Clerk SDK/CLI authentication. Use when setting up a new Clerk integration, configuring API keys, or initializing Clerk in your project. Trigger with phrases like "install clerk", "setup clerk", "clerk auth", "configure clerk API key", "add clerk to project".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with complete, executable code and a clear step sequence, but it is dense for a single SKILL.md and lacks validation checkpoints and progressive disclosure through external references. Tightening and externalizing framework-specific material would lift conciseness and progressive disclosure.

Suggestions

Move the React SPA and Express setup variants into separate reference files and link to them from the main Next.js flow to improve progressive disclosure and conciseness.

Add explicit validation checkpoints between steps (e.g., 'After Step 2, verify keys are loaded'; 'After Step 4, confirm middleware protects a private route') to create a feedback loop rather than relying on the reactive error table.

Trim inline boilerplate in the ClerkProvider and sign-in/up page examples to the minimum needed, since Claude can expand standard patterns.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste code, but it is lengthy and leans toward completeness over brevity, e.g. fully inlining ClerkProvider, middleware, sign-in/up pages, plus React SPA and Express variants and a six-row error table — some of which could be externalized.

2 / 3

Actionability

Provides fully executable, specific, copy-paste-ready code and commands across Next.js, React, and Express (npm install steps, .env vars, ClerkProvider, middleware, route handlers), matching the highest anchor.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1–6) and there is a verification endpoint, but the setup workflow lacks explicit validation checkpoints or a feedback loop confirming each step succeeded before proceeding — the error table is reactive, not a checkpoint.

2 / 3

Progressive Disclosure

Content is well-organized into sections, but everything is inlined in one ~225-line SKILL.md with no bundle files; the framework variants (React SPA, Express) and error reference could be split out and signaled as one-level-deep references.

2 / 3

Total

9

/

12

Passed

Description

100%

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 is strong: it names concrete actions, provides explicit user-facing trigger phrases, and answers both what and when. It occupies a clear Clerk-specific niche with low conflict risk.

DimensionReasoningScore

Specificity

States concrete actions ('Install and configure Clerk SDK/CLI authentication') and lists several setup activities (configuring API keys, initializing Clerk in a project), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both 'what' (install and configure Clerk SDK/CLI authentication) and 'when' via an explicit 'Use when...' clause plus trigger phrases, satisfying the highest anchor.

3 / 3

Trigger Term Quality

Provides explicit trigger phrases users would naturally say — 'install clerk', 'setup clerk', 'clerk auth', 'configure clerk API key', 'add clerk to project' — giving good natural coverage.

3 / 3

Distinctiveness Conflict Risk

The Clerk-specific trigger phrases and narrow scope make it unlikely to conflict with unrelated skills, fitting the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 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

Total

14

/

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.