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

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A highly actionable, lean skill body with executable code and a useful error-recovery table. It is held back by absent validation checkpoints across its parallel patterns and by monolithic inline content plus an unreferenced bundle file.

Suggestions

Add a brief verification step to each pattern (e.g. 'curl /api/hello with the Bearer token and expect 200 + userId') so the workflow has explicit validation checkpoints.

Link the existing references/quickstart-notes.md from the body (or move the Enterprise Considerations / Express pattern into a reference file) so progressive disclosure is signaled and content is split one level deep.

Trim the redundant Output and Examples sections, which restate the Overview instead of adding new guidance.

Dimension	Reasoning	Score
Conciseness	The body is code-centric and lean, assuming Claude's familiarity with Clerk/Next.js/Express, with high-value inline notes (e.g. the auth() vs currentUser() rate-limit distinction); only the trailing Output/Examples sections are mildly redundant, not enough to drop below the score-3 anchor.	3 / 3
Actionability	Five complete, copy-paste-ready code blocks each with a concrete file path, plus an error-handling table mapping specific errors to solutions — fully executable and specific.	3 / 3
Workflow Clarity	Steps are clearly numbered and the Error Handling table provides recovery guidance, but there are no explicit validation/verification checkpoints and the five steps are parallel patterns rather than one gated pipeline, matching the score-2 anchor.	2 / 3
Progressive Disclosure	Sections are organized with headers, but the body is a ~225-line monolith with multiple full code patterns and enterprise notes kept inline, and the existing references/quickstart-notes.md is never signaled or linked from the body.	2 / 3
	Total	10 / 12 Passed

Description

90%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, third-person description that clearly states what the skill does and when to use it, with concrete Clerk-specific trigger phrases. Its only weakness is that the 'what' names a single action rather than a comprehensive set of capabilities.

Dimension	Reasoning	Score
Specificity	Names the Clerk domain and a concrete action ('Create your first authenticated request with Clerk'), but frames a single action rather than listing multiple specific concrete actions, so it falls short of the score-3 anchor.	2 / 3
Completeness	Explicitly answers both 'what' (create first authenticated request with Clerk) and 'when' ('Use when making initial API calls, testing authentication, or verifying Clerk integration works correctly') with explicit triggers.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('clerk hello world', 'first clerk request', 'test clerk auth', 'verify clerk setup') give good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Clerk-specific triggers carve a clear niche unlikely to fire for unrelated skills; the named phrases are distinct and not generic.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clerk-pack/skills/clerk-hello-world/SKILL.md
Commit: 4c47e33

Reviewed: 1 day 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.