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
Pending
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 that clearly identifies its niche (Instantly.ai API client patterns) and provides explicit trigger guidance. The 'when' clause and trigger phrases are strong, making it easy for Claude to select this skill appropriately. The main weakness is that the specific capabilities listed (API wrappers, retry logic, coding standards) are somewhat generic software engineering concepts rather than Instantly-specific actions.
Suggestions
Add more Instantly-specific capabilities such as 'campaign management endpoints', 'lead list operations', or 'email warmup configuration' to increase specificity beyond generic API patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly.ai API client patterns) and some actions (building reusable API wrappers, implementing retry logic, establishing coding standards), but the actions are somewhat generic software engineering concepts rather than highly specific capabilities unique to this skill. | 2 / 3 |
Completeness | Clearly answers both 'what' (apply production-ready Instantly.ai API client patterns for TypeScript and Python) and 'when' (building reusable API wrappers, implementing retry logic, establishing coding standards) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes a good range of natural trigger terms: 'instantly SDK patterns', 'instantly best practices', 'instantly client wrapper', 'instantly code patterns', 'idiomatic instantly', plus mentions TypeScript and Python. These are terms a user would naturally say when seeking this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific focus on Instantly.ai API patterns. The combination of 'Instantly' branding with API client patterns creates a clear niche that is unlikely to conflict with generic API or coding 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 provides high-quality, executable code patterns for Instantly API integration with good coverage of common needs (retry, pagination, multi-tenant). However, it suffers from being a monolithic document where extensive type definitions and two language implementations are all inlined, making it token-inefficient. It also lacks validation checkpoints in its workflow steps.
Suggestions
Move TypeScript interfaces (Step 2) to a separate TYPES.md or types reference file and link to it from the main skill
Move the Python client to a separate PYTHON.md reference file, keeping the main skill focused on one language with cross-references
Add validation checkpoints such as 'verify your client connects: await client.getCampaigns({ limit: 1 })' after Step 1
Add a quick-start section at the top showing minimal usage in 5-10 lines before diving into the full implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) with extensive type definitions that could be split into a separate reference file. The TypeScript interfaces section in particular is verbose and could be linked rather than inlined. However, the code itself is lean without unnecessary prose explanations. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready TypeScript and Python with proper imports, class definitions, and usage examples. The client, retry, pagination, and factory patterns are all concrete and complete. | 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 pattern that involves API calls and retry logic, 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. The ~80 lines of TypeScript interfaces should be in a separate types reference file. The Python client could also be a separate file reference. Everything is inlined in one massive SKILL.md with no clear separation between overview and detailed reference material. | 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
c8a915c
- 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.