optimizing-cloud-costs

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill optimizing-cloud-costs

Execute use when you need to work with cloud cost optimization. This skill provides cost analysis and optimization with comprehensive guidance and automation. Trigger with phrases like "optimize costs", "analyze spending", or "reduce costs".

41%

Overall

Validation — 81%

Implementation — 20%

Activation — 40%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

20%

This skill is a generic template with 'cloud cost optimizer' inserted into placeholders. It contains no actual cloud cost optimization knowledge - no specific cloud providers, no cost analysis tools, no optimization techniques, no example queries or commands. The content would be equally (in)applicable to database administration, security auditing, or any other domain.

Suggestions

Add concrete, executable examples: specific AWS/GCP/Azure CLI commands for cost analysis (e.g., `aws ce get-cost-and-usage`), queries for identifying unused resources, or scripts for rightsizing recommendations

Include specific cost optimization techniques: reserved instance analysis, spot instance strategies, storage tier optimization, idle resource identification with actual tool commands

Replace generic steps with cloud cost-specific workflows: e.g., '1. Run `aws ce get-cost-and-usage --time-period Start=2024-01-01,End=2024-01-31` 2. Identify top 5 cost drivers 3. For each, check utilization with CloudWatch metrics'

Remove all generic boilerplate (prerequisites, error handling sections) that don't contain cloud cost-specific information - Claude already knows to test in staging and handle permission errors

Dimension	Reasoning	Score
Conciseness	Extremely verbose with generic boilerplate that applies to any task. Contains no cloud cost-specific information - the entire content could be copy-pasted for any skill topic. Explains obvious concepts like 'backup critical data' and 'test in staging' that Claude already knows.	1 / 3
Actionability	Completely abstract with zero concrete guidance. No actual cloud cost commands, no specific tools (AWS Cost Explorer, GCP Billing, etc.), no code examples, no specific metrics to analyze. Instructions like 'Review current configuration' provide no actionable direction for cost optimization.	1 / 3
Workflow Clarity	Steps are numbered and sequenced, but they're generic project management phases rather than cloud cost optimization workflows. No validation checkpoints specific to cost analysis (e.g., 'verify savings estimate before implementing'), no feedback loops for cost monitoring.	2 / 3
Progressive Disclosure	References external files in Resources section which is good structure, but the main content is a wall of generic text. The referenced files use placeholder paths that may not exist. Overview and Examples sections at the bottom are empty placeholders.	2 / 3
	Total	6 / 12 Passed

Activation

40%

This description suffers from vague, buzzword-heavy language that fails to communicate concrete capabilities. While it includes some trigger phrases, the lack of specific actions (what analysis is performed, what automation is provided, which cloud platforms are supported) makes it difficult to understand when this skill should be selected over alternatives.

Suggestions

Replace vague phrases like 'comprehensive guidance and automation' with specific actions (e.g., 'Identifies unused resources, rightsizes instances, analyzes reserved instance coverage, generates cost allocation reports').

Add cloud platform specificity to improve distinctiveness (e.g., 'for AWS, Azure, and GCP environments').

Expand trigger terms to include common variations like 'cloud billing', 'cost report', 'spending breakdown', 'resource utilization', and specific platform names.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'cost analysis and optimization with comprehensive guidance and automation' without listing any concrete actions. No specific capabilities are enumerated (e.g., what kind of analysis, what gets automated).	1 / 3
Completeness	Has a 'Use when' equivalent with trigger phrases, but the 'what' portion is extremely weak - 'cost analysis and optimization with comprehensive guidance and automation' is vague fluff that doesn't explain what the skill actually does.	2 / 3
Trigger Term Quality	Includes some natural trigger phrases ('optimize costs', 'analyze spending', 'reduce costs') that users might say, but missing common variations like 'cloud billing', 'AWS/Azure/GCP costs', 'cost report', or 'spending breakdown'.	2 / 3
Distinctiveness Conflict Risk	Mentions 'cloud cost optimization' which provides some domain specificity, but 'cost analysis' and 'reduce costs' are generic enough to potentially conflict with financial analysis or budgeting skills.	2 / 3
	Total	7 / 12 Passed

Reviewed

14 days ago

Table of Contents

Validation Implementation Activation

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.