CtrlK
BlogDocsLog inGet started
Tessl Logo

custom-dimension-analysis

Use when analyzing costs by organization-specific dimensions like teams, products, business units, or applications for showback, chargeback, or business-aligned cost reporting

59

Quality

70%

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/custom-dimension-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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-sequenced, actionable analysis workflow with concrete tool calls and a useful math-in-code guardrail, undermined by significant verbosity from placeholder output templates and redundant advisory sections. Splitting the output-format and patterns material into reference files would materially improve both conciseness and progressive disclosure.

Suggestions

Move the large Output Format placeholder-table templates and the Common Custom Dimension Patterns / Advanced Techniques sections into separate reference files, leaving SKILL.md as a concise overview that links to them.

Consolidate the overlapping advisory lists ('Skill-Specific Best Practices', 'Tips for Effective Analysis') into a single short list, cutting generic guidance Claude already knows.

Add a brief data-validation checkpoint (e.g. confirming dimension values and totals are non-empty/sane before computing derived metrics) to strengthen workflow clarity even for read-only analysis.

DimensionReasoningScore

Conciseness

The ~570-line body is noticeably verbose: an extensive Output Format section filled with placeholder tables ($X,XXX / XX%) plus redundant advisory lists ('Tips for Effective Analysis', 'Skill-Specific Best Practices', 'Common Custom Dimension Patterns', 'Advanced Techniques') that could be trimmed without losing clarity.

2 / 5

Actionability

Most steps give concrete tool invocations (e.g. get_cost_data(group_by=[...], cost_type=..., limit=...)) and Step 8 plus the optimization-scoring block provide real executable Python, with only minor descriptive gaps in a few steps.

4 / 5

Workflow Clarity

A clear 9-step sequence with an enforced 'All Math In Code' guardrail; because the operations are read-only cost queries rather than destructive/batch mutations, the absence of explicit validate->fix->retry loops is a minor gap rather than a cap.

4 / 5

Progressive Disclosure

References are listed in a See Also section and inline, but the bulk of the content (output templates, patterns, advanced techniques) is inlined in one long SKILL.md rather than split into separate reference files, fitting the 'could be better organized; content that should be separate is inline' anchor.

3 / 5

Total

13

/

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, trigger-rich description that clearly answers both what and when with concrete business-aligned keywords. Minor gaps in action variety and explicit platform naming keep specificity and distinctiveness just below maximum.

DimensionReasoningScore

Specificity

Names the domain and enumerates concrete dimension objects ('teams, products, business units, or applications') plus purposes ('showback, chargeback, or business-aligned cost reporting'), but the core action is a single verb ('analyzing') rather than multiple distinct actions, so it falls short of anchor 5.

4 / 5

Completeness

Explicitly combines what ('analyzing costs by organization-specific dimensions') and when ('Use when analyzing costs by... for showback, chargeback, or business-aligned cost reporting') with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes natural user phrases ('teams, products, business units, applications', 'showback, chargeback') plus a 'by [custom dimension name]' trigger, giving good keyword coverage; not quite anchor 5 because it lacks a few common synonyms/variations users might say.

4 / 5

Distinctiveness Conflict Risk

The 'organization-specific dimensions' / showback-chargeback niche is mostly distinct, but the description does not name CloudZero or User:Defined dimensions, leaving minor overlap risk with general cost-analysis skills.

4 / 5

Total

17

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (572 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

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.