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 trigger terms and clear 'when' guidance. Its main weakness is that the 'what' portion is somewhat high-level—it says 'configure' and 'manage' without detailing the specific actions involved (e.g., creating config files, setting up environment-specific API endpoints, managing credentials). Adding more concrete actions would elevate the specificity.
Suggestions
Add specific concrete actions like 'Creates environment-specific Apollo config files, manages API key separation across environments, configures client instances per environment' 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 configuring API keys. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Apollo.io multi-environment setup) and 'when' (explicit 'Use when' clause with scenarios plus explicit 'Trigger with phrases' section). Both components are present and well-defined. | 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 all Apollo-specific and environment-focused, making it unlikely to conflict with general environment setup skills or other Apollo skills focused on different aspects. | 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 code for Apollo multi-environment setup with good structure and error handling documentation. However, it is verbose for a skill file — the extensive inline code blocks could be better organized through progressive disclosure, and the workflow lacks explicit validation checkpoints between steps despite involving environment configuration that could fail silently.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Run the verification script after Step 2 to confirm all API keys are valid before building the client factory.'
Move the detailed code implementations into separate referenced files (e.g., config-schema.ts, client-factory.ts) and keep SKILL.md as a concise overview with key patterns and navigation links.
Trim explanatory comments in code that Claude can infer (e.g., '// Feature gate: block disabled endpoints', '// Debug logging in dev') to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive code blocks. Some of the code is reasonable for a config setup guide, but the level of detail (e.g., full Zod schemas, interceptor logic, K8s manifests) is verbose for what Claude could infer. The error handling table and resources section add useful but somewhat redundant information. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with complete Zod schemas, client factory implementation, 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), and Step 5 provides a verification script. However, there are no explicit validation checkpoints between steps — e.g., no instruction to validate the schema works before proceeding to the client factory, and no feedback loop for fixing issues during setup. | 2 / 3 |
Progressive Disclosure | The content is mostly monolithic — all code is inline in a single file rather than being split into referenced files. The 'Next Steps' reference to apollo-observability is good, but the bulk of the content (200+ lines of code) could benefit from being split into separate reference files with a concise overview in the main skill. | 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
3e83543
- 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.