apollo-multi-env-setup
Configure Apollo.io multi-environment setup. Use when setting up development, staging, and production environments, or managing multiple Apollo configurations. Trigger with phrases like "apollo environments", "apollo staging", "apollo dev prod", "apollo multi-tenant", "apollo env config".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-multi-env-setup84
Quality
77%
Does it follow best practices?
Impact
100%
1.72xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-multi-env-setup/SKILL.mdDiscovery
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 excellent trigger term coverage and clear when/what guidance. The main weakness is the lack of specific concrete actions - it describes the general purpose but not the specific operations the skill enables (e.g., creating config files, setting environment variables, validating setups).
Suggestions
Add 2-3 specific concrete actions like 'Creates environment-specific config files, manages API key rotation across environments, validates environment parity'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io multi-environment setup) and mentions some actions (setting up environments, managing configurations), but lacks concrete specific actions like 'create config files', 'sync settings', or 'validate environment variables'. | 2 / 3 |
Completeness | Clearly answers both what (configure Apollo.io multi-environment setup) and when (setting up dev/staging/prod environments, managing multiple configs) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'apollo environments', 'apollo staging', 'apollo dev prod', 'apollo multi-tenant', 'apollo env config'. Good coverage of variations including shorthand terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Apollo.io multi-environment configuration. The combination of 'Apollo' + environment-specific terms creates distinct triggers unlikely to conflict with general environment or configuration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, production-ready code for Apollo multi-environment setup with excellent TypeScript and Kubernetes examples. However, it's verbose with repetitive configuration patterns that could be templated, and lacks a clear step-by-step setup workflow. The content would benefit from splitting detailed configs into separate reference files.
Suggestions
Add a numbered 'Setup Workflow' section at the top with explicit steps: 1) Create env files, 2) Configure secrets, 3) Validate with validateEnvironment(), 4) Deploy ConfigMaps
Consolidate the three nearly-identical Kubernetes ConfigMaps into a single template with environment-specific values table, reducing repetition
Move detailed Kubernetes manifests and the full EnvironmentAwareApolloClient to separate reference files (e.g., K8S_CONFIGS.md, CLIENT.md) and keep only the core pattern in SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides comprehensive configuration examples but is verbose with repetitive patterns across environments. The three nearly-identical Kubernetes ConfigMaps and environment configs could be condensed with a template approach, and some code comments explain obvious behavior. | 2 / 3 |
Actionability | Excellent executable code throughout - complete TypeScript configurations with Zod validation, working Kubernetes manifests, bash scripts, and test examples. All code is copy-paste ready with realistic values and proper imports. | 3 / 3 |
Workflow Clarity | The environment promotion script shows a clear sequence with validation, but the overall setup workflow lacks explicit step-by-step guidance. There's no clear 'start here' sequence for initial setup, and validation checkpoints for the configuration process are implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a helpful overview table, but the skill is monolithic with ~300 lines of inline code. The Kubernetes configs and detailed client implementation could be split into referenced files, with SKILL.md providing just the core pattern. | 2 / 3 |
Total | 9 / 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 | |
- 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.