clerk-deploy-integration

Configure Clerk for deployment on various platforms. Use when deploying to Vercel, Netlify, Railway, or other platforms, or when setting up production environment. Trigger with phrases like "deploy clerk", "clerk Vercel", "clerk Netlify", "clerk production deploy", "clerk Railway".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

77%

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

A highly actionable, well-sequenced deployment guide with strong executable examples and a real verification step. Its weaknesses are minor redundancy in the Examples section and poor use of the existing reference bundle, which is never linked from the body.

Suggestions

Link to `references/implementation-guide.md` from the body (e.g. a "## Detailed implementation" section pointing to it) and move the deeper per-platform code patterns there, keeping SKILL.md as a lean overview.

Remove the duplicated Vercel env-add commands from the Examples section or replace them with a genuinely distinct scenario (e.g. preview-vs-production key rotation).

Fix the Resources list so every entry is a real link, or drop the unlinked "Deploy to Netlify" and "Clerk Domain Configuration" placeholders.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands and code, but the Examples section duplicates the Vercel env-add commands already shown in Step 1, the Netlify section includes a full tangential TypeScript handler, and the Resources list contains unlinked placeholder entries ("Deploy to Netlify", "Clerk Domain Configuration"), so it could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands and complete scripts across every platform — `vercel env add`, `netlify env:set`, `railway variables set`, a multi-stage Dockerfile, docker-compose, and a `verify-deployment.sh` script with `set -euo pipefail`.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced per platform and capped by an explicit post-deployment verification step (Step 5) with concrete HTTP checks, plus an Error Handling table mapping errors to causes and solutions that serves as a feedback loop.	3 / 3
Progressive Disclosure	A bundle file `references/implementation-guide.md` exists but is never referenced or linked from the body, and the detailed per-platform implementation is kept inline rather than split out, matching the anchor of references present but not clearly signaled with content that should be separate left inline.	2 / 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.

A strong description that clearly communicates its niche and explicit trigger guidance with natural user phrases. Its only weakness is specificity: it summarizes the work as a single "Configure" action rather than listing the concrete deployment tasks it covers.

Suggestions

Expand the "what" clause to list concrete actions, e.g. "Configure Clerk environment variables, dashboard domains/URLs, and webhook endpoints for deployment on Vercel, Netlify, Railway, and Docker."

Optionally mention the post-deployment verification capability in the description so the skill's scope is fully conveyed up front.

Dimension	Reasoning	Score
Specificity	The description names the domain and one action ("Configure Clerk for deployment on various platforms") but does not enumerate multiple concrete actions like env-var configuration, domain setup, or webhook configuration, so it stops at naming domain and some actions rather than a comprehensive list.	2 / 3
Completeness	It states what the skill does ("Configure Clerk for deployment on various platforms") and provides an explicit "Use when deploying to Vercel, Netlify, Railway, or other platforms, or when setting up production environment" trigger, answering both what and when.	3 / 3
Trigger Term Quality	It explicitly enumerates natural phrases users would say — "deploy clerk", "clerk Vercel", "clerk Netlify", "clerk Railway", "clerk production deploy" — giving good coverage of likely trigger terms.	3 / 3
Distinctiveness Conflict Risk	The Clerk-plus-deployment niche and triggers that combine "clerk" with specific platform names make it clearly distinguishable and unlikely to fire for unrelated skills.	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 — 13 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

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