clay-multi-env-setup

Configure Clay integrations across development, staging, and production environments. Use when setting up per-environment Clay tables, managing webhook URLs per environment, or implementing environment-specific enrichment configurations. Trigger with phrases like "clay environments", "clay staging", "clay dev prod", "clay environment setup", "clay config by env".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

92%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, concise body with a well-sequenced workflow and explicit validation/safety checkpoints. Its main weakness is progressive disclosure: bundle reference files exist but are neither linked nor signaled, leaving config detail inline that those files already cover.

Suggestions

Link to the existing reference files (e.g., 'See references/implementation-guide.md for the full config-directory structure') instead of inlining all configuration code, so the overview stays lean and the bundle is actually used.

Surface the implementation.md / implementation-guide.md split under a clearly labeled 'Advanced' or 'Reference' section so navigation is one level deep and well-signaled.

Add an explicit validate->fix->retry note in Step 4 prose (the code fail-fast exits, but a one-line 'fix the reported field and re-run' loop would make the feedback loop explicit rather than implicit).

Dimension	Reasoning	Score
Conciseness	Lean body with no padding explaining what Clay is or basic programming concepts; inline comments encode domain rationale ('Never push dev data to real CRM', 'Small batches to conserve credits') that earns its place.	3 / 3
Actionability	Provides fully executable TypeScript config, Zod validation, bash env files, and GitHub Actions 'gh secret set' commands — copy-paste ready with specific values and a complete config object.	3 / 3
Workflow Clarity	A clearly sequenced 5-step process with explicit validation in Step 4 (Zod safeParse that fail-fast exits on invalid config) and environment-aware safety guards in Step 5, addressing the batch/cross-environment risk the rubric flags.	3 / 3
Progressive Disclosure	The body is well-organized into sections but never references the two provided bundle files (references/implementation.md, references/implementation-guide.md), keeping substantial inline config that overlaps with those files and only pointing outward to another skill (clay-observability).	2 / 3
	Total	11 / 12 Passed

Description

100%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, well-structured description that clearly states concrete capabilities, includes an explicit 'Use when' trigger with natural keyword variations, and occupies a distinct niche. Voice is appropriately third person/imperative with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'setting up per-environment Clay tables, managing webhook URLs per environment, or implementing environment-specific enrichment configurations' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Configure Clay integrations across development, staging, and production environments') and when ('Use when setting up per-environment Clay tables...'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides good coverage of natural phrases a user would say: 'clay environments', 'clay staging', 'clay dev prod', 'clay environment setup', 'clay config by env'.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Clay multi-environment setup) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clay-pack/skills/clay-multi-env-setup/SKILL.md
Commit: 4c47e33

Reviewed: 3 days 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.