CtrlK
BlogDocsLog inGet started
Tessl Logo

cost-spike-investigation

Use when a cost spike or unexpected increase has already been identified and you need to find which service, account, or resource is responsible

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/cost-spike-investigation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, mostly executable investigation skill that defers detail cleanly to one-level references. The main weakness is the absence of explicit validation/feedback checkpoints in the workflow, which is notable for a multi-query comparison investigation.

Suggestions

Add explicit validation checkpoints between steps, e.g. after Step 2 confirm both periods returned data before drilling down, and a 're-query with wider range if results are empty' feedback loop.

Replace placeholder values (date_range="<spike_period>") with a brief note on how to construct them from Step 1, so the examples are fully executable without inference.

Trim 'Common Spike Patterns' and 'Best Practices' to the non-obvious items, since much is inferable from the queries already shown.

DimensionReasoningScore

Conciseness

The body is mostly efficient with numbered steps and compact code blocks, though sections like 'Common Spike Patterns' and 'Best Practices' add some explanatory padding that Claude could largely infer.

4 / 5

Actionability

Provides concrete, copy-pasteable get_cost_data / get_dimension_values examples across every step, but several blocks use placeholder date_range/group_by values rather than fully parameterized executable calls, leaving minor gaps.

4 / 5

Workflow Clarity

The seven steps are clearly sequenced, but for a batch/comparison investigation there are no explicit validation checkpoints or feedback loops (e.g. verify data returned, re-query on empty results), which caps this dimension at 3.

3 / 5

Progressive Disclosure

The body is a well-organized overview that defers detail to clearly signaled one-level-deep references (best-practices.md, cloudzero-tools-reference.md, error-handling.md, dimensions-reference.md, cost-types-reference.md), with no nested references and easy navigation.

5 / 5

Total

16

/

20

Passed

Description

81%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 with an explicit 'Use when' trigger and good keyword coverage targeting a distinct niche. Specificity is the only weak spot, since it states one action rather than enumerating the comparative and dimensional analysis the skill performs.

Suggestions

Expand the action clause to name the core methods, e.g. 'compare recent spending to historical baselines and drill down by service, account, and resource'.

Add a couple of natural synonyms users say (e.g. 'bill jumped', 'spending anomaly') to broaden trigger matching.

DimensionReasoningScore

Specificity

Names the domain (cost spike investigation) and one concrete action ("find which service, account, or resource is responsible") but does not enumerate the comparative/baseline analysis actions the body actually performs.

3 / 5

Completeness

Explicitly answers "what" (find which service/account/resource is responsible) and "when" with a clear "Use when..." clause naming an already-identified cost spike or unexpected increase.

5 / 5

Trigger Term Quality

Includes natural terms users would say ("cost spike", "unexpected increase") plus strong synonyms ("spike", "increase") and the implicit context of services/accounts/resources, covering common variations.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (post-identification cost spike root-causing) with distinct triggers tied to an already-identified spike, minimizing overlap with general cost-analysis skills.

5 / 5

Total

18

/

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.