cost-trend-analysis

Use when analyzing whether costs are growing, declining, or stable over time — for forecasting, budget planning, or understanding spending velocity

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/cost-analyst/skills/cost-trend-analysis/SKILL.md

Quality

Content

67%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, actionable analysis workflow with concrete code and API examples and a clear step sequence. Its main weakness is redundancy — pattern types and best-practice guidance are repeated across sections — and a long inlined output template that could live in a reference file.

Suggestions

Consolidate the pattern-type material: "Step 5: Identify Pattern Types" and "Common Trend Patterns and Causes" cover the same patterns (exponential, linear, step, declining) — merge them into one section to remove duplication.

Merge "Skill-Specific Best Practices" and "Tips for Effective Analysis", which overlap heavily (granularity, decomposition, drivers, actionability), into a single concise best-practices list.

Move the long templated "Output Format" section into a separate reference file (e.g. references/output-format.md) and keep only a brief pointer in SKILL.md to reduce inlined bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly useful and avoids explaining basic concepts, but it duplicates material across sections — pattern types appear both in "Step 5: Identify Pattern Types" and again in "Common Trend Patterns and Causes", and guidance overlaps between "Skill-Specific Best Practices" and "Tips for Effective Analysis" — so it could be tightened.	3 / 5
Actionability	It provides concrete, executable guidance: a runnable Python script for growth metrics, specific get_cost_data calls with real parameters and dimension names, and a firm "all math in code" rule with security constraints; minor gaps remain where forecasts and the output format are prose/placeholder templates rather than executable code.	4 / 5
Workflow Clarity	The process is laid out as a clear, ordered Step 1 through Step 8 sequence with well-defined inputs per step; because this is read-only analysis rather than destructive/batch work the missing-data validation cap does not apply, though no explicit data-quality validation checkpoints are present, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	Structure is good with clear sections and a "See Also" list of one-level-deep references (best-practices, tools, error-handling, dimensions, cost-types), but no bundle files are actually provided and the referenced paths point outside this bundle, while a fair amount of reference-like material (output templates, pattern catalog) is inlined, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

75%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 concise, third-person description that clearly answers both what the skill does and when to use it, with concrete actions and natural trigger phrases. It is strong across all dimensions but stops just short of comprehensive on specificity and completeness.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "analyzing whether costs are growing, declining, or stable over time", "forecasting", "budget planning", "understanding spending velocity" — giving good coverage with only minor gaps, matching the anchor for several specific actions.	4 / 5
Completeness	It has both a "what" (analyzing cost direction over time) and an explicit "Use when..." trigger clause covering forecasting, budget planning, and spending velocity; the "what" is somewhat embedded in the "when" clause rather than stated as a comprehensive standalone list, so it falls just short of the top anchor.	4 / 5
Trigger Term Quality	Natural phrases a user would say are present ("costs are growing, declining, or stable", "forecasting", "budget planning", "spending velocity"), providing good keyword coverage, though a few common variations like "trend" as a bare trigger are folded in rather than surfaced.	4 / 5
Distinctiveness Conflict Risk	The niche (cost trend / spending velocity analysis) is fairly distinct with specific triggers, though it could overlap with closely related CloudZero cost-analysis skills such as anomaly detection or general cost analysis, so minor overlap risk remains.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Cloudzero/cloudzero-claude-marketplace
Path: plugins/cost-analyst/skills/cost-trend-analysis/SKILL.md
Commit: 62c27f3

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.