clay-multi-env-setup
Configure Clay across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Clay configurations. Trigger with phrases like "clay environments", "clay staging", "clay dev prod", "clay environment setup", "clay config by env".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-multi-env-setup81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 with explicit trigger guidance and clear 'Use when' clauses. The main weakness is that the capabilities could be more concrete - it describes categories of work (multi-environment deployments, secrets) rather than specific actions (create config files, validate environment variables). The trigger terms are excellent and provide good coverage.
Suggestions
Add more specific concrete actions like 'create environment-specific config files', 'validate environment variables', 'sync secrets between environments' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay environments) and mentions actions like 'setting up multi-environment deployments' and 'configuring per-environment secrets', but lacks specific concrete actions like 'create environment files', 'validate configs', or 'sync secrets'. | 2 / 3 |
Completeness | Clearly answers both what (configure Clay across environments, set up deployments, configure secrets) and when (explicit 'Use when' clause plus 'Trigger with phrases' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clay environments', 'clay staging', 'clay dev prod', 'clay environment setup', 'clay config by env'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Clay tool and environment configuration. The combination of 'Clay' + environment-specific terms creates a clear niche unlikely to conflict with generic deployment or configuration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 excellent code examples and clear configuration structure. The main weaknesses are some redundant sections (Output, Instructions that restate what's shown) and missing validation checkpoints for a workflow that involves production secrets and environment-specific configurations.
Suggestions
Remove or consolidate the 'Output' and 'Instructions' sections - the code examples already demonstrate the workflow clearly
Add explicit validation steps such as 'Verify config loads correctly: `npm run test:config` or manually log getClayConfig() in each environment before deploying'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient with good code examples, but includes some unnecessary sections like the 'Output' bullet list that restates what was already shown, and the 'Instructions' section that adds little value beyond what the code examples already demonstrate. | 2 / 3 |
Actionability | Provides fully executable TypeScript code, complete JSON configuration files, and specific CLI commands for multiple secret managers. All examples are copy-paste ready with clear file paths and structure. | 3 / 3 |
Workflow Clarity | Steps are listed in the Instructions section but lack validation checkpoints. For a multi-environment setup involving secrets and production safeguards, there should be explicit verification steps (e.g., 'Test config loading in each environment before proceeding'). | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, a logical flow from overview to implementation details, and appropriate external references to clay-observability and documentation. Content is appropriately scoped for a single SKILL.md file. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.