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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-multi-env-setup/SKILL.mdQuality
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 strong completeness and trigger term coverage. It clearly identifies both when to use the skill and provides explicit trigger phrases. The main weakness is that the specificity of concrete actions could be improved by listing what specific configuration tasks are performed.
Suggestions
Add more specific concrete actions like 'Creates environment-specific config files, manages API key separation, sets up tenant isolation' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io multi-environment setup) and mentions some actions like 'setting up development, staging, and production environments' and 'managing multiple Apollo configurations', but doesn't list specific concrete actions like creating config files, setting environment variables, or managing API keys. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Apollo.io multi-environment setup) and 'when' (explicit 'Use when' clause with triggers for setting up dev/staging/prod environments, plus a 'Trigger with phrases' section listing specific keywords). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'apollo environments', 'apollo staging', 'apollo dev prod', 'apollo multi-tenant', 'apollo env config'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Apollo.io with multi-environment configuration. The trigger terms are distinct and unlikely to conflict with other skills, as they combine a specific tool (Apollo) with a specific task (environment setup). | 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, executable TypeScript code for Apollo multi-environment setup with good structure and concrete examples. However, it's verbose for a skill file — the three near-identical environment config blocks and full Zod schema consume significant tokens, and the workflow lacks explicit validation checkpoints between steps. The content would benefit from being split across bundle files with the SKILL.md serving as a concise overview.
Suggestions
Extract the full environment config objects and Zod schema into a referenced bundle file (e.g., `apollo-env-configs.ts`) and keep only a concise summary or single example in SKILL.md.
Add explicit validation checkpoints between steps, e.g., 'Verify the schema parses correctly before proceeding to Step 3' and 'Run verify-envs.ts after deploying secrets — do not proceed if any environment fails.'
Condense the three environment configs into a table or show one full example with a diff-style summary of how staging/production differ, rather than repeating the full object three times.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed with executable code, but includes some unnecessary verbosity — the full Zod schema with every field spelled out, three nearly identical environment config blocks, and the Kubernetes YAML could be more concise. The error handling table and resources section add bulk without proportional value for Claude. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with complete Zod schemas, a client factory with interceptors, Kubernetes manifests, and a verification script. All code is copy-paste ready with concrete values and patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (schema → configs → client → secrets → verification), but there are no explicit validation checkpoints between steps. The verification script exists as a final step but there's no feedback loop — no guidance on what to do if verification fails beyond reading the error message. | 2 / 3 |
Progressive Disclosure | The content is essentially monolithic — all code is inline in a single file with no references to supporting bundle files. The 'Next Steps' reference to 'apollo-observability' is good, but the lengthy code blocks (especially the three environment configs) could be split into referenced files. No bundle files exist to support progressive disclosure. | 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 | |
- 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.