CtrlK
BlogDocsLog inGet started
Tessl Logo

clay-prod-checklist

Execute production readiness checklist for Clay integrations. Use when launching Clay-powered enrichment pipelines, preparing for go-live, or auditing production Clay configurations. Trigger with phrases like "clay production", "clay go-live", "clay launch checklist", "clay production readiness", "deploy clay pipeline".

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, concise checklist skill with executable code and concrete thresholds. Its main weaknesses are the absence of an explicit gated validation feedback loop for the batch webhook workflow and a monolithic inline structure with no progressive disclosure to separate reference files.

Suggestions

Add an explicit gated feedback loop to the webhook submission flow — e.g., a 'run pre-flight checks; only proceed to bulk submission when all checks pass; halt and remediate on failure' step — to raise workflow clarity for the batch operation.

Split the inline TypeScript validation function and bash pre-flight script into files under scripts/ and reference them from the body, so SKILL.md stays a lean overview and content is one level deep.

Consider moving the credit-plan table and error-handling matrix into a references/ file (e.g. reference.md) linked from the relevant phases to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and task-focused — tight one-line checklist items and executable code — with no padding explaining concepts Claude already knows about Clay or enrichment.

3 / 3

Actionability

Provides a fully executable TypeScript validateForProduction function, runnable bash pre-flight curl checks, and concrete numeric thresholds ("< 500 credits remaining", "> 60% email find rate", "50K/webhook") that are copy-paste ready.

3 / 3

Workflow Clarity

The six sequenced phases and pre-flight checks give a clear structure, but the batch webhook-submission workflow lacks an explicit "only proceed when validation passes" gated feedback loop, which the rubric caps at 2 for batch operations.

2 / 3

Progressive Disclosure

Sections are well organized, but at ~140 lines everything is inline with no real bundle files (references/scripts/assets are absent); the code blocks, credit-plan table, and error matrix could be split into referenced files rather than kept monolithic.

2 / 3

Total

10

/

12

Passed

Description

100%

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 description that concisely states what the skill does, when to use it, and lists natural trigger phrases in third-person imperative voice. All four dimensions hit the top anchor with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Execute production readiness checklist", "launching Clay-powered enrichment pipelines", "preparing for go-live", "auditing production Clay configurations" — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ("Execute production readiness checklist for Clay integrations") and when ("Use when launching Clay-powered enrichment pipelines...") with explicit triggers, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Provides five natural user phrases ("clay production", "clay go-live", "clay launch checklist", "clay production readiness", "deploy clay pipeline") giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Clay-specific niche with distinct clay-prefixed triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.