CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloud-finops

Use for any cloud cost question on AWS, Azure or Google Cloud - a bill that jumped or one service that spiked (NAT gateway, egress, storage), cost anomaly alert thresholds, untagged or unallocated spend and tag cleanup for showback or chargeback, Savings Plans, Reserved Instances or committed use discounts (utilization, coverage, unused commitment, effective savings rate, whether to buy more), or whether cost per order or per customer got worse. Reads a FOCUS billing export with stdlib scripts.

Quality

91%

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

The canonical home for this skill is cloud-finops in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplarily structured body: executable, flag-accurate commands for every step, typed exit codes as validation signals, hard policy rules that prevent common analytical mistakes, and a clean one-level-deep bundle layout that was verified against the actual files. The only deductions are a time-sensitive verification date in the overview and the absence of an explicit recovery loop for bad-input exits.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explaining what cloud billing or CSVs are, and each section carries real information (commands, exit codes, policy defaults). Two minor trims exist: the time-sensitive stamp "Definitions verified 2026-11-17 against FOCUS v1.4" (a specific date outside any deprecated/old-patterns section, which the guidelines penalize) and the slightly rhetorical opening paragraph ("A cloud bill answers 'how much'; it rarely answers..."). This matches anchor 4 — efficient with minor instances that could be trimmed — rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

All three workflow commands are copy-paste ready with real flags ("python scripts/allocation_check.py --input focus.csv --required-tags team,env,cost-center", "--eligible Compute", "--units orders.csv"), and every flag cited in the body — including --target, --min-coverage, -k, --min-abs, --sample, --output json — was verified to exist in the bundled scripts. The common cases (which script answers which question) are explicitly covered, matching anchor 5.

5 / 5

Workflow Clarity

The sequence is explicit and well-motivated (numbered steps 0–3, each paired with the question it answers, per-step expected outputs, provider-specific export instructions) and validation checkpoints are documented via typed exit codes ("0 at target · 2 findings · 3 bad input") and refusal rules ("Under 14 days it refuses"). It sits at anchor 4 rather than 5 only because no explicit error-recovery loop is stated for exit 3 (e.g., fix the export and re-run) — a minor validation gap.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview (~65 lines) with a one-line role per script, and every referenced path (three references/*.md, two assets/*, four scripts) exists and is described in a single annotated list. The reference files themselves contain no nested references, so all disclosure is exactly one level deep with clear navigation — matching anchor 5.

5 / 5

Total

18

/

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 dense, well-constructed description with explicit use-when triggers, comprehensive natural trigger terms across all three providers, and a clearly bounded FinOps-billing niche. Its only weakness is that capabilities are framed as user questions with a single explicit action verb, leaving the skill's actions slightly implied.

DimensionReasoningScore

Specificity

Names one explicit action ("Reads a FOCUS billing export with stdlib scripts") and enumerates many concrete capability areas ("utilization, coverage, unused commitment, effective savings rate", "untagged or unallocated spend and tag cleanup", "cost per order or per customer"), but the bulk of the enumeration frames user questions rather than listing action verbs, leaving the actual actions partly implied — matching anchor 4 (several specific items, minor framing gap) rather than anchor 5's fully action-verb coverage.

4 / 5

Completeness

Explicitly answers both: "Use for any cloud cost question on AWS, Azure or Google Cloud..." gives concrete when-triggers, and "Reads a FOCUS billing export with stdlib scripts" plus the enumerated analyses (allocation/tag hygiene, commitment metrics, anomaly and unit-cost questions) state the what. Not the level below (4) because the when-clause is explicit and richly specific rather than merely adequate.

5 / 5

Trigger Term Quality

Comprehensive natural phrasing a user would actually say: "a bill that jumped", "one service that spiked (NAT gateway, egress, storage)", "Savings Plans, Reserved Instances or committed use discounts", "cost per order or per customer", plus provider names AWS, Azure, Google Cloud. Cross-provider synonyms and product-specific terms are all present, matching the anchor-5 standard of comprehensive synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche — analyzing cloud billing data via FOCUS exports — with distinct triggers (NAT gateway spend, commitment utilization, ESR, showback/chargeback) that no adjacent skill (LLM token spend, SaaS procurement, architecture design) would naturally claim. Minimal conflict risk; only a faint brush with general finance via unit-cost questions, which is not enough to drop below anchor 5.

5 / 5

Total

19

/

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.

Validation — 15 / 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

alirezarezvani/claude-skills

Path

engineering/skills/cloud-finops/SKILL.md

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.