cost-optimization-analyzer
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cost-optimization-analyzerCost Optimization Analyzer - Auto-activating skill for AWS Skills. Triggers on: cost optimization analyzer, cost optimization analyzer Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just naming the skill without explaining what it actually does or when users would need it. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The redundant trigger term and absence of capability details make this ineffective for skill selection among multiple options.
Suggestions
Add specific capabilities: 'Analyzes AWS spending patterns, identifies unused or underutilized resources, recommends Reserved Instance purchases, detects cost anomalies'
Include natural trigger terms users would say: 'AWS costs', 'cloud spending', 'billing', 'save money', 'expensive resources', 'cost reduction'
Add explicit 'Use when...' clause: 'Use when the user asks about reducing AWS costs, analyzing cloud spending, finding unused resources, or optimizing their AWS bill'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Cost Optimization Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'analyzes spending patterns', 'identifies unused resources', or 'recommends cost-saving measures'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and the 'when' clause only triggers on the exact tool name rather than describing use cases. There is no explicit 'Use when...' guidance with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cost optimization analyzer' listed twice) and overly specific to the tool name. Missing natural user phrases like 'reduce AWS costs', 'save money on cloud', 'billing analysis', 'spending', or 'expensive resources'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Cost Optimization Analyzer' is somewhat specific to AWS cost analysis, the lack of detail means it could conflict with other AWS-related skills or general cost/billing skills. The AWS context provides some distinction. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no substantive content. It describes what a cost optimization analyzer skill would do without providing any actual guidance, code, AWS-specific commands, or actionable instructions. The content is entirely meta-description without any practical value for performing cost optimization tasks.
Suggestions
Add concrete AWS CLI commands or boto3 code for analyzing costs (e.g., `aws ce get-cost-and-usage` examples with specific parameters)
Include a clear workflow for cost analysis: 1) Pull cost data, 2) Identify top spending services, 3) Generate recommendations, 4) Validate savings estimates
Provide specific examples of cost optimization patterns (e.g., identifying unused EC2 instances, right-sizing recommendations, Reserved Instance analysis)
Add references to AWS Cost Explorer API documentation and link to detailed guides for specific optimization scenarios
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The entire skill describes what it does abstractly without any executable instructions for actually performing cost optimization analysis. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for cost optimization analysis. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, no links to related resources, and no structured navigation. The content is a shallow placeholder with no depth or organization. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.