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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

92%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 and well-sequenced with strong verification and error-recovery guidance. Its main weakness is progressive disclosure: a detailed implementation-guide.md bundle exists but is never referenced, and substantial platform configuration is duplicated both inline and in the bundle rather than cleanly split.

Suggestions

Link the bundle from the body — e.g., add 'See [implementation-guide.md](references/implementation-guide.md) for per-platform config files and the deployment checklist' under a dedicated section — so the existing reference is signaled and discoverable.

De-duplicate the platform configuration between SKILL.md and references/implementation-guide.md: keep concise quick-start commands inline and move the fuller platform configs (vercel.json, netlify.toml, railway.json, amplify.yml) exclusively to the bundle, referencing them from the body.

Fix the broken Resources entries — 'Deploy to Netlify' and 'Clerk Domain Configuration' are plain text without links; either make them real links or point them at the corresponding bundle sections.

Dimension	Reasoning	Score
Conciseness	The body is a lean reference of commands and config with minimal prose and no explanations of concepts Claude already knows (no 'what Clerk is' or 'how deployment works' padding), so every section earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready guidance — `vercel env add`, `netlify env:set`, `railway variables set`, a complete Dockerfile, docker-compose.yml, and a verification script — matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and capped by a dedicated Step 5 post-deployment verification script, with an error-handling table mapping failures to fixes that serves as a recovery feedback loop.	3 / 3
Progressive Disclosure	The body is well-sectioned, but the bundle file references/implementation-guide.md is never linked or signaled from the body, and its platform-by-platform content is largely duplicated inline rather than split out, fitting the 'content that should be separate is inline; references not clearly signaled' anchor.	2 / 3
	Total	11 / 12 Passed

Description

90%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, well-structured description that clearly states what it does and when to use it with natural trigger phrases. Its only weakness is specificity, as it describes a single high-level action rather than enumerating multiple concrete capabilities.

Suggestions

Replace the single verb 'Configure Clerk for deployment' with a short list of concrete actions (e.g., 'Configure Clerk environment variables, dashboard domains, webhook endpoints, and production URLs for deployment on Vercel, Netlify, Railway, and Docker') to reach the 'multiple specific concrete actions' anchor.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — "Configure Clerk for deployment on various platforms" — but does not list multiple specific concrete actions, so it sits at the 'names domain and some actions' anchor rather than the 'lists multiple specific concrete actions' level.	2 / 3
Completeness	It explicitly answers both what ("Configure Clerk for deployment on various platforms") and when ("Use when deploying to Vercel, Netlify, Railway..." plus an explicit trigger-phrases clause), satisfying the highest anchor.	3 / 3
Trigger Term Quality	It provides good coverage of natural terms a user would actually say — "deploy clerk", "clerk Vercel", "clerk Netlify", "clerk production deploy", "clerk Railway" — matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	Clerk combined with named hosting platforms is a clear niche with distinct triggers, making it unlikely to fire for an unrelated skill.	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
Path: plugins/saas-packs/clerk-pack/skills/clerk-deploy-integration/SKILL.md
Commit: 0540a62

Reviewed: about 18 hours 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.