CtrlK
BlogDocsLog inGet started
Tessl Logo

top-cost-drivers

Use when identifying where cloud spend is concentrated — which services, accounts, teams, or regions are driving the most cost — to prioritize optimization efforts

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/cost-analyst/skills/top-cost-drivers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A highly actionable skill with excellent concrete code examples and a clear step sequence, weakened by redundant sections and the absence of validation checkpoints in a batch workflow. It also references bundle files that are not present.

Suggestions

Add explicit validation/verification checkpoints to the workflow — e.g., after each query confirm results are non-empty and reconcile the sum against the period total before computing contribution percentages.

Consolidate the overlapping "Common Analysis Patterns," "Tips for Effective Analysis," and "Best Practices" sections to remove redundancy and reduce token cost.

Either create the referenced references/*.md files (best-practices, dimensions-reference, etc.) and move the inlined FQDID/query detail there, or remove the dangling references to keep navigation intact.

DimensionReasoningScore

Conciseness

Mostly efficient with code-driven steps, but "Common Analysis Patterns" restates "How This Skill Works" and "Tips for Effective Analysis" overlaps "Best Practices," adding redundant sections that could be trimmed.

3 / 5

Actionability

Provides numerous copy-paste-ready get_cost_data() calls with concrete group_by, cost_type, and limit parameters covering services, accounts, providers, regions, custom dimensions, and tags across the common cases.

5 / 5

Workflow Clarity

The 7-step sequence is clear, but this batch-query workflow lacks explicit validation or verification checkpoints (e.g., confirming non-empty results, reconciling totals), which caps batch-operation workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized sections with clearly signaled, one-level-deep references in "See Also," but the five referenced references/*.md files do not exist as bundle files and substantial reference-style material (FQDIDs, all query patterns) is inlined rather than externalized.

4 / 5

Total

15

/

20

Passed

Description

83%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, well-structured description that clearly states both capability and trigger conditions with concrete dimensions. It would benefit from incorporating more of the natural user phrasings ("biggest costs," "most expensive") it lists later in the body.

DimensionReasoningScore

Specificity

Names the domain and concrete analytical dimensions ("services, accounts, teams, or regions") plus the action of prioritizing optimization, listing several specifics though the verbs remain somewhat abstract.

4 / 5

Completeness

Explicitly answers both what (identifying where cloud spend is concentrated across named dimensions) and when ("Use when identifying... to prioritize optimization efforts") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural trigger coverage with "Use when" plus "where cloud spend is concentrated" and "driving the most cost," but missing common synonyms like "biggest costs," "top spending," or "most expensive" that the body itself uses.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche around cloud cost concentration with distinct triggers, though the broader cloud-spend analytics domain carries minor overlap risk with related optimization skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Cloudzero/cloudzero-claude-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.