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

70

Quality

87%

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

80%Weight 40%Scale 1-5

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

Well-structured, lean content that leverages real reference files for full code. The main weakness is the absence of an explicit validation feedback loop in the apply-sequence for a batch/spending workflow.

Suggestions

Add an explicit verification checkpoint between the routing/minimize/batch steps and the tracking step (e.g., 'after routing, confirm token usage dropped via trackUsage before enabling caching') to create a validate->fix->retry loop.

Surface a concrete validation step for batch operations, such as checking parsed batchClassify output length matches input length before trusting results.

Include a brief rollback or rollback-detection note for the console spending-limit step so overspend is caught and reverted rather than only alerted.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence, leads with a lean routing skeleton, defers full code to references, and contains no padding or explanations of concepts Claude already knows.

5 / 5

Actionability

Inline routing skeleton is executable and the full, copy-pasteable implementations live in the real references files; minor gaps remain inline (only routing shown in the body), so it falls just short of fully copy-paste-ready in the overview.

4 / 5

Workflow Clarity

The six levers are sequenced ('apply in order; each compounds'), but this batch/spending workflow has no explicit validate->fix->retry checkpoint in the apply sequence, which caps the score per the batch-operation guidance.

3 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references (implementation.md, examples.md) that are real files, making navigation easy with no nested indirection.

5 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

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 that cleanly states what the skill does, when to use it, and supplies natural trigger phrases. Only the specificity of the listed actions keeps it from a perfect profile.

DimensionReasoningScore

Specificity

Names the domain and three concrete levers (model routing, token management, usage monitoring), but the actions are listed at a summary level rather than the comprehensive, fine-grained set required for a 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Optimize Groq costs through model routing, token management, and usage monitoring') and 'when' ('Use when analyzing Groq billing...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Six natural phrases a user would actually say ('groq cost', 'groq billing', 'reduce groq costs', 'groq pricing', 'groq expensive', 'groq budget') give comprehensive coverage with synonyms.

5 / 5

Distinctiveness Conflict Risk

A clearly Groq-specific niche with distinct Groq-branded triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

20

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.

Validation — 14 / 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/tons-of-skills-marketplace
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.