Name: cx-cost-optimization
Rating: 73.6 (1 reviews)
Author: coralogix

cx-cost-optimization

Use this skill when the user asks to "check data usage", "list TCO policies", "reduce Coralogix costs", "optimize observability spend", "lower our logging bill", "data budget exceeded", "TCO policy", "retention tier", "archive storage", "ingestion costs", "frequent search vs archive", "why is our bill so high", "spending too much on logs", "data retention settings", "cost analysis", "usage breakdown", "optimize log volume", "control data ingestion", "archive cold data", "billing units", "plan consumption", "daily plan", "overage", "PAYG", "usage anomaly", "usage trend", "cx_data_usage_units", or wants to investigate, analyze, or reduce Coralogix data costs.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable command reference with a well-sequenced investigation workflow and explicit validation/approval safeguards for write operations. The main weakness is repetition of the two-step usage workflow and diagnosis commands across sections, which could be tightened.

Suggestions

Consolidate the mandatory two-step usage workflow into one place and have Step 1 reference it rather than restating it, to reduce redundancy.

Move the detailed jq and PromQL query catalogs into a separate reference file, keeping only the canonical examples inline in SKILL.md.

Deduplicate the diagnosis commands that appear in both the workflow steps and the "Common Optimization Patterns" table.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept padding, but the mandatory two-step usage workflow is repeated in "Authoritative Billable Usage Queries" and again in "Step 1", and diagnosis commands are duplicated across the workflow and the "Common Optimization Patterns" table — noticeable tightening opportunity.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — CLI invocations with flags, jq pipelines, and PromQL queries covering the common cost-analysis cases, matching the anchor for fully executable guidance.	5 / 5
Workflow Clarity	The 5-step Cost Investigation Workflow is clearly sequenced with an explicit validation checkpoint ("Verify after changes: Re-run the diagnosis commands to confirm the change took effect") and a template→modify→apply→verify feedback loop, plus approval gating for destructive writes.	5 / 5
Progressive Disclosure	Good section structure with one clearly signaled, one-level-deep reference (references/data-usage-query-api.md, which exists) linked from both body and the Reference Files section; however a large amount of detailed PromQL/jq reference material is inlined that could live in separate files.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description that explicitly covers what the skill does and when to use it with many natural user phrases and domain-specific synonyms. It is comprehensive and clearly scoped to the Coralogix cost niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "check data usage", "list TCO policies", "reduce Coralogix costs", "optimize log volume", "control data ingestion", "archive cold data" — with comprehensive coverage of the cost-management domain, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ("investigate, analyze, or reduce Coralogix data costs") and when ("Use this skill when the user asks to ...") with concrete trigger phrases, matching the anchor that requires both clearly and explicitly.	5 / 5
Trigger Term Quality	Comprehensive natural phrases users would actually say ("why is our bill so high", "spending too much on logs", "data budget exceeded", "lower our logging bill") plus synonyms and technical terms (PAYG, overage, billing units, cx_data_usage_units), matching the anchor for comprehensive coverage including synonyms.	5 / 5
Distinctiveness Conflict Risk	Targets a clear Coralogix cost-optimization niche with distinct triggers (TCO policies, retention tier, archive storage, PAYG, cx_data_usage_units), giving minimal conflict risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: coralogix/cx-cli
Path: skills/cx-cost-optimization/SKILL.md
Commit: 4aa811a

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.