CtrlK
BlogDocsLog inGet started
Tessl Logo

instantly-cost-tuning

Optimize Instantly costs through tier selection, sampling, and usage monitoring. Use when analyzing Instantly billing, reducing API costs, or implementing usage monitoring and budget alerts. Trigger with phrases like "instantly cost", "instantly billing", "reduce instantly costs", "instantly pricing", "instantly expensive", "instantly budget".

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-cost-tuning
What are skills?

84

1.56x

Quality

77%

Does it follow best practices?

Impact

100%

1.56x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-cost-tuning/SKILL.md
SKILL.md
Review
Evals

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-crafted skill description with strong trigger term coverage and explicit usage guidance. The main weakness is that the specific capabilities could be more concrete - 'tier selection' and 'sampling' are mentioned but not fully explained. Overall, it effectively communicates when Claude should select this skill.

Suggestions

Expand the capabilities list with more specific actions like 'analyze tier pricing differences', 'calculate sampling ratios', or 'set up budget threshold alerts' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (Instantly costs) and some actions (tier selection, sampling, usage monitoring), but 'optimize' is somewhat vague and the specific concrete actions are not fully detailed.

2 / 3

Completeness

Clearly answers both what (optimize costs through tier selection, sampling, monitoring) and when (explicit 'Use when' clause with specific scenarios plus 'Trigger with phrases' providing additional guidance).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms including 'instantly cost', 'instantly billing', 'reduce instantly costs', 'instantly pricing', 'instantly expensive', 'instantly budget' - these are phrases users would naturally say.

3 / 3

Distinctiveness Conflict Risk

Very specific niche targeting 'Instantly' platform costs specifically, with distinct trigger terms that include the product name - unlikely to conflict with generic cost optimization or other API billing skills.

3 / 3

Total

11

/

12

Passed

Implementation

64%

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

This skill provides solid, actionable code examples for Instantly cost optimization with clear pricing information and multiple optimization strategies. However, it lacks validation checkpoints in the workflow (e.g., how to verify monitoring is working) and could be more concise by removing obvious prerequisites and redundant output sections. The structure is adequate but could benefit from better progressive disclosure.

Suggestions

Add validation steps to the Instructions workflow, such as 'Verify monitoring is capturing requests by checking logs after 24 hours'

Remove the Prerequisites section (access to billing dashboard and understanding usage patterns are obvious) and the Output section (restates the skill purpose)

Add explicit verification for budget alerts: 'Test alert by temporarily lowering threshold to current usage level'

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary sections like 'Prerequisites' listing obvious items and 'Output' section that restates what the skill does. The pricing table and code examples are appropriately concise.

2 / 3

Actionability

Provides fully executable TypeScript code for cost estimation, usage monitoring, sampling, and batching. SQL query for dashboard is copy-paste ready. All examples are concrete and implementable.

3 / 3

Workflow Clarity

Steps are listed in the Instructions section but lack validation checkpoints. No feedback loops for verifying that optimizations are working or that monitoring is correctly configured. The 'Cost Reduction Strategies' steps are clear but disconnected from verification.

2 / 3

Progressive Disclosure

Content is reasonably structured with clear sections, but the skill is somewhat monolithic with all code inline. The reference to 'instantly-reference-architecture' and caching 'from P16' suggests external resources exist but navigation is minimal. Could benefit from splitting detailed code into separate reference files.

2 / 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.

Validation9 / 11 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

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.