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", "delete expired keys", "send data keys", "configure SAML", "set up SSO", "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.
79
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cx-platform-admin/SKILL.mdQuality
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage and distinctiveness by listing numerous natural user phrases and scoping to Coralogix access management. However, it lacks a clear 'what this skill does' statement — it reads entirely as a trigger list without describing the skill's concrete capabilities, outputs, or workflow. Adding a concise capability summary before the trigger phrases would significantly improve it.
Suggestions
Add a capability summary before the trigger list, e.g., 'Manages Coralogix access controls including user permissions, API key lifecycle management, SSO/SAML configuration, IP allowlisting, and team/group membership administration.'
Restructure to separate 'what it does' from 'when to use it' — lead with concrete actions (audits permissions, creates/rotates/deletes API keys, configures SAML/SSO, manages IP allowlists, adds/deactivates users) then follow with the trigger clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists many trigger phrases but doesn't clearly articulate concrete actions the skill performs. It mentions activities like 'audit permissions', 'rotate API keys', 'configure SAML', 'set up SSO' etc., but these are framed as user queries rather than explicit capability statements. There's no structured list of what the skill actually does (e.g., 'Audits user permissions, manages API key lifecycle, configures SSO/SAML settings'). | 2 / 3 |
Completeness | The 'when' is very well covered with explicit trigger phrases and a 'Use this skill when...' clause. However, the 'what does this do' is weak — there's no clear statement of the skill's capabilities or what it produces. It reads as a list of triggers without describing the skill's actual functionality or outputs. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say, including 'who has access', 'audit permissions', 'check user roles', 'list API keys', 'rotate API keys', 'configure SAML', 'set up SSO', 'IP allowlist', 'IP whitelist', 'add user', 'deactivate user', 'manage team groups', 'role-based access'. These are highly natural phrases covering many variations. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Coralogix account access management, including specific features like SAML, SSO, IP allowlists, API keys, and team/group management. The mention of 'Coralogix account' and the specific domain terms make it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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, actionable skill with excellent workflow clarity and concrete executable commands throughout. The safety-first approach with destructive operation warnings and the structured audit workflow are particularly well done. Minor improvements could come from trimming some redundant safety callouts and potentially splitting the extensive command reference into a separate file for better progressive disclosure.
Suggestions
Remove the duplicated safety warning about API key deletion (appears in both 'API Key Rotation' and 'Safety Callouts' sections) to improve conciseness.
Consider extracting the CLI command reference tables into a separate COMMANDS.md file, keeping only the most common commands inline, to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with well-structured tables and concrete commands, but includes some unnecessary explanation (e.g., the 'Agent Mode' paragraph explaining how cx detects agent environments, and the 'Key Principles' section restates things already covered). The safety callouts section partially duplicates the warning in the API Key Rotation section. Could be tightened by ~20%. | 2 / 3 |
Actionability | Fully concrete and executable: every command is copy-paste ready with exact CLI syntax, jq pipelines for filtering, and specific flags. The access audit workflow and key rotation workflow provide step-by-step executable guidance with real commands. | 3 / 3 |
Workflow Clarity | The access audit workflow is clearly sequenced (Steps 1-7) with specific commands at each step. The API key rotation workflow includes explicit validation checkpoints ('Verify the new key works') and a clear feedback loop (create → deploy → verify → delete). Safety warnings about destructive operations are prominent and well-placed. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a fairly long monolithic document (~180 lines of content). The command reference tables could potentially be split into a separate reference file. There's only one cross-reference (to cx-cost-optimization) and no bundle files to offload detail into. However, for a CLI reference skill, inline tables are reasonable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
defdc4d
Table of Contents
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.