clerk-multi-env-setup

Configure Clerk for multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing multiple Clerk instances, or implementing environment promotion. Trigger with phrases like "clerk environments", "clerk staging", "clerk dev prod", "clerk multi-environment".

Quality

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

This is a strong, actionable skill with clear step-by-step workflows and executable code throughout. The validation step (Step 4) is particularly well done, providing key mismatch detection and environment safety checks. The main weakness is that the content is somewhat long for a single SKILL.md — some sections like the webhook handler and CI/CD config could be split into supporting files — and there's minor verbosity in the Prerequisites and Output sections.

Suggestions

Consider moving the webhook handler (Step 5) and CI/CD config (Step 6) into separate referenced files to improve progressive disclosure and reduce the main file's length.

Remove the Prerequisites section and Output section — the prerequisites are implicit from the steps, and the output section restates what the steps already demonstrate.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary sections like the Prerequisites list (Claude knows what's needed from context) and the Output section which largely restates what the steps already cover. The error handling table adds value but the overall content could be tightened.	2 / 3
Actionability	Every step includes fully executable, copy-paste ready code — TypeScript configuration, environment files, webhook handlers, and CI/CD YAML. The table in Step 1 gives concrete key prefixes and domains, and the Vercel preview example provides specific CLI commands.	3 / 3
Workflow Clarity	The six steps are clearly sequenced from instance creation through CI/CD deployment. Step 4 provides explicit validation with key mismatch detection and environment warnings, creating a feedback loop that catches configuration errors at startup before they cause runtime failures.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections, but it's fairly long and monolithic — the webhook handler code and CI/CD config could reasonably be split into referenced files. The Resources section links to external docs, and there's a reference to clerk-observability, but no bundle files exist to support progressive disclosure.	2 / 3
	Total	10 / 12 Passed

Description

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 well-structured skill description with strong completeness and distinctiveness. It clearly identifies when to use the skill with explicit trigger phrases and a 'Use when' clause. The main weakness is that the capability descriptions could be more concrete—listing specific actions rather than somewhat abstract tasks like 'managing multiple Clerk instances'.

Suggestions

Add more concrete specific actions such as 'configure API keys per environment', 'set up webhook endpoints for each stage', or 'migrate Clerk settings between environments' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (Clerk multi-environment configuration) and some actions (setting up environment-specific configurations, managing multiple instances, implementing environment promotion), but doesn't list concrete specific actions like 'create API keys per environment' or 'sync webhook endpoints across stages'.	2 / 3
Completeness	Clearly answers both 'what' (configure Clerk for multiple environments, manage instances, implement environment promotion) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' section providing concrete trigger guidance).	3 / 3
Trigger Term Quality	Includes natural trigger terms users would actually say: 'clerk environments', 'clerk staging', 'clerk dev prod', 'clerk multi-environment', plus contextual phrases like 'environment-specific configurations' and 'environment promotion'. Good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Highly specific niche combining Clerk (a specific auth provider) with multi-environment configuration. Very unlikely to conflict with other skills due to the narrow domain focus and specific trigger terms.	3 / 3
	Total	11 / 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: 02d6341

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