diff-cost-projection
Analyze code diffs for infrastructure cost impact using CloudZero spend data. Detects Terraform, CDK, CloudFormation, SAM, K8s, scaling, and application code changes that affect cloud spending.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
82%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 is a strong description with excellent specificity and trigger term coverage across multiple IaC technologies and cloud cost concepts. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The domain is distinctive enough that conflict risk is minimal.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user submits a code diff or pull request and wants to understand its cloud cost implications, or when reviewing infrastructure changes for spending impact.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyzing code diffs for cost impact, detecting changes across Terraform, CDK, CloudFormation, SAM, K8s, scaling, and application code. These are concrete, named technologies and actions. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (analyze code diffs for infrastructure cost impact using CloudZero data, detect IaC changes), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural keywords users would say: 'code diffs', 'infrastructure cost', 'CloudZero', 'Terraform', 'CDK', 'CloudFormation', 'SAM', 'K8s', 'scaling', 'cloud spending'. These are terms developers naturally use when discussing infrastructure cost analysis. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining code diff analysis with cloud cost impact via CloudZero. The specific combination of infrastructure-as-code tools and cost analysis makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, complex skill that excels at workflow clarity and progressive disclosure. The 7-phase structure with multiple early-exit points and explicit validation checkpoints is exemplary for a multi-step process. The content is highly actionable with executable commands, specific API call patterns, and concrete estimation formulas. Minor verbosity in some sections (trigger examples, confidence level explanations) prevents a perfect conciseness score, but the length is largely justified by the complexity of the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300+ lines) but most content is genuinely instructional for a complex multi-phase workflow. Some sections are slightly verbose (e.g., the 'When to Use' bullet list with 6 examples, explaining what confidence levels mean when Claude understands this). The classification table and estimation approaches are dense but necessary. Overall mostly efficient with some tightening possible. | 2 / 3 |
Actionability | Highly actionable throughout — provides executable bash commands for diff retrieval, specific file pattern matching tables, concrete CloudZero API call patterns with parameters, precise estimation formulas (M/N ratios, hourly×730), and detailed report structure. Each phase has clear, specific instructions rather than vague guidance. | 3 / 3 |
Workflow Clarity | Excellent 7-phase workflow with clear sequencing, multiple explicit early-exit checkpoints (empty diff → stop, all files skipped → stop, no signals → stop), validation steps (verify dimension values exist before querying), and error handling guidance (CloudZero queries fail → still provide analysis). The feedback loops and conditional branching are well-defined throughout. | 3 / 3 |
Progressive Disclosure | The SKILL.md serves as a clear orchestration document with well-signaled references to 8 separate reference files for detailed content (taxonomy, service mapping, output examples, best practices, tool reference, dimensions, cost types, error handling). References are one level deep and clearly placed at the point of use within each phase, plus collected in a 'See Also' section. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Cloudzero/cloudzero-claude-marketplace
- Commit
760a9c7
- 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.