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

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-install-auth/SKILL.md

Quality

Discovery

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. Its main weakness is that the capability description could be more specific about what concrete actions are performed beyond 'install and configure.' The explicit trigger phrases and clear 'Use when' clause make it very effective for skill selection.

Suggestions

Expand the specificity of actions, e.g., 'Install Clerk SDK packages, set environment variables for API keys, initialize Clerk middleware, and configure authentication providers.'

Dimension	Reasoning	Score
Specificity	Names the domain (Clerk SDK/CLI authentication) and some actions (install, configure), but doesn't list multiple concrete actions beyond install/configure. Missing specifics like what configuration entails (e.g., setting environment variables, initializing middleware, adding provider wrappers).	2 / 3
Completeness	Clearly answers both 'what' (install and configure Clerk SDK/CLI authentication) and 'when' (setting up new Clerk integration, configuring API keys, initializing Clerk) with explicit trigger phrases.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'install clerk', 'setup clerk', 'clerk auth', 'configure clerk API key', 'add clerk to project'. These are phrases users would naturally say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Very specific to Clerk authentication setup. The combination of 'Clerk' as a named product with specific actions like SDK installation and API key configuration makes it highly unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

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, highly actionable skill with executable code for multiple frameworks and a useful error handling table. Its main weaknesses are that it tries to cover too many frameworks in a single file (hurting conciseness and progressive disclosure) and lacks explicit validation checkpoints between steps beyond the final health check. The content would benefit from splitting framework-specific setups into separate referenced files.

Suggestions

Split React SPA and Express setup sections into separate referenced files (e.g., CLERK_REACT.md, CLERK_EXPRESS.md) to keep the main skill focused on Next.js and improve progressive disclosure.

Add an explicit validation checkpoint after Step 2, such as running `npx next dev` and checking console output for Clerk initialization confirmation.

Remove the overview paragraph—it restates the skill description and adds no new information for Claude.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some unnecessary verbosity. The overview paragraph restates what the description already covers. The code examples are mostly lean, but covering Next.js, React SPA, and Express in one skill makes it longer than needed—some of this could be split into separate files. The enterprise considerations and error table add value but push the token count.	2 / 3
Actionability	Every step includes fully executable, copy-paste-ready code with correct file paths, imports, and configurations. The error handling table provides specific causes and solutions. The code covers multiple frameworks with real, working examples rather than pseudocode.	3 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced for the Next.js path, and Step 6 provides a verification endpoint. However, there's no explicit validation checkpoint after Step 2 (e.g., confirming env vars are loaded) or after Step 4 (confirming middleware is active). The React SPA and Express setups are appended without clear sequencing or verification steps of their own.	2 / 3
Progressive Disclosure	The content is well-structured with clear headings, but it's monolithic—all three framework setups (Next.js, React, Express) are inline rather than split into separate files. The 'Next Steps' reference to `clerk-hello-world` is good, but the React SPA and Express sections could be separate referenced files to keep the main skill focused. No bundle files exist to offload content to.	2 / 3
	Total	9 / 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: 3a2d27d

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.