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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
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 that clearly identifies its niche (Clay environment configuration), provides explicit trigger guidance with natural phrases, and answers both what and when questions. The main weakness is that the specific capabilities listed are somewhat generic configuration actions rather than highly concrete operations, though the domain specificity of Clay compensates for this.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay integrations across environments) and some actions (setting up per-environment tables, managing webhook URLs, implementing enrichment configurations), but the actions are somewhat generic configuration tasks rather than highly specific concrete operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Clay integrations across dev/staging/prod environments, manage webhook URLs, implement enrichment configs) and 'when' (explicit 'Use when' clause plus 'Trigger with phrases like' section providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'clay environments', 'clay staging', 'clay dev prod', 'clay environment setup', 'clay config by env' which are natural terms a user would say. Also includes natural keywords like 'webhook URLs', 'enrichment configurations', and environment names (development, staging, production). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Clay' (a specific product) with environment-specific configuration creates a very clear niche that is unlikely to conflict with other skills. The trigger terms are specific enough to avoid false matches. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable code examples, clear multi-step workflow, and good safety considerations for multi-environment setups. Its main weakness is moderate verbosity — the Prerequisites section and some explanatory comments could be trimmed, and the inline code could benefit from being split into referenced bundle files for better progressive disclosure. The validation and safety guard patterns are particularly strong.
Suggestions
Remove the Prerequisites section — Claude already understands environment variables, webhooks, and Clay workspace concepts.
Consider extracting the TypeScript code blocks into bundle files (e.g., config/clay.ts, config/validate.ts, clay/guards.ts) and referencing them from the SKILL.md to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but includes some unnecessary content like the Prerequisites section (Claude knows what env vars and webhooks are), and the interface/type definitions add verbosity. The error handling table is useful but some entries are obvious. | 2 / 3 |
Actionability | Provides fully executable TypeScript code, concrete bash commands for secret management, specific env file examples, and a complete Zod validation schema. All code is copy-paste ready with realistic placeholder values and clear configuration patterns. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence from table creation through safety guards, with explicit validation at Step 4 (Zod schema validation with fail-fast behavior) and safety guards at Step 5 that prevent cross-environment data leaks. The error handling table provides a feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's fairly long and monolithic for a single file with no bundle. The configuration code, validation, and guards could be split into referenced files. The 'Next Steps' reference to `clay-observability` is good but there's only one outward reference. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.