instantly-sdk-patterns
Apply production-ready Instantly.ai API client patterns for TypeScript and Python. Use when building reusable API wrappers, implementing retry logic, or establishing coding standards for Instantly integrations. Trigger with phrases like "instantly SDK patterns", "instantly best practices", "instantly client wrapper", "instantly code patterns", "idiomatic instantly".
77
73%
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-sdk-patterns/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 when to use the skill and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more concrete—listing particular patterns or actions beyond 'API wrappers' and 'retry logic' would strengthen it.
Suggestions
Add more specific concrete actions such as 'handle pagination, manage authentication, implement rate limiting, structure error responses' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Instantly.ai API client patterns) and mentions some actions like 'building reusable API wrappers' and 'implementing retry logic', but doesn't list multiple concrete specific actions (e.g., what endpoints, what specific patterns like pagination, error handling, authentication). | 2 / 3 |
Completeness | Clearly answers both 'what' (apply production-ready Instantly.ai API client patterns for TypeScript and Python) and 'when' (explicit 'Use when' clause with triggers, plus a 'Trigger with phrases' section listing specific activation terms). | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'instantly SDK patterns', 'instantly best practices', 'instantly client wrapper', 'instantly code patterns', 'idiomatic instantly'. Also mentions TypeScript and Python, retry logic, and coding standards, which are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Instantly.ai API client patterns specifically. The combination of 'Instantly.ai' + 'API client patterns' + specific trigger phrases makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with production-ready, executable code patterns for both TypeScript and Python. However, it suffers from being a monolithic document with ~300 lines of inline code that would benefit greatly from being split into referenced files. The workflow lacks validation checkpoints for verifying API connectivity or testing the client setup.
Suggestions
Extract the TypeScript interfaces (Step 2) and Python client into separate bundle files (e.g., types.ts.md, python-client.md) and reference them from the SKILL.md overview to improve progressive disclosure.
Add a validation step after client creation, such as a simple health check call (e.g., `client.getCampaigns({ limit: 1 })`) to verify the API key and connectivity before proceeding to more complex patterns.
Condense the SKILL.md to show one or two key patterns inline with brief usage examples, then link to detailed reference files for the full implementations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial executable code which is valuable, but the TypeScript interfaces section (Step 2) is very lengthy and could be split into a separate reference file. The overview and prerequisites are reasonably lean, but the overall token footprint is heavy for a SKILL.md that should serve as an overview. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready TypeScript and Python with complete class implementations, proper imports, and usage examples. The client, retry, pagination, and factory patterns are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically (client → types → retry → pagination → multi-tenant), but there are no validation checkpoints or verification steps. For a skill involving API integrations where errors are common, there's no guidance on testing the client works, verifying API key validity, or handling setup failures. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of code — over 250 lines of inline TypeScript interfaces and implementations that should be split into referenced files. The types definition alone (Step 2) is ~80 lines that belongs in a separate TYPES.md or reference file. No bundle files exist to offload this content, and the SKILL.md doesn't leverage any progressive disclosure structure. | 1 / 3 |
Total | 8 / 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.