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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

92%

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

The body is highly actionable and well-sequenced with validation and safety guards, but progressive disclosure is weak: orphaned, overlapping reference files duplicate inline content instead of being clearly signaled and properly split.

Suggestions

Reference the bundle files from the body — add a section linking to references/implementation.md and references/implementation-guide.md so the detailed patterns are discoverable rather than orphaned.

Deduplicate the per-environment config: the inline src/config/clay.ts in Step 2 overlaps both reference files — keep a concise version inline and move the full resolver and secret-manager patterns into one reference file.

Consolidate the two reference files, which duplicate getClayConfig() and env-config patterns, into a single reference to reduce overlap and navigation friction.

Dimension	Reasoning	Score
Conciseness	The body is lean and dominated by executable code with purposeful, non-fluff comments; it does not explain concepts Claude already knows and avoids padded prose.	3 / 3
Actionability	Provides fully executable TypeScript (getClayConfig, Zod validation, safety guards) and copy-paste bash commands (gh secret set) with specific, concrete examples.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with an explicit validation checkpoint (Zod fail-fast) and environment-aware safety guards, plus an error-handling table mapping causes to solutions.	3 / 3
Progressive Disclosure	Two bundle files (references/implementation.md, references/implementation-guide.md) exist but are never referenced or signaled from the body, and their content heavily duplicates the inline Step 2 config rather than being appropriately split.	2 / 3
	Total	11 / 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.

The description is specific, complete, and distinctive, clearly stating both the capability and the use-conditions with explicit trigger phrases. It is a strong, well-targeted skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "setting up per-environment Clay tables", "managing webhook URLs per environment", and "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 explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ("clay staging", "clay environments", "clay environment setup") with reasonable coverage, though a couple ("clay dev prod", "clay config by env") are slightly jargon-flavored.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Clay multi-environment isolation) with Clay-specific triggers, making conflict with unrelated skills unlikely.	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
Commit: 02d6341

Reviewed: 2 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.