cost-optimization-analyzer
Cost Optimization Analyzer - Auto-activating skill for AWS Skills. Triggers on: cost optimization analyzer, cost optimization analyzer Part of the AWS Skills skill category.
35
3%
Does it follow best practices?
Impact
95%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/cost-optimization-analyzer/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that names the skill and its category but provides no substantive information about what it does or when it should be used. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes AWS billing data, identifies underutilized resources, recommends Reserved Instance purchases, and flags idle EC2 instances and unused EBS volumes.'
Add a 'Use when...' clause with natural trigger terms like 'reduce AWS costs', 'cloud spending', 'billing analysis', 'unused resources', 'right-sizing', 'savings plan'.
Remove the duplicate trigger term ('cost optimization analyzer' is listed twice) and replace with diverse, natural phrases users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Cost Optimization Analyzer' and 'AWS Skills') but describes no concrete actions. There are no specific capabilities listed such as analyzing billing, identifying unused resources, or recommending savings. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause is just a repetition of the skill name rather than meaningful trigger guidance. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'cost optimization analyzer' repeated twice. These are not natural phrases users would say — users are more likely to say 'reduce AWS costs', 'save money on cloud', 'billing analysis', or 'unused resources'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'AWS' and 'cost optimization' provides some specificity that narrows the domain, but without concrete actions it could overlap with other AWS-related skills or general cost analysis skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It repeatedly references 'cost optimization analyzer' without ever defining what it does, how to use it, or providing any actionable guidance. There is no code, no commands, no concrete examples, and no real information about AWS cost optimization.
Suggestions
Add concrete, executable guidance such as AWS CLI commands for Cost Explorer queries, example boto3 scripts for analyzing spend, or specific CloudWatch/Cost Explorer API calls.
Define a clear workflow: e.g., 1) Pull cost data via AWS Cost Explorer API, 2) Identify top spend categories, 3) Analyze underutilized resources, 4) Generate recommendations with specific actions.
Include specific examples of cost optimization patterns (e.g., right-sizing EC2 instances, S3 lifecycle policies, Reserved Instance analysis) with copy-paste ready code or configurations.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that contain no actionable information and replace with actual technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'cost optimization analyzer' excessively, and provides zero substantive information about AWS cost optimization. | 1 / 3 |
Actionability | There are no concrete steps, commands, code examples, or specific guidance. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints — just generic claims about capabilities without any actual process. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no references to detailed materials, no links to related files, and no meaningful structure beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.