instantly-cost-tuning

Optimize Instantly.ai costs through plan selection, account management, and usage monitoring. Use when analyzing Instantly billing, reducing per-campaign costs, or choosing between Instantly pricing tiers. Trigger with phrases like "instantly cost", "instantly pricing", "instantly billing", "reduce instantly cost", "instantly plan comparison".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with concrete API code and a clear four-step sequence, but it is verbose and monolithic — inline code that should live in scripts/ and missing validation checkpoints around destructive batch actions hold it back.

Suggestions

Move the four TypeScript functions into scripts/ files and reference them one level deep, keeping SKILL.md as a concise overview with the pricing table, checklist, and per-step entry points.

Add explicit validation checkpoints before destructive/batch actions in Step 4 (e.g., confirm account list, dry-run removal, re-check utilization after pausing) so the workflow has a validate-then-act feedback loop.

Tighten the body by removing repeated account-fetching across steps and trimming console.log scaffolding so each step shows only the essential logic.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient and free of concepts Claude already knows, but the ~230-line body repeats account-fetching across steps and embeds four long code blocks inline that could be tightened or factored out.	2 / 3
Actionability	Provides fully concrete TypeScript hitting real Instantly v2 endpoints with specific thresholds (utilization <20%, bounce >5%) and copy-paste-ready logic, satisfying the executable-code anchor.	3 / 3
Workflow Clarity	The four steps are clearly sequenced and a checklist exists, but batch/destructive suggestions (removing inactive accounts, archiving campaigns) lack explicit validation checkpoints before acting, capping clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but the body is a monolithic ~230-line file with heavy inline code that belongs in bundle scripts; no references/scripts/assets files exist to split the detail one level deep.	2 / 3
	Total	9 / 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.

The description is strong: it states concrete capabilities, includes explicit 'Use when' triggers with natural user phrases, and is tightly scoped to Instantly.ai cost optimization. Minor formatting noise (blank lines splitting sentences) does not affect the scored dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'plan selection, account management, and usage monitoring' — matching the anchor for several specific concrete actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Optimize Instantly.ai costs through plan selection, account management, and usage monitoring') and when ('Use when analyzing Instantly billing...') with explicit triggers, satisfying the top anchor.	3 / 3
Trigger Term Quality	Provides natural phrases a user would actually say — 'instantly cost', 'instantly pricing', 'instantly billing', 'reduce instantly cost', 'instantly plan comparison' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Instantly.ai with branded trigger phrases, occupying a clear niche unlikely to fire for unrelated skills.	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: 4 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.