instantly-multi-env-setup
Configure Instantly.ai across development, staging, and production environments. Use when setting up multi-workspace deployments, isolating test from production, or managing per-environment API keys and webhook endpoints. Trigger with phrases like "instantly environments", "instantly staging", "instantly dev prod", "instantly multi-env", "instantly workspace isolation".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-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 distinctiveness. It clearly identifies the product, the task domain (environment configuration), and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more concrete — listing actual actions like 'create workspace configurations', 'rotate API keys', or 'set up webhook routing' rather than higher-level use cases.
Suggestions
Replace or supplement the high-level 'Configure' verb with more concrete actions like 'create environment-specific workspace configs, rotate API keys per environment, configure webhook routing between stages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai environments) and some actions (setting up multi-workspace deployments, isolating test from production, managing API keys and webhook endpoints), but the primary verb 'Configure' is somewhat generic and the listed actions are more like use cases than concrete step-by-step capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Instantly.ai across dev/staging/prod environments) and 'when' (setting up multi-workspace deployments, isolating test from production, managing per-environment API keys). Includes explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger phrases like 'instantly environments', 'instantly staging', 'instantly dev prod', 'instantly multi-env', 'instantly workspace isolation' that cover common variations a user would naturally say. Also includes terms like 'API keys', 'webhook endpoints', and 'multi-workspace deployments'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Instantly.ai) combined with a specific concern (environment configuration/isolation). The trigger terms are product-specific and unlikely to conflict with other 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 is a solid, actionable skill with executable TypeScript code covering multi-environment Instantly.ai configuration. Its main strengths are concrete, copy-paste-ready code and good environment safety guards. Weaknesses include missing explicit validation checkpoints between workflow steps and a monolithic structure that could benefit from splitting detailed implementations into referenced files.
Suggestions
Add explicit validation checkpoints between steps — e.g., 'Run verifyWorkspaceIsolation() and confirm correct workspace BEFORE proceeding to campaign creation or webhook setup'
Split detailed code implementations (webhook setup, workspace verification, campaign creation) into separate bundle files and reference them from the main SKILL.md to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some unnecessary verbosity — the environment strategy table partially duplicates what the config code already shows, and some inline comments are redundant. The code blocks are substantial but mostly earn their place given the multi-environment complexity. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for configuration, campaign creation with guards, workspace verification, and webhook setup. The .env file examples are copy-paste ready with clear variable naming conventions. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (config → env files → campaign creation → workspace verification → webhooks), and the promotion workflow diagram is helpful. However, there are no explicit validation checkpoints between steps — e.g., no instruction to verify workspace isolation before proceeding to campaign creation, and no feedback loop for what to do if the workspace verification warning fires. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a reference to `instantly-observability` for next steps, but the skill is quite long (~200 lines of code) and could benefit from splitting detailed code (e.g., webhook setup, workspace verification) into separate 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
a04d1a2
- 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.