instantly-local-dev-loop
Configure Instantly.ai local development with mock server and test workflows. Use when setting up a dev environment, testing API calls without sending emails, or building integration tests against Instantly endpoints. Trigger with phrases like "instantly dev setup", "test instantly locally", "instantly mock server", "instantly development environment".
80
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-local-dev-loop/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 that clearly identifies its niche (Instantly.ai local development), explains when to use it, and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more granular—listing concrete actions like configuring mock endpoints, stubbing email sends, or setting up test fixtures would strengthen the specificity dimension.
Suggestions
Add more concrete specific actions beyond 'configure' and 'test workflows', e.g., 'stub API responses, configure mock SMTP, generate test fixtures, validate webhook payloads'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai local development) and some actions (configure, mock server, test workflows), but doesn't list multiple concrete specific actions like 'start mock SMTP server, stub API responses, run integration test suites'. The actions remain somewhat high-level. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure local dev with mock server and test workflows) and 'when' (setting up dev environment, testing API calls without sending emails, building integration tests) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'instantly dev setup', 'test instantly locally', 'instantly mock server', 'instantly development environment', plus terms like 'dev environment', 'testing API calls', 'integration tests', and 'Instantly endpoints'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Instantly.ai local development and mock server setup. The combination of 'Instantly.ai' + 'local development' + 'mock server' creates a clear niche that is 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 fully executable code examples covering the complete local dev loop for Instantly.ai. Its main weaknesses are the lack of explicit validation checkpoints between steps (e.g., verifying mock server connectivity, confirming webhook registration) and the monolithic structure that could benefit from splitting detailed code into separate referenced files. The content is slightly verbose in places but generally well-organized.
Suggestions
Add explicit validation checkpoints between steps — e.g., 'Verify mock server is reachable: curl https://developer.instantly.ai/_mock/api/v2/campaigns' before running tests, and verify webhook registration response before testing delivery.
Consider extracting the full API client and test suite code into bundle files (e.g., src/instantly.ts, tests/instantly.test.ts) and referencing them from SKILL.md to improve progressive disclosure and reduce inline length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary elements like the full project structure recap (which is evident from the code), and the error handling table contains somewhat obvious troubleshooting. The prerequisites and overview sections are lean, but the overall length (~180 lines) could be tightened given that Claude can infer patterns from fewer examples. | 2 / 3 |
Actionability | Every step provides fully executable, copy-paste-ready TypeScript and bash code. The config, API client, test suite, webhook server, and webhook registration are all concrete and complete with specific URLs, commands, and code patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-5) and logically ordered from config through testing to webhooks. However, there are no explicit validation checkpoints — for example, no step to verify the mock server is reachable before running tests, no verification that the webhook was successfully registered before testing it, and no feedback loop for handling test failures. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a reference to `instantly-sdk-patterns` for next steps. However, with no bundle files, all content is inline in a single file. The lengthy code blocks for the API client and tests could benefit from being split into referenced files, and the Resources section provides external links but no internal file references for deeper content. | 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.