CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cx-platform-admin

Use this skill when the user asks "who has access", "audit permissions", "check user roles", "list API keys", "review access controls", "rotate API keys", "create API key", "RUM API key", "delete expired keys", "send data keys", "IP allowlist", "IP access restrictions", "check IP whitelist", "add user", "deactivate user", "manage team groups", "user permissions", "role-based access", "manage scopes", "system roles", "API key admin", "team member keys", "group membership", or wants to audit, manage, or configure access controls for a Coralogix account.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cx-platform-admin/SKILL.md
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 highly actionable CLI skill with well-structured command tables, safety-conscious destructive-operation gating, and explicit verification in the rotation workflow. The main gaps are the undocumented --from-file payload formats for all write operations and minor redundancy in the safety messaging.

Suggestions

Add a short example payload (or a references/key-role-templates.md file) showing the JSON format expected by --from-file for api-keys, roles, and users create/update.

Add an error-recovery branch to key rotation (e.g. "If verification fails, keep the old key active and re-check the new key's presets/roles") to close the feedback loop.

Consolidate the thrice-repeated delete-key warning into the Safety Callouts section and reference it from the rotation workflow to trim redundancy.

DimensionReasoningScore

Conciseness

Mostly lean command tables and executable jq pipelines with no concept over-explanation; the body assumes Claude's competence. Minor tightening possible: the "deleting API keys breaks integrations" warning appears three times (rotation WARNING, Safety Callouts, Key Principles) and confirmation-gating is restated in both the safety section and workflow step annotations.

4 / 5

Actionability

Concrete, copy-paste-ready commands throughout ("cx iam users search -o json | jq '[.[] | {id, name: .user_name, status, role_ids}]'") covering audit and rotation end-to-end. Held below 5 because every create/update operation uses "--from-file" without ever showing a payload file example — only the indirect "Template from existing" hint is given.

4 / 5

Workflow Clarity

The audit workflow is a clear 6-step sequence and key rotation includes explicit validation (deploy → "Verify the new key works" → delete old) plus interactive confirmation gates, so the destructive-operation cap does not apply. Missing error-recovery branches (e.g. what to do when verification fails) and a vague Step 6 ("Produce a summary") keep it below 5.

4 / 5

Progressive Disclosure

Well-organized single file: clear section headers, scannable command tables, and Related Skills pointers, with no bundle files to reference. At ~190 lines the --from-file payload schemas and detailed IAM reference material would justify a separate references file, which keeps it below 5; the inline command tables are appropriately placed core content, above the anchor-3 case of inlined API reference.

4 / 5

Total

16

/

20

Passed

Description

73%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-rich description with excellent natural keyword coverage and a well-defined Coralogix IAM niche. Its main weakness is the absence of an explicit capability statement — the "what" is only implied through the trigger list and a generic closing clause.

Suggestions

Lead with an explicit capability statement before the trigger list, e.g. "Manages Coralogix IAM — API keys, users, roles, scopes, team groups, and IP access restrictions — via the cx CLI."

Reconsider claiming "RUM API key" as a trigger, or explicitly scope it (e.g. "listing RUM/send-data keys") since the body delegates RUM key creation to the cx-rum-setup skill.

Add a couple of missing natural variations such as "access review" or "remove user access" to round out trigger coverage.

DimensionReasoningScore

Specificity

Trigger phrases name many concrete actions ("rotate API keys", "create API key", "add user", "deactivate user", "manage team groups", "manage scopes"), giving several specific actions with minor gaps. It falls short of 5 because the only explicit capability statement is the generic "audit, manage, or configure access controls for a Coralogix account".

4 / 5

Completeness

The "when" is maximally explicit ("Use this skill when the user asks..." with a long trigger list), but the "what" is never stated as a capability — it appears only as the when-condition "wants to audit, manage, or configure access controls for a Coralogix account", which is generic. It cannot reach 4 without an explicit capability statement, but the enumerated operations convey scope well above the anchor-2 example "Use when working with documents".

3 / 5

Trigger Term Quality

Comprehensive natural-language triggers including synonyms and variations: "who has access", "audit permissions", "review access controls", "IP allowlist" alongside "check IP whitelist", "role-based access", "team member keys", "group membership". These are exactly the phrases a user would naturally say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Clearly niche (Coralogix IAM: API keys, scopes, team groups, IP access restrictions) with distinct triggers and minimal conflict risk. The one overlap: "RUM API key" is claimed as a trigger while the body routes RUM key work to the separate cx-rum-setup skill, creating minor conflict risk with that closely related skill.

4 / 5

Total

16

/

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-platform-admin/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.