CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cx-rum-setup

Use this skill when the user asks to "add RUM", "set up RUM", "install the RUM SDK", "add Coralogix RUM to my app", "create a RUM API key", "RUM public key", "init Coralogix RUM", "CoralogixRum.init", "add the browser SDK", "real user monitoring", "frontend monitoring", "monitor my web app", "session replay", "track frontend errors", "add RUM to React", "add RUM to Next.js", "add RUM to my mobile app", or wants to instrument a browser or mobile application with Coralogix Real User Monitoring end to end - RUM API key, SDK install, init code, and verifying data arrives.

Quality

98%

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

100%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 high-quality operational skill body: it is token-efficient, gives copy-paste-ready commands and code, sequences the workflow with explicit checkpoints and error-recovery loops, and handles volatile platform specifics via live doc fetching instead of inlining. No bundle files are needed and the structure is easy to navigate.

DimensionReasoningScore

Conciseness

The body is lean and operational - CLI command tables, gotchas, and exact payloads with zero explanation of concepts Claude already knows; every section conveys non-obvious domain knowledge (preset semantics, permission-error mapping, hashed-key caveat) and the Key Principles recap is a distillation rather than padding.

5 / 5

Actionability

Fully executable throughout: copy-paste commands with exact flags (`cx iam api-keys list -p <profile> -o json`), a complete JSON key-creation payload, a runnable init example, and a concrete verification query; deferring other platforms' install snippets to `cx docs` is explicitly justified ("SDK package names, versions, and options change - fetch them instead of guessing").

5 / 5

Workflow Clarity

Six clearly sequenced steps with explicit ordering constraints ("Pick the profile - before any key operation", platform detection "stop at the first match"), an approval checkpoint before the write (`--yes` only after user approval), a verification step, and error-recovery feedback loops ("No rows? Check the browser network tab..." plus the `Permission denied` triage paths), matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: the skill keeps volatile per-platform SDK details out of the body by deferring to the external `cx docs` commands, points to related skills by name, and organizes everything into clean, navigable sections, fitting the well-organized no-external-references pattern.

5 / 5

Total

20

/

20

Passed

Description

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

An excellent description: it explicitly states what the skill does end to end, provides a rich set of natural trigger phrases including platform variations, and stays lean with no fluff. The only minor weakness is a handful of vendor-neutral phrases that could collide with other frontend-monitoring skills.

DimensionReasoningScore

Specificity

The description names multiple concrete, end-to-end actions - "RUM API key, SDK install, init code, and verifying data arrives" - with comprehensive coverage of the whole onboarding flow, matching the top anchor rather than the 'minor gaps' level 4 anchor.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' ("instrument a browser or mobile application with Coralogix Real User Monitoring end to end - RUM API key, SDK install, init code, and verifying data arrives") and the 'when' ("Use this skill when the user asks to..." with concrete quoted trigger phrases), exactly matching the top anchor.

5 / 5

Trigger Term Quality

Extensive natural phrases users would actually say ("add RUM", "set up RUM", "create a RUM API key", "real user monitoring", "session replay", "track frontend errors") plus framework and platform synonyms (React, Next.js, mobile, browser SDK), giving comprehensive coverage with no natural terms missing.

5 / 5

Distinctiveness Conflict Risk

Mostly distinct with a clear Coralogix RUM niche, but several trigger phrases are vendor-agnostic ("frontend monitoring", "monitor my web app", "session replay", "track frontend errors") and could overlap with a sibling frontend-monitoring skill; this fits 'mostly distinct; minor overlap risk' better than the minimal-conflict level 5 anchor.

4 / 5

Total

19

/

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-rum-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.