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

78%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

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, highly actionable production readiness skill with executable validation scripts, CI integration examples, and well-structured checklists. Its main weakness is that it packs a lot of content into a single file without leveraging progressive disclosure through supporting bundle files. Minor verbosity in the Output section and some redundancy between the error handling table and the validation script slightly reduce conciseness.

Suggestions

Split the security, monitoring, error handling, and performance checklists into separate referenced files (e.g., SECURITY.md, MONITORING.md) to improve progressive disclosure and reduce the main file's length.

Remove the 'Output' section as it merely restates what the checklists already cover, improving conciseness.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and executable code, but some sections are slightly verbose — the Output section restates what the checklists already cover, and some checklist items could be more terse. The error handling table at the bottom partially duplicates information from the validation script.	2 / 3
Actionability	Highly actionable with a fully executable TypeScript validation script, a concrete CI/CD YAML integration example, a copy-paste-ready error boundary component, and specific environment variable names and commands. Every checklist item has a concrete action.	3 / 3
Workflow Clarity	The steps are clearly sequenced from environment configuration through security, monitoring, error handling, and performance. The validation script in Step 2 serves as an explicit checkpoint with pass/fail output and a non-zero exit code for CI gating, providing a clear feedback loop before deployment.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but it's a long monolithic file (~180 lines of substantive content) with no bundle files to offload detail into. The security, monitoring, error handling, and performance checklists could each be separate referenced files. The Resources section links to external docs but doesn't reference any local supporting files.	2 / 3
	Total	10 / 12 Passed

Description

79%

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 excels at trigger term coverage and completeness, clearly specifying when to use the skill with explicit trigger phrases. Its main weakness is the lack of specificity about what concrete actions or checks the skill performs—it says 'checklist' without enumerating any checklist items. The narrow domain (Clerk deployment) makes it highly distinctive despite the vague capability description.

Suggestions

Add specific concrete actions the checklist covers, e.g., 'Verifies API key configuration, checks webhook endpoints, audits session and token settings, reviews domain and redirect URL setup for Clerk deployment.'

Dimension	Reasoning	Score
Specificity	The description says 'production readiness checklist' but does not list any concrete actions like 'verify API keys', 'check webhook configurations', or 'audit session settings'. It remains abstract about what the checklist actually covers.	1 / 3
Completeness	Clearly answers both 'what' (production readiness checklist for Clerk deployment) and 'when' (preparing to deploy, reviewing production configuration, auditing before launch) with explicit trigger phrases provided.	3 / 3
Trigger Term Quality	Includes explicit trigger phrases like 'clerk production', 'clerk deploy checklist', 'clerk go-live', 'clerk launch ready', plus natural terms like 'deploy', 'production configuration', and 'launch'. These are terms users would naturally say.	3 / 3
Distinctiveness Conflict Risk	The combination of 'Clerk' (a specific authentication platform) with 'production readiness checklist' and deployment-specific triggers creates a very distinct niche unlikely to conflict with other skills.	3 / 3
	Total	10 / 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: about 17 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.