clay-prod-checklist
Execute Clay production deployment checklist and rollback procedures. Use when deploying Clay integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "clay production", "deploy clay", "clay go-live", "clay launch checklist".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-prod-checklist91
Does it follow best practices?
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger term coverage and clear when/what guidance. The main weakness is the lack of specific concrete actions - it describes categories of work (checklist, rollback) rather than the actual steps involved. The Clay-specific terminology provides strong distinctiveness.
Suggestions
Add 2-3 specific concrete actions to improve specificity, e.g., 'Execute Clay production deployment checklist including environment verification, integration testing, and rollback procedures'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay production deployment) and mentions some actions (checklist, rollback procedures), but doesn't list specific concrete actions like 'verify environment variables', 'run smoke tests', or 'backup database'. | 2 / 3 |
Completeness | Clearly answers both what (execute deployment checklist and rollback procedures) and when (deploying to production, preparing for launch, go-live procedures) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clay production', 'deploy clay', 'clay go-live', 'clay launch checklist'. Good coverage of variations including both technical and business terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining 'Clay' product name with 'production deployment' context. The explicit trigger phrases with 'clay' prefix make it highly unlikely to conflict with generic deployment or other product skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality production deployment skill with excellent actionability and workflow clarity. The checklist format is appropriate for the use case, code examples are executable, and the gradual rollout process includes proper validation checkpoints. Minor improvement could be made by extracting detailed code examples to separate files for better progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with checklist format, executable code blocks, and no unnecessary explanations. Every section serves a clear purpose without padding. | 3 / 3 |
Actionability | Provides fully executable bash commands for deployment, TypeScript code for health checks, and specific kubectl commands. Checklists are concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation checkpoints (pre-flight checks, canary monitoring, gradual rollout pauses). Includes rollback procedure and error handling table with severity levels. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is somewhat monolithic. The detailed deployment commands and health check implementation could be split into separate reference files, with SKILL.md serving as a lighter overview. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.