CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, well-structured CLI setup skill with concrete commands and explicit test-after-setup validation in every workflow. Its consistent gaps are the unspecified --from-file JSON payload schemas and the monolithic inline command catalog that belongs in a reference file.

Suggestions

Move the full command catalog to references/commands.md and keep a short command-group summary in SKILL.md, surfacing only the commands used in the workflows.

Add one minimal example JSON payload (e.g., a Slack connector or router) or point to how to discover payload schemas, so the create steps are fully executable.

Add a short error-recovery note after each test step (e.g., what to check and re-run when cx notifications test destination fails) to close the feedback loop.

DimensionReasoningScore

Conciseness

No concept explanations or padding — commands appear as dense table rows and workflows as bare command sequences — but the ~100-line full command catalog (60+ commands including contextual-data, entity-subtypes, and template-render) goes well beyond what the four described workflows use and could be trimmed.

4 / 5

Actionability

Exact, copy-paste-ready cx commands appear throughout, plus a concrete payload-construction pattern ("cx webhooks get <existing-id> -o json > webhook-template.json"), but none of the --from-file JSON payloads (view.json, slack-connector.json, router.json, etc.) are ever exemplified or given schemas, leaving a gap at every create step.

4 / 5

Workflow Clarity

Sequenced checklists with explicit validation checkpoints ("Test End-to-End" step, "Always test after setup" principle, cx webhooks test), but there is no error-recovery guidance for when a test fails, and steps 6–7 of the new-service workflow simply delegate to other skills without any detail.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, tables, and a Related Skills map, making navigation easy, but the inline 100-line command reference is exactly the bulk content that should live one level deep in a references/ file rather than in SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

82%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 trigger-phrase-first description with excellent natural keyword coverage and an explicit use-when clause. Its main weakness is that the "what" is never directly stated in third-person capability form — capabilities must be inferred from the quoted trigger list — plus a couple of trigger terms that overlap sibling skills.

Suggestions

Add a direct third-person capability sentence (e.g., "Creates saved views, configures outgoing webhooks, notification connectors/routers/presets, and installs integrations and extensions.") to lift specificity and completeness.

Remove or narrow the "organize dashboards" trigger, which conflicts with the cx-dashboards skill, and scope "set up monitoring" toward notification/observability-stack setup to reduce collision with cx-alerts/cx-slos.

DimensionReasoningScore

Specificity

Many concrete actions are named ("create saved view", "configure webhook", "set up Slack integration", "configure PagerDuty", "deploy extension"), but only as quoted user trigger phrases — there is no direct capability statement, and coverage of routers and automation actions is reduced to single phrases like "notification routing" and "webhook actions".

4 / 5

Completeness

The "when" is maximally explicit ("Use this skill when the user asks to … or wants to set up, configure, or manage the observability stack for a service or team"), and a "what" exists ("set up, configure, or manage the observability stack"), but the stack's components are only implied through trigger quotes rather than stated as capabilities, falling just short of the anchor-5 example.

4 / 5

Trigger Term Quality

The description is dominated by natural phrases users would actually say ("set up monitoring", "onboard new service", "set up email alerts", "test webhook") with strong synonym coverage across variations ("create view"/"saved view"/"view folder"; "set up notifications"/"test notification"/"notification preset"), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Niche terms like "saved view", "outgoing webhook", "notification connector", and "contextual data" carve a clear niche, but "organize dashboards" overlaps the cx-dashboards skill referenced in the body and "set up monitoring" is broad enough to collide with alerting/SLO skills.

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coralogix/cx-cli

Path

skills/cx-observability-setup/SKILL.md

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.