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

—

Does it follow best practices?

Impact

98%

1.28x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a broad, well-structured reference with real executable Terraform examples, but it is padded with concept restatements, lacks validation feedback loops in its workflow, and cites bundle files that are missing.

Suggestions

Create the referenced 'references/tagging-standards.md' and 'assets/cost-analysis-template.xlsx' (or remove the references) so signaled progressive-disclosure links resolve to real files.

Trim bullet sections that restate common knowledge (e.g. serverless 'Auto-scaling included', Sustained Use Discounts 'Automatic discounts') to tighten token use.

Add an explicit validation/checkpoint step to the cost-optimization workflow (e.g. verify savings via Cost Explorer after a rightsizing change) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete code blocks, but many bullet sections restate concepts Claude already knows ('Auto-scaling included', 'Pay only for execution time', 'Automatic discounts') and the ~280-line body could be tightened.	2 / 3
Actionability	Several executable Terraform HCL blocks (S3 lifecycle, tagging, budgets, autoscaling) are copy-paste ready, but the Azure, GCP, and architecture-pattern sections are descriptive bullet lists with no commands or code, leaving guidance incomplete.	2 / 3
Workflow Clarity	A sequenced four-phase framework (Visibility, Right-Sizing, Pricing Models, Architecture Optimization) and an end checklist exist, but there are no explicit validation checkpoints or error-recovery feedback loops.	2 / 3
Progressive Disclosure	Sections are well-organized, but the body is monolithic with all per-cloud detail inline, and the two referenced bundle files ('references/tagging-standards.md', 'assets/cost-analysis-template.xlsx') do not exist, so the signaled references are broken.	2 / 3
	Total	8 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, uses third-person imperative voice, and pairs concrete capabilities with an explicit 'Use when' trigger. It is well-distinguished and free of fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'resource rightsizing, tagging strategies, reserved instances, and spending analysis' — rather than vague language, matching the top anchor.	3 / 3
Completeness	Explicitly answers both what ('Optimize cloud costs through...') and when via a clear 'Use when...' clause, satisfying the highest anchor.	3 / 3
Trigger Term Quality	'Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies' provides natural phrasings a user would actually say, with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The cloud cost-optimization niche is clear with distinct triggers ('cloud expenses', 'infrastructure costs', 'cost governance'), unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: abece4a

Reviewed: 4 days 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.