CtrlK
BlogDocsLog inGet started
Tessl Logo

instantly-common-errors

Diagnose and fix Instantly.ai API v2 common errors and exceptions. Use when encountering Instantly errors, debugging failed requests, or troubleshooting campaign/account/lead issues. Trigger with phrases like "instantly error", "instantly 401", "instantly 429", "instantly api failed", "instantly debug", "instantly troubleshoot".

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable diagnostic reference built from runnable code and compact tables. Its main weakness is workflow_clarity: state-changing/batch fixes (pausing accounts) lack explicit validate-and-verify feedback loops.

Suggestions

Add a verify step after fixUnhealthyAccounts (e.g., re-run /accounts/test/vitals and confirm smtp_status/imap_status are 'ok') to close the validate→fix→retry loop on batch account operations.

Fold the overlapping 401/403/422 rows from the "Error Handling" table into the "HTTP Status Codes" table (or cross-reference) to remove the mild redundancy.

Consider extracting the status-code reference tables into a references/ file to reduce SKILL.md length and improve progressive_disclosure, keeping the diagnostic code inline.

DimensionReasoningScore

Conciseness

The body is predominantly compact reference tables and executable code with almost no concept padding, but the "Error Handling" table partially overlaps the "HTTP Status Codes" table (401/403/422), a minor instance of content that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready TypeScript (diagnoseCampaign, fixUnhealthyAccounts, withBackoff) and a runnable bash diagnostic script with real curl/jq commands covering the common cases.

5 / 5

Workflow Clarity

Fix steps are numbered (1. Get accounts, 2. Test vitals, 3. Identify and fix) but lack explicit validate-after-fix checkpoints; pausing accounts is a state-changing batch operation without a verify step, capping this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

Single SKILL.md body (~210 lines) is well-organized with clear section headers (HTTP Status Codes, Campaign Errors, Lead Errors, Webhook Errors) and a clearly signaled Next Steps pointer to instantly-debug-bundle; no nested references, though bulk reference tables remain inline rather than split into bundle files.

4 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that explicitly states capabilities, use conditions, and natural trigger phrases for a clearly delineated niche. Minor specificity gap is the only thing keeping it from a perfect score across all dimensions.

DimensionReasoningScore

Specificity

"Diagnose and fix Instantly.ai API v2 common errors and exceptions" names a specific domain plus two concrete actions, with coverage broadened by "campaign/account/lead issues" — several specific actions with minor gaps rather than the comprehensive multi-action list of a 5.

4 / 5

Completeness

Clearly answers both what ("Diagnose and fix Instantly.ai API v2 common errors and exceptions") and when ("Use when encountering Instantly errors, debugging failed requests..."), supplemented by concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit trigger phrases — "instantly error", "instantly 401", "instantly 429", "instantly api failed", "instantly debug", "instantly troubleshoot" — cover natural user phrasings including error codes and synonyms (debug/troubleshoot).

5 / 5

Distinctiveness Conflict Risk

Scoped to the Instantly.ai API v2 niche with code-specific triggers ("instantly 401", "instantly 429"), making collision with unrelated skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.