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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%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.

The body is highly actionable with a clear validated workflow, but it is hurt by redundancy: a reference bundle exists yet is unreferenced and duplicates the inline steps. Tightening the overlap would materially improve both conciseness and progressive disclosure.

Suggestions

Link references/implementation-guide.md from the body (e.g., a '## Detailed implementation' section) and trim the duplicated Steps 1–6 so the SKILL.md body stays a lean overview.

Decide a single source of truth for the env-config and webhook code — keep one canonical version inline or in the reference, not both — to remove the token redundancy.

Add a one-line pointer near the top noting the implementation guide exists, so the reference is clearly signaled rather than undiscoverable.

Dimension	Reasoning	Score
Conciseness	Sections are mostly lean code with little concept explanation, but the body (~215 lines) substantially duplicates Steps 1–6 that also appear in references/implementation-guide.md, so tokens are not all earning their place.	2 / 3
Actionability	Each step ships fully executable, copy-paste-ready TypeScript/bash/YAML with explicit file paths (lib/clerk-config.ts, app/layout.tsx, .github/workflows/deploy.yml) — no pseudocode.	3 / 3
Workflow Clarity	Six clearly numbered, sequential steps include an explicit startup-validation step (Step 4) plus an error-handling table mapping errors to causes and solutions for recovery.	3 / 3
Progressive Disclosure	Sections are well organized, but the bundle file references/implementation-guide.md is never linked or signaled from the body and largely duplicates inline content instead of extending it; content that should be separate remains inline.	2 / 3
	Total	10 / 12 Passed

Description

100%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 explicitly covers capabilities, use-when triggers, and natural trigger phrases with minimal padding. It is distinguishable and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Configure Clerk for multiple environments", "setting up environment-specific configurations", "managing multiple Clerk instances", "implementing environment promotion" — rather than vague language.	3 / 3
Completeness	Clearly states what it does ("Configure Clerk for multiple environments") and when to use it ("Use when setting up... managing... or implementing environment promotion") with explicit triggers, satisfying both requirements.	3 / 3
Trigger Term Quality	Explicit trigger phrases ("clerk environments", "clerk staging", "clerk dev prod", "clerk multi-environment") are natural terms a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The Clerk + multi-environment niche is specific and the triggers are Clerk-scoped, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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-multi-env-setup/SKILL.md
Commit: 4c47e33

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