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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The body delivers highly actionable, executable code across five well-organized scenarios with genuinely useful non-obvious guidance on rate limits and trade-offs. Its weaknesses are conciseness (some restating prose and a dated version note) and workflow clarity (no explicit validation/feedback checkpoints, though the task is low-risk and non-destructive).

Suggestions

Tighten the conciseness by trimming the 'Key distinction' paragraph where it restates the inline code comments, and move the time-sensitive 'Session token v2 (default since April 2025)' detail into a dedicated 'Version notes' section so it does not penalize conciseness.

Add an explicit validation/feedback step to the workflow — e.g., after Step 2's API route, instruct the reader to call `GET /api/hello` and confirm a 401 when signed out and a 200 with userId when signed in — to lift workflow clarity above level 2.

Consider extracting the Express.js example (Step 5) and Enterprise Considerations into a referenced file (e.g. references/express-and-enterprise.md) to keep the core Next.js flow leaner and reinforce progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basics Claude already knows, using code comments to convey non-obvious distinctions (auth() vs currentUser() cost/rate limits). It is not level 3 because some prose restates what the code shows and a time-sensitive note ("default since April 2025") could be trimmed; it is not level 1 because it is not padded with introductory explanations.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript and Express code across server components, API routes, client hooks, and server actions, with file paths annotated (e.g. `// app/dashboard/page.tsx`).	3 / 3
Workflow Clarity	Five steps are clearly numbered and sequenced, but there are no explicit validation checkpoints or feedback loops; the Error Handling table provides recovery guidance but no verify-then-proceed cycle, matching the 'steps listed but validation gaps' anchor rather than level 3.	2 / 3
Progressive Disclosure	All content lives in a single, well-organized SKILL.md with clean sections (Overview, Prerequisites, Steps, Error Handling, Enterprise, Resources, Next Steps) and navigational pointers to the next skill and external docs; for a single-purpose skill with no external bundle files, this level of organization warrants level 3.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 states a concrete purpose, provides explicit 'Use when' triggers, and lists natural trigger phrases a user would actually say. The only weak spot is specificity, which describes a single action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain (Clerk) and a concrete action ("Create your first authenticated request") but does not list multiple distinct actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	Explicitly answers both 'what' (create your first authenticated request with Clerk) and 'when' ("Use when making initial API calls, testing authentication, or verifying Clerk integration works correctly"), with explicit triggers — matching the level 3 anchor structure.	3 / 3
Trigger Term Quality	Provides explicit natural trigger phrases users would actually say ("clerk hello world", "first clerk request", "test clerk auth", "verify clerk setup"), giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (first authenticated Clerk request / integration verification) with Clerk-specific triggers, making it unlikely to fire for unrelated skills.	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
Commit: 6e3a65f

Reviewed: 5 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.