optimize-triage
Fetch top unaddressed CloudZero Optimize recommendations, dispatch parallel research agents per item, apply SRE critique, and surface actionable findings with confidence verdicts and per-resource report files. Read-only research only.
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/cost-analyst/skills/optimize-triage/SKILL.mdQuality
Discovery
67%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 excels at specificity and distinctiveness by naming a concrete platform (CloudZero Optimize) and detailing a multi-step workflow. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms are somewhat technical and may not match how users naturally phrase their requests.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about CloudZero cost optimization recommendations, cloud cost savings, or wants to review unaddressed optimization opportunities.'
Include more natural user-facing trigger terms such as 'cost optimization', 'cloud spending', 'cost reduction', 'savings recommendations', or 'cloud waste' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fetch recommendations, dispatch parallel research agents, apply SRE critique, surface actionable findings with confidence verdicts, and generate per-resource report files. Also specifies 'read-only research only' as a constraint. | 3 / 3 |
Completeness | The 'what' is well-covered with specific actions and outputs, but there is no explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. This caps the score at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'CloudZero Optimize', 'recommendations', 'SRE critique', and 'confidence verdicts', but these are fairly technical. Missing natural user phrases like 'cost optimization', 'cloud spending', 'cost savings', or 'cloud recommendations' that users would more likely say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'CloudZero Optimize' as the platform, combined with the unique workflow of parallel research agents and SRE critique. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent workflow clarity — clear phases, decision points, validation criteria, and concrete commands throughout. Its main weakness is that all content is packed into a single large file with no progressive disclosure via supporting documents, and there's minor redundancy (repeated read-only disclaimers). The depth of domain-specific guidance (per-resource-type checks, confidence verdicts, report templates) is impressive and genuinely useful.
Suggestions
Extract the per-resource-type check commands (Check D) and category-specific guidance (Check E) into a separate CHECKS.md reference file to reduce the main skill's length and improve progressive disclosure.
Move the Phase 6 report template into a separate REPORT-TEMPLATE.md file, referenced from the main skill, to keep the primary workflow focused on orchestration logic.
Consolidate the 4 separate 'read-only' disclaimers into a single prominent notice at the top to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is long (~300+ lines) but most content is genuinely instructive and non-obvious (specific CLI commands, check categories, validation criteria, report templates). However, there's some redundancy — the 'read-only' disclaimer appears 4 times, and some sections like the agent instructions preamble could be tightened. It doesn't explain things Claude already knows, but it could be more compact. | 2 / 3 |
Actionability | Highly actionable throughout: specific CLI commands (aws s3api, gcloud, kubectl), exact grep patterns with proper flags, concrete table formats for output, specific file naming conventions for reports, and detailed per-resource-type check commands. The workflow is copy-paste ready with real executable commands and clear output expectations. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with clear sequencing (Phases 1-6), explicit decision points (threshold selection, user confirmation), validation checkpoints (Phase 3 internal validation with specific criteria), error handling ('hit a dead end — stop and ask'), and feedback loops (Phase 5 follow-up research loop that can update verdicts). The VALID/INVALID/UNCERTAIN labeling and confidence verdicts provide structured validation. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and phases, but it's entirely monolithic — all ~300+ lines live in a single file with no references to supporting documents. The check categories (A-E), report template, and category-specific guidance could each be split into separate reference files. For a skill this complex, the lack of any bundle files or cross-references is a missed opportunity. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | 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.