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.
55
61%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cx-cost-optimization/SKILL.mdQuality
Discovery
44%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 essentially a long list of trigger phrases with no explanation of what the skill actually does. While it excels at providing natural keywords users might say and is clearly distinctive to Coralogix cost management, it completely lacks any description of the skill's concrete capabilities or actions. The description also uses second person ('Use this skill when the user asks') rather than describing what the skill does in third person.
Suggestions
Add a clear 'what it does' statement at the beginning, e.g., 'Analyzes Coralogix data ingestion costs, queries TCO policies, identifies usage anomalies, and recommends cost optimization strategies for observability spend.'
Restructure to lead with concrete capabilities first, then follow with a 'Use when...' clause containing the trigger terms, rather than having only trigger terms.
Rewrite in third person voice describing actions (e.g., 'Queries Coralogix usage APIs, generates cost breakdowns, and modifies TCO retention tiers') instead of the current format.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists no concrete actions or capabilities. It only provides trigger phrases but never states what the skill actually does (e.g., 'queries usage APIs', 'generates cost reports', 'modifies TCO policies'). There are no specific actions described. | 1 / 3 |
Completeness | The description answers 'when' extensively with trigger phrases but completely fails to answer 'what does this do'. There is no explanation of the skill's capabilities, actions, or outputs. The 'what' component is entirely missing. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say, including variations like 'reduce Coralogix costs', 'lower our logging bill', 'why is our bill so high', 'spending too much on logs', plus technical terms like 'TCO policy', 'retention tier', 'cx_data_usage_units'. Very comprehensive keyword list. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Coralogix cost optimization and data usage management. The platform-specific terms ('Coralogix', 'TCO policy', 'cx_data_usage_units') make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 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 strong, highly actionable skill with excellent workflow clarity and safety guardrails. The cost investigation workflow is well-sequenced with concrete commands at every step, and the PromQL metrics section adds significant value for advanced analysis. The main weakness is length—the skill could benefit from splitting detailed reference material (jq examples, PromQL queries, metrics tables) into separate files to improve token efficiency and progressive disclosure.
Suggestions
Extract the 'jq Examples' and 'Metrics-Based Cost Analysis' sections into separate reference files (e.g., JQ_EXAMPLES.md, METRICS_REFERENCE.md) and link to them from the main skill to reduce token footprint.
Remove the jq commands in the 'jq Examples' section that duplicate commands already shown in the workflow steps (e.g., the usage summary sort appears in both Step 1 and the jq section).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient and avoids explaining basic concepts, but it's quite long (~200+ lines) with some redundancy—e.g., the jq examples section repeats commands already shown in the workflow, and the 'Common Optimization Patterns' table partially duplicates Step 5 guidance. Some tightening is possible. | 2 / 3 |
Actionability | Excellent actionability throughout: every step includes copy-paste-ready bash commands with specific flags, jq pipelines for analysis, and concrete PromQL queries. The optimization patterns table maps symptoms directly to diagnosis commands and remediation actions. | 3 / 3 |
Workflow Clarity | The 5-step cost investigation workflow is clearly sequenced with explicit validation (Step 2 after Step 1, verify after changes). The 'Applying Changes' section includes a feedback loop (template → edit → apply → verify), safety constraints (never pass --yes without approval), and read-only mode for safe exploration. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a logical progression from CLI commands to workflows to advanced PromQL analysis. However, given the length, the detailed jq examples, PromQL queries, and metrics reference could be split into separate files. There's only one cross-reference (to cx-telemetry-querying) and no bundle files to offload content to. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coralogix/cx-cli
- Commit
34d6303
- 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.