clerk-prod-checklist

Production readiness checklist for Clerk deployment. Use when preparing to deploy, reviewing production configuration, or auditing Clerk implementation before launch. Trigger with phrases like "clerk production", "clerk deploy checklist", "clerk go-live", "clerk launch ready".

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/clerk-pack/skills/clerk-prod-checklist/SKILL.md

Quality

Content

65%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 content is highly actionable with executable validation code and well-structured checklists, but it leans verbose due to inline code duplicated in the bundle and lacks explicit feedback loops and clear signaling of the bundled reference file.

Suggestions

Replace the lengthy inline validation script and error.tsx block with concise summaries and link to references/implementation-guide.md, which already contains these details, to reduce duplication and tighten conciseness.

Add an explicit feedback loop: instruct the user to fix failing checks from the validation script and re-run until all pass before proceeding to deploy, which would lift workflow clarity.

Link the bundled implementation guide in the body (e.g., 'See [implementation-guide.md](references/implementation-guide.md) for full configuration examples') so progressive disclosure is clearly signaled rather than leaving the reference unlinked.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient tables and a single inline validation script, but it includes a lengthy inline TypeScript block and an error.tsx example that also appears in the bundled implementation guide, adding redundancy; it is not score 1 because it avoids concept explanations Claude already knows, and not score 3 because the duplicated and long inline blocks could be tightened or deferred to the reference.	2 / 3
Actionability	It provides a complete, copy-paste-ready TypeScript validation script, an explicit run command ('npx tsx scripts/prod-readiness.ts'), a CI workflow snippet, and an error boundary component; it is not score 2 because the guidance is fully executable rather than pseudocode or abstract direction.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1 through Step 6) and the validation script acts as a checkpoint with pass/fail exit codes, but there is no explicit fix-and-re-run feedback loop tying a failed check back to remediation; it is not score 1 because the sequence and a validation checkpoint are present, and not score 3 because the recovery loop is implicit rather than explicit.	2 / 3
Progressive Disclosure	A one-level-deep bundled reference (references/implementation-guide.md) exists, but the body never signals or links to it, instead linking external docs in Resources and pointing to a different skill in Next Steps; it is not score 1 because there is some organization and a real reference file, and not score 3 because the reference is not clearly signaled from the overview.	2 / 3
	Total	9 / 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.

The description is well-constructed: it states both what the skill does and when to use it, with natural trigger phrases and a clear Clerk-specific niche. Its only weakness is that the stated actions are broad phases rather than a rich list of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the Clerk deployment domain and a few actions ('preparing to deploy, reviewing production configuration, or auditing Clerk implementation') but does not enumerate multiple distinct concrete actions like the score-3 anchor; it is not score 1 because it specifies concrete domain activities, and not score 3 because the actions are broad phases rather than a list of specific operations.	2 / 3
Completeness	It explicitly answers both what ('Production readiness checklist for Clerk deployment') and when ('Use when preparing to deploy... or auditing Clerk implementation before launch') with explicit triggers, matching the score-3 anchor; it is not score 2 because the 'when' is explicit rather than merely implied.	3 / 3
Trigger Term Quality	Phrases like 'clerk production', 'clerk deploy checklist', 'clerk go-live', and 'clerk launch ready' are natural terms users would say, giving good coverage; it is not score 2 because the trigger list covers several common variations rather than only one or two.	3 / 3
Distinctiveness Conflict Risk	It targets a clear Clerk-specific niche with distinct triggers unlikely to fire for unrelated skills; it is not score 2 because the Clerk-scoped phrasing is specific enough to avoid overlap with generic deployment 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: 3 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clerk-pack/skills/clerk-prod-checklist/SKILL.md
Commit: 4c47e33

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.