CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-cost-optimizer

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

54

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-aws-cost-optimizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 content is highly actionable with executable AWS CLI commands and example prompts, but it is somewhat verbose, lacks validation checkpoints around its destructive quick-win steps, and keeps everything inline rather than splitting reference material into separate files.

Suggestions

Add explicit validation checkpoints to destructive quick-wins (e.g. 'Verify a volume is unattached and unowned before deletion; confirm with the user or --dry-run first') to lift workflow clarity above 3.

Move the bulk CLI command catalogue and/or checklist into references/ files (e.g. commands.md, checklist.md) and link to them one level deep to improve progressive disclosure.

Trim redundant sections (Example Prompts, Best Practices) that restate capabilities already shown in the command catalogue to reduce token load.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands, but sections like the full CLI command catalogue, checklist, and example-prompts restate capability lists already covered and could be tightened; some over-explanation (e.g. 'Integration with Kiro CLI') adds tokens.

3 / 5

Actionability

Provides copy-paste-ready, fully executable AWS CLI commands with real flags and --query syntax covering the common cost and resource-analysis cases, plus concrete example prompts.

5 / 5

Workflow Clarity

The 4-step Optimization Workflow is sequenced, but destructive/batch quick-win steps ('Delete unattached EBS volumes', 'Release unused Elastic IPs') lack explicit verify-before-delete validation checkpoints, which per the rubric caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

The body is well-sectioned but monolithic within SKILL.md (no references/ or scripts/ files exist despite the large command catalogue and checklist that could be split out), and there are no one-level-deep reference pointers, so structure is present but not optimally split.

3 / 5

Total

14

/

20

Passed

Description

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

The description conveys a concrete AWS cost-optimization niche with named tools, but it lacks an explicit 'Use when...' trigger clause and uses a few generic phrases ('Comprehensive', 'recommendations'), capping completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing AWS spending, finding wasted resources, or reducing cloud costs.'

Replace generic terms ('Comprehensive', 'recommendations') with concrete actions matching the body, e.g. 'Detect idle EC2 instances, unattached EBS volumes, and Reserved Instance opportunities.'

Include natural user synonyms such as 'AWS bill', 'wasted spend', or 'cloud waste' to improve trigger-term quality.

DimensionReasoningScore

Specificity

Lists several concrete actions ('AWS cost analysis', 'optimization recommendations') tied to specific tools ('AWS CLI', 'Cost Explorer'), but 'Comprehensive ... recommendations' is mildly generic and coverage of the actual actions is narrower than the body implies.

4 / 5

Completeness

It gives a clear 'what' (cost analysis and optimization recommendations) but no explicit 'when' / 'Use when...' trigger clause, so per the rubric a missing trigger caps completeness at 3.

3 / 5

Trigger Term Quality

'AWS cost analysis', 'AWS CLI', 'Cost Explorer' are relevant but the description omits natural user phrases like 'reduce my AWS bill', 'find wasted spend', or 'cost optimization', and includes no synonyms.

3 / 5

Distinctiveness Conflict Risk

The AWS-cost niche is fairly distinct and unlikely to clash with unrelated skills, though it could overlap with a generic AWS skill; minor overlap risk keeps it just below 5.

4 / 5

Total

14

/

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.

Validation15 / 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
boisenoise/skills-collections
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.