cost-optimization

Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.

1.28x

Quality

74%

Does it follow best practices?

Impact

98%

1.28x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/cost-optimization/SKILL.md

The canonical home for this skill is cost-optimization in wshobson/agents

Quality

Content

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

The body is actionable and mostly token-efficient with good code examples, but its batch optimization workflow lacks validation checkpoints and it inlines large cloud-specific sections while citing bundle files that do not exist.

Suggestions

Add validation/verification steps to the cost-optimization workflow — e.g., measure utilization before downsizing and verify spend after each change — so batch/destructive actions have feedback loops.

Create the referenced 'references/tagging-standards.md' and 'assets/cost-analysis-template.xlsx' (or remove the broken citations), and move the per-cloud pricing detail into separate reference files to keep SKILL.md a lean overview.

Tighten the repeated AWS/Azure/GCP pricing bullet lists into a single comparison table to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Largely dense lists and code with no concept-explanation fluff, but repeated per-cloud pricing bullets and several code blocks add length that could be tightened, fitting anchor 4 over 5.	4 / 5
Actionability	Provides executable Terraform/HCL for S3 lifecycle, tagging, budgets, and autoscaling plus concrete savings percentages and tool names; minor gaps (some Reserved Instance sections are plain-text specs rather than code) keep it at anchor 4.	4 / 5
Workflow Clarity	A numbered 4-phase framework and a checklist provide a sequence, but batch/destructive operations (rightsizing, deleting resources) lack any validation or verify-savings checkpoints, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The body references 'references/tagging-standards.md' and 'assets/cost-analysis-template.xlsx', but neither file nor its directory exists, and all cloud-specific detail is inlined rather than split out, matching anchor 2 (inlined content that belongs in separate files).	2 / 5
	Total	13 / 20 Passed

Description

87%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, well-formed description: third-person voice, concrete capabilities, and an explicit 'Use when' trigger clause covering both what and when. Minor keyword-coverage gaps keep trigger quality and specificity at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions ('resource rightsizing, tagging strategies, reserved instances, and spending analysis') but stops short of comprehensive coverage, so it sits at anchor 4 rather than 5.	4 / 5
Completeness	Explicitly answers both 'what' (optimize cloud costs through four named strategies) and 'when' (an explicit 'Use when...' clause with concrete trigger phrases), matching the anchor 5 example.	5 / 5
Trigger Term Quality	Natural trigger phrases ('reducing cloud expenses', 'analyzing infrastructure costs', 'implementing cost governance policies') give good keyword coverage, though a few common phrasings a user might say are absent.	4 / 5
Distinctiveness Conflict Risk	'Cloud cost optimization' is a clear niche with distinct triggers (cost governance, reserved instances, rightsizing) and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/cloud-infrastructure/skills/cost-optimization/SKILL.md
Commit: 6453c0b

Reviewed: about 10 hours 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.