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
Quality
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 severely underdeveloped, essentially just stating the skill name without explaining what it does or when to use it. It lacks any concrete actions, meaningful trigger terms, or explicit usage guidance. The redundant trigger term ('cost optimization analyzer' repeated twice) suggests a template that wasn't properly filled out.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes AWS resource usage, identifies underutilized instances, recommends Reserved Instance purchases, and generates cost-saving reports'
Include a 'Use when...' clause with natural trigger terms like 'reduce AWS spending', 'cloud costs too high', 'billing optimization', 'EC2 costs', 'right-sizing', or 'cost explorer'
Remove the redundant trigger term and replace with varied, user-natural phrases that would appear in actual requests
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Cost Optimization Analyzer') without describing any concrete actions. There are no specific capabilities listed - no verbs describing what the skill actually does with AWS costs. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use cases or trigger guidance beyond the redundant skill name). Both components are missing or very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('cost optimization analyzer, cost optimization analyzer'). Missing natural user phrases like 'reduce AWS costs', 'save money', 'billing analysis', 'expensive resources', or 'cost savings'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'AWS' and 'Cost Optimization' provide some domain specificity, the lack of concrete actions means it could overlap with other AWS-related skills or generic cost analysis tools. The mention of being 'Part of the AWS Skills skill category' helps slightly. | 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 a placeholder template with no actual content. It contains only generic boilerplate text that could apply to any skill, with 'cost optimization analyzer' substituted in. There is no AWS-specific guidance, no code examples, no actual cost optimization techniques, and no actionable information whatsoever.
Suggestions
Add concrete AWS cost optimization techniques with executable code (e.g., boto3 scripts to identify unused EC2 instances, analyze S3 storage classes, or review Reserved Instance coverage)
Include specific AWS CLI commands or SDK examples for common cost analysis tasks like querying Cost Explorer API or generating cost reports
Provide a clear workflow for cost optimization analysis: identify resources -> analyze usage patterns -> recommend optimizations -> validate savings
Add references to AWS-specific tools and services (Cost Explorer, Trusted Advisor, Compute Optimizer) with concrete usage examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It repeats 'cost optimization analyzer' multiple times without providing any concrete information about what it does or how to use it. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The content only describes vague capabilities ('provides step-by-step guidance') without actually providing any steps, code, or specific instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for performing cost optimization analysis on AWS. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no links to AWS-specific resources, and no organization of content by complexity or use case. | 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
0c08951
- 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.