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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

The body is a lean, highly actionable diagnostic reference: executable code, concrete curl commands, and dense status tables with minimal padding. Its weaknesses are structural — batch/destructive fix workflows lack verification checkpoints, and the content is monolithic with a dangling reference to a non-existent bundle.

Suggestions

Add a validation/re-verify step to the destructive and batch fix workflows (e.g., after pausing and repairing accounts in fixUnhealthyAccounts, re-run /accounts/test/vitals and only resume when smtp_status and imap_status are 'ok').

Split the inline reference material into bundle files (e.g., references/status-codes.md, references/campaign-errors.md) and turn the 'Next Steps' pointer into a clearly-signaled link to a real instantly-debug-bundle file so progressive disclosure is one level deep and navigable.

Consolidate the overlapping 'HTTP Status Codes' and 'Error Handling' tables to remove the duplicated 401/403/422 rows and tighten token usage.

Dimension	Reasoning	Score
Conciseness	The body is dense reference material — tight one-sentence Overview, bullet prerequisites, status-code tables, and executable code — with no concept-padding Claude already knows. Not a 2: despite minor overlap between the HTTP Status Codes and Error Handling tables, the prose is lean and nearly every token earns its place as concrete reference.	3 / 3
Actionability	Provides fully executable TypeScript functions and concrete curl/jq one-liners with real endpoints (e.g., 'Regenerate key in Settings > Integrations', 'POST /webhooks/{id}/resume'), copy-paste ready. Not a 2: guidance is complete and executable rather than pseudocode or abstract.	3 / 3
Workflow Clarity	Diagnostic and fix routines are sequenced (numbered steps in fixUnhealthyAccounts, the backoff retry loop, the health-check script), but the destructive/batch account-pause and lead operations lack an explicit validate/re-verify checkpoint after the fix. The rubric caps batch/destructive workflows without validation at 2; not a 1 because clear sequences are present.	2 / 3
Progressive Disclosure	Sections are well-organized, but ~210 lines of status-code tables and code are all inline rather than split into reference files, and the only pointer ('see `instantly-debug-bundle`') is a vague backtick reference to a file that does not exist in any bundle directory. Not a 3 because there are no well-signaled one-level-deep references to real files; not a 1 because it is sectioned rather than a monolithic wall.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 description: it pairs concrete capabilities with an explicit use-when clause and a rich set of natural trigger phrases, all in third person. It clearly answers both what the skill does and when to invoke it, and is well-differentiated from generic debugging skills.

Dimension	Reasoning	Score
Specificity	States concrete actions ('Diagnose and fix Instantly.ai API v2 common errors and exceptions') and enumerates specific sub-domains (campaign/account/lead issues), matching the anchor that lists multiple specific concrete actions. Not a 2 because the actions are tied to concrete, named error categories rather than a vague domain.	3 / 3
Completeness	Explicitly answers both 'what' ('Diagnose and fix ... errors and exceptions') and 'when' ('Use when encountering Instantly errors, debugging failed requests, or troubleshooting campaign/account/lead issues') with an explicit 'Trigger with phrases like' clause, in third person. Not a 2 because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say: 'instantly error', 'instantly 401', 'instantly 429', 'instantly api failed', 'instantly debug', 'instantly troubleshoot'. Good coverage of natural terms, matching the anchor-3 example.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Instantly.ai API v2) with distinctive 'instantly ...' trigger phrases unlikely to fire for other skills. Not a 2 because the Instantly-specificity and branded triggers make overlap with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.