CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-cost-tuning

Optimize Groq costs through model routing, token management, and usage monitoring. Use when analyzing Groq billing, reducing API costs, or implementing usage monitoring and budget alerts. Trigger with phrases like "groq cost", "groq billing", "reduce groq costs", "groq pricing", "groq expensive", "groq budget".

78

Quality

100%

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

100%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 body is a tight, well-structured overview: a pricing table, an ordered six-lever workflow with an inline routing skeleton, and clearly signaled one-level-deep references holding the full code. It is actionable, concise, and navigable without lecturing on basics.

DimensionReasoningScore

Conciseness

The body is lean — pricing is a compact table, levers are one-line bullets, and a small code skeleton replaces prose — and it avoids explaining concepts Claude already knows. Could not justify a 2 as there is no padded or unnecessary explanation.

3 / 3

Actionability

Provides an executable TypeScript routing skeleton plus concrete per-lever guidance (cap max_tokens, temperature:0 caching, batch 10-in-1), with complete copy-paste code clearly signaled in references/implementation.md.

3 / 3

Workflow Clarity

Six levers are explicitly ordered ('Apply these six levers in order. Each compounds on the last') with a usage-tracking feedback loop that catches spend regressions and an error-handling table for recovery; the destructive/batch cap does not apply because verification is present.

3 / 3

Progressive Disclosure

SKILL.md is an overview with two well-signaled, one-level-deep references (implementation.md, examples.md) — both real files listed in the Resources section — matching the top anchor for clear navigation.

3 / 3

Total

12

/

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 specific, complete, and well-triggered: it states concrete capabilities, gives explicit 'Use when' guidance, and lists natural Groq-prefixed trigger phrases. It uses appropriate third-person/imperative voice with no fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'model routing, token management, and usage monitoring' — matching the anchor that lists several specific actions rather than vague language.

3 / 3

Completeness

Clearly answers both what ('Optimize Groq costs through model routing...') and when via an explicit 'Use when...' clause plus trigger phrases, satisfying the top anchor.

3 / 3

Trigger Term Quality

Explicit trigger phrases ('groq cost', 'groq billing', 'reduce groq costs', 'groq pricing', 'groq expensive', 'groq budget') are natural terms a user would say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

All triggers are Groq-specific and the niche (Groq cost optimization) is distinct, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

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.