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".

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A highly actionable, token-efficient production checklist with concrete code and thresholds. It loses points on workflow clarity (no explicit feedback loops) and progressive disclosure (monolithic single-file layout).

Suggestions

Add explicit feedback loops between phases, e.g. 'If the 500-row sample run yields <60% find rate, fix input quality/provider order before proceeding to Phase 3.'

Move the plan/credit comparison table and the validation/pre-flight scripts into reference files (e.g. references/credit-plans.md, scripts/preflight.sh) and link to them from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is a dense, task-focused checklist with no concept teaching; the TypeScript validation function, bash pre-flight, and plan table each earn their tokens rather than padding.

3 / 3

Actionability

Checklist items carry concrete thresholds (100+ rows, >60% find rate, <500 credits, 50K/webhook) and the code/commands are executable and copy-paste ready.

3 / 3

Workflow Clarity

The six phases give a clear sequence and Phase 2 adds validation gates, but there are no explicit validate→fix→retry feedback loops for these batch operations, which the rubric caps at 2.

2 / 3

Progressive Disclosure

Sections are well organized, but at over 50 lines everything lives inline in one file with no bundle split; the only references are external URLs and another skill rather than one-level-deep bundle files.

2 / 3

Total

10

/

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.

A strong description that clearly states purpose, usage时机, and trigger phrases in third person. Its only weakness is that it names a single action rather than enumerating several concrete capabilities.

Suggestions

Expand the opening sentence to list two or three concrete capabilities (e.g., 'validate table configuration, audit credit budgeting, and verify webhook reliability') to lift specificity to the top anchor.

DimensionReasoningScore

Specificity

Names the domain ('Clay integrations') and one concrete action ('Execute production readiness checklist'), but does not list multiple distinct concrete actions, so it stops short of the top anchor.

2 / 3

Completeness

Explicitly states what it does ('Execute production readiness checklist') and when to use it ('Use when launching... preparing for go-live, or auditing'), with explicit trigger phrases.

3 / 3

Trigger Term Quality

Provides natural phrases a user would say ('clay production', 'clay go-live', 'clay launch checklist', 'deploy clay pipeline'), giving good coverage of likely trigger language.

3 / 3

Distinctiveness Conflict Risk

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

3 / 3

Total

11

/

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.