cx-observability-setup

Use this skill when the user asks to "set up monitoring", "configure observability", "onboard new service", "create saved view", "set up notifications", "configure webhook", "set up Slack integration", "outgoing webhook", "automation action", "webhook for alerts", "create view", "saved view", "view folder", "organize dashboards", "install integration", "configure extension", "contextual data", "connect external service", "create notification connector", "set up email alerts", "configure PagerDuty", "notification routing", "deploy extension", "test webhook", "notification preset", "test notification", "webhook actions", or wants to set up, configure, or manage the observability stack for a service or team.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cx-observability-setup/SKILL.md

Quality

Content

65%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.

Highly actionable command reference with well-sequenced setup workflows, but it is weighed down by redundant command listings, no validation guidance for destructive/batch operations, and a large inline command table that belongs in a separate reference file.

Suggestions

Move the four CLI command tables into a references/ file (e.g. COMMANDS.md) and link to it from a short overview, keeping only the workflow steps and key principles inline in SKILL.md.

Add a validation/confirmation checkpoint before destructive and batch operations — e.g. a Key Principle like 'Confirm before delete: cx <resource> get <id> -o json and review before running delete, undeploy, actions batch, or actions reorder.'

De-duplicate the workflow sections: reference commands by name rather than re-printing full command lines that already appear in the command tables, or consolidate the Notification and Webhook setup sections into the New Service Setup checklist.

Dimension	Reasoning	Score
Conciseness	Per-line content is lean, but the ~250-line body re-lists commands across the New Service, Notification, and Webhook workflow sections that already appear in the command tables, adding redundant tokens that could be tightened.	3 / 5
Actionability	Fully executable CLI commands with real flags (--from-file, -o json) and concrete file names, plus a copy-paste-ready "template from existing" pattern (cx webhooks get <id> -o json > webhook-template.json) covering the common cases.	5 / 5
Workflow Clarity	Setup workflows include test checkpoints, but the skill exposes destructive (delete, extensions undeploy) and batch (actions batch, actions reorder) operations with no validation or confirmation guidance, so per the rubric cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Section headers are clear, but ~120 lines of command reference are inlined in SKILL.md with no bundle files or one-level-deep references to move the bulk API reference into a separate file.	3 / 5
	Total	14 / 20 Passed

Description

91%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 clearly states both purpose and invocation conditions with comprehensive natural keywords. Minor overlap risk with sibling cx skills and a trigger-phrase framing (vs. a crisp capability sentence) keep it just short of perfect.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ("create saved view", "configure webhook", "deploy extension", "configure PagerDuty") with comprehensive coverage, but they are framed as user-trigger phrases rather than a clean capability statement, leaving a minor gap versus the 5 anchor.	4 / 5
Completeness	Explicitly answers both "what" ("set up, configure, or manage the observability stack for a service or team") and "when" ("Use this skill when the user asks to ..." with concrete trigger phrases).	5 / 5
Trigger Term Quality	Extensive natural phrases a user would actually say, including synonyms ("saved view"/"create view"/"create saved view") and channel-specific terms (Slack, PagerDuty, email), giving comprehensive trigger coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear observability-setup niche with specific triggers, but broad phrases like "set up notifications" and "organize dashboards" create minor overlap with the related cx-dashboards/cx-alerts skills referenced in the body.	4 / 5
	Total	18 / 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-observability-setup/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.