clay-cost-tuning

Optimize Clay credit spending with provider key management, waterfall tuning, and budget controls. Use when analyzing Clay costs, reducing credit consumption, or implementing spending alerts and caps. Trigger with phrases like "clay cost", "clay billing", "reduce clay costs", "clay pricing", "clay expensive", "clay budget", "clay credits".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

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

The content is highly actionable with executable code, clear sequencing, and useful decision checkpoints for batch operations. Its main weaknesses are inline time-sensitive date references and a monolithic structure with no reference files for the detailed implementations.

Suggestions

Move the 'March 2026' pricing changes into a dedicated 'Pricing changes' or 'Deprecated patterns' section so time-sensitive facts do not penalize conciseness.

Extract the longer TypeScript implementations (cost-filter, budget-monitor, sampler) into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Tighten prose around the code blocks — e.g. drop restating that using own keys is 'the single most impactful cost reduction' since the savings table already shows it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code is actionable, but inline time-sensitive statements ('March 2026 pricing split', 'March 2026 change: Failed lookups no longer cost Data Credits') are not isolated in a deprecated/old-patterns section, which the rubric penalizes, and the lengthy inline TypeScript could be trimmed.	2 / 3
Actionability	Provides complete, executable TypeScript functions (cost filter, sampler, budget monitor, cost calculator), a concrete provider cost table, and specific setup navigation, all copy-paste ready.	3 / 3
Workflow Clarity	Six steps are clearly sequenced with explicit checkpoints: the sampling step's hit-rate decision gate (>60% proceed, <40% clean first), budget caps with STOP alerts, and an error-handling table form validation/feedback loops for batch enrichment.	3 / 3
Progressive Disclosure	Sections are well-organized, but at ~200 lines all detailed code is inline with no bundle files to split into; the only cross-reference ('see clay-reference-architecture') points to another skill, not a one-level-deep reference file, so content that could be separate stays monolithic.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 third-person, concise, and well-structured, clearly stating capabilities, use conditions, and trigger phrases without padding. It is a strong example of a complete, distinctive skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'provider key management, waterfall tuning, and budget controls' — matching the anchor for naming several specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Optimize Clay credit spending with...') and when ('Use when analyzing Clay costs, reducing credit consumption...') with explicit trigger guidance, exceeding the 2-cap for missing triggers.	3 / 3
Trigger Term Quality	Provides broad natural-phrase coverage a user would actually say: 'clay cost', 'clay billing', 'reduce clay costs', 'clay pricing', 'clay expensive', 'clay budget', 'clay credits'.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Clay-cost niche with Clay-specific trigger phrases, making it 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
Path: plugins/saas-packs/clay-pack/skills/clay-cost-tuning/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.