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".
81
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-prod-checklist/SKILL.mdQuality
Discovery
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 terms, completeness, and distinctiveness by clearly specifying when to use the skill and targeting a narrow niche (Clerk production deployment). However, it falls short on specificity—it doesn't describe what concrete actions or checks the checklist actually performs, leaving the 'what' at a high level.
Suggestions
Add specific concrete actions the checklist covers, e.g., 'Verifies API key configuration, checks webhook endpoints, audits session/token settings, reviews domain and redirect URI setup for Clerk deployment.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'production readiness checklist for Clerk deployment' but does not list any concrete actions like 'verify API keys', 'check webhook configuration', 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 natural trigger phrases like 'clerk production', 'clerk deploy checklist', 'clerk go-live', 'clerk launch ready' which are terms users would naturally say. Also includes relevant keywords like 'deploy', 'production configuration', and 'launch'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Clerk' (a specific auth platform) and 'production readiness checklist'. Unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 checklist with executable validation scripts, CI integration examples, and comprehensive coverage of security, monitoring, and error handling concerns. Its main weakness is that it's a lengthy single file that could benefit from splitting detailed checklists into separate bundle files for better progressive disclosure. The content is mostly concise but includes some items that are self-evident to Claude.
Suggestions
Consider splitting the security, monitoring, and performance checklists into separate bundle files (e.g., SECURITY_CHECKLIST.md, MONITORING.md) and referencing them from the main SKILL.md to improve progressive disclosure.
Remove checklist items that are general best practices Claude already knows (e.g., '.env.local in .gitignore', 'don't show stack traces') to tighten conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured checklists and executable code, but some checklist items are somewhat obvious for Claude (e.g., 'don't show stack traces', '.env.local in .gitignore') and the tables add visual bulk. The validation script is thorough but could be slightly tighter. | 2 / 3 |
Actionability | Excellent actionability — provides a fully executable TypeScript validation script, a complete error boundary component, a CI/CD YAML integration example, and specific environment variable names and key prefixes. Everything is copy-paste ready with concrete commands. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from environment config through validation, security, monitoring, error handling, and performance. The validation script serves as an explicit checkpoint with pass/fail output and a non-zero exit code for CI gating. The error handling table provides a clear feedback loop for common failures. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's quite long for a single file with no bundle files to offload detail into. The security, monitoring, and performance checklists could be separate reference files. External links to Clerk docs are provided but no internal bundle references exist to support progressive disclosure. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%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 | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.