instantly-common-errors
Diagnose and fix Instantly common errors and exceptions. Use when encountering Instantly errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "instantly error", "fix instantly", "instantly not working", "debug instantly".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-common-errors81
Quality
73%
Does it follow best practices?
Impact
100%
1.44xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-common-errors/SKILL.mdDiscovery
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/what guidance. The main weakness is the lack of specific concrete actions - it describes general categories (errors, exceptions, integration issues) rather than listing specific capabilities like 'fix authentication errors, resolve rate limiting, debug webhook failures'.
Suggestions
Add 2-3 specific concrete actions to improve specificity, e.g., 'fix authentication errors, resolve rate limiting issues, debug webhook failures, troubleshoot API connection problems'
Consider adding specific error types or common Instantly issues that users might mention, such as 'campaign errors', 'email delivery issues', or 'API response codes'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly) and general actions ('diagnose and fix', 'debugging failed requests', 'troubleshooting integration issues'), but lacks specific concrete actions like what types of errors, what fixes are applied, or what integration issues are covered. | 2 / 3 |
Completeness | Clearly answers both what ('Diagnose and fix Instantly common errors and exceptions') and when ('Use when encountering Instantly errors, debugging failed requests, or troubleshooting integration issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases users would say: 'instantly error', 'fix instantly', 'instantly not working', 'debug instantly'. Good coverage of common variations and natural language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | The skill is clearly scoped to 'Instantly' (a specific platform/tool), with distinct triggers that include the product name. Unlikely to conflict with generic debugging or error-handling 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.
This skill provides a reasonable troubleshooting framework but underdelivers on its promise of 'top 10 errors' by only documenting 3. The scaffolding sections (Overview, Prerequisites, generic Instructions) consume tokens without adding value. The actual error solutions are actionable but incomplete, with Rate Limit deferring entirely to another skill.
Suggestions
Remove the generic Instructions steps 1-3 and Output section - they describe obvious troubleshooting steps Claude already knows
Add the remaining 7 errors promised in the overview, or change the description to match actual content
Add verification commands after each solution to confirm the fix worked (e.g., 'Test with: curl -H "Authorization: Bearer $INSTANTLY_API_KEY" https://api.instantly.com/v1/me')
Include the actual exponential backoff code inline rather than deferring to another skill for the Rate Limit solution
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary scaffolding (Overview, Prerequisites, Instructions steps 1-3, Output section) that adds little value. The actual error solutions are reasonably concise, but the wrapper content could be trimmed. | 2 / 3 |
Actionability | Provides some concrete commands (curl checks, env verification, timeout config), but only covers 3 errors despite claiming 'top 10'. Solutions are incomplete - Rate Limit just defers to another skill, and many common errors are missing. | 2 / 3 |
Workflow Clarity | The 3-step diagnostic process is clear but generic. Escalation path is good. However, there's no validation checkpoint to confirm fixes worked, and the 'Verified resolution' output claim has no corresponding verification steps. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections. References to other skills (instantly-rate-limits, instantly-debug-bundle) and external resources are one level deep and well-signaled. Content is appropriately organized for a troubleshooting reference. | 3 / 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 | |
- 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.