aws-cost-optimizer

Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is strong on actionability with concrete, executable AWS CLI commands, but is held back by redundant padding and a destructive-operations workflow that lacks explicit validation checkpoints. Progressive disclosure is limited because all reference material is inline with no bundle files to offload it.

Suggestions

Remove or trim low-value sections ('Best Practices', 'Integration with Kiro CLI', example prompts) that restate the capability bullets and CLI examples.

Add explicit validation/verification checkpoints into the Optimization Workflow (e.g., 'Confirm volume is unattached and untagged before deletion' as a gated step).

Move the detailed command catalog and checklist into a separate reference file (e.g., REFERENCES.md) and signal it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The AWS CLI command blocks and optimization workflow are lean and useful, but redundant padding ('Best Practices', 'Cost Optimization Checklist', the marketing-style 'Integration with Kiro CLI' section, and example prompts that restate capability bullets) keeps it at 'mostly efficient but includes some unnecessary' content rather than fully lean.	2 / 3
Actionability	Provides fully executable, copy-paste-ready `aws` CLI commands with real flags, JMESPath `--query` expressions, and date arithmetic, matching the 'fully executable code/commands; specific examples; copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear four-step Optimization Workflow exists, but it involves destructive/batch operations (delete unattached EBS volumes, release EIPs, terminate idle EC2, delete old snapshots) without explicit verify-before-act validation checkpoints embedded in the workflow steps, so per the guideline workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	No bundle files exist and everything is inline in a ~190-line SKILL.md; while sections are well-organized, the detailed command catalog and checklist are content that could be split into separate reference files, matching the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 conveys a clear, distinctive niche and relevant tooling but stops short of listing multiple concrete actions and omits any explicit 'Use when...' trigger guidance. It is competent but not exemplary, sitting at the mid-range of the rubric.

Suggestions

Expand the description to list multiple concrete actions (e.g., 'identify idle EC2 instances, find unattached EBS volumes, recommend Reserved Instance purchases').

Add an explicit 'Use when...' trigger clause naming natural user phrasings like 'spending', 'reduce my AWS bill', or 'cloud waste'.

Trim vague intensifiers like 'Comprehensive' in favor of specific, enumerated capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and tooling ("AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer") but does not enumerate multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action score-3 example.	2 / 3
Completeness	Answers 'what' (cost analysis and optimization recommendations) but provides no 'when' — there is no 'Use when...' clause or equivalent explicit trigger, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains relevant keywords ('AWS cost', 'Cost Explorer') but misses common natural phrasings a user would actually say (e.g., 'spending', 'reduce my AWS bill', 'cloud waste') and has no 'Use when...' trigger, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (AWS cost optimization) with distinct tooling references, making it unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 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.