Name: citrix
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

citrix

Citrix integration. Manage data, records, and automate workflows. Use when the user wants to interact with Citrix data.

Quality

65%

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/citrix/SKILL.md

Quality

Content

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

The body is a strong, executable command reference with a well-sequenced, state-aware connection workflow and feedback loops. Weaknesses are padding (the Citrix background sentence and empty Overview bullets) and the hollow 'Popular actions' section that promises more than it delivers.

Suggestions

Cut the 'Citrix provides virtualization...' opener and the empty 'Citrix Overview' bullet placeholders, or fill each 'Details' entry with one concrete action.

Populate 'Popular actions' with 3-5 named high-value Citrix actions (e.g., list sessions, get delivery group) instead of only restating the discovery command.

Add a short numbered master workflow (connect → search actions → run / proxy) at the top to make the end-to-end sequence explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but the 'Citrix provides virtualization, networking...' opener and the 'Citrix Overview' section with empty 'Details' bullets ('App Details', 'Desktop Details') plus filler like 'Use action names and parameters as needed.' are unnecessary padding, matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (install, login, connection ensure, action list/run, request) with a full proxy flag table, but the 'Popular actions' heading promises named actions and delivers only a discovery command, a minor gap against the fully-executable anchor.	4 / 5
Workflow Clarity	The 'Connecting to Citrix' flow is a clear state-driven sequence with explicit checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but there is no top-level numbered master workflow tying connect→search→run together, leaving a minor gap versus the explicit-checklist anchor.	4 / 5
Progressive Disclosure	Content is a single well-organized file with clear headers and no external references (and none needed), giving good structure and easy navigation; the placeholder 'Citrix Overview' list is a minor organization gap against the ideally-structured anchor.	4 / 5
	Total	15 / 20 Passed

Description

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

The description cleanly identifies a distinct Citrix niche and includes an explicit 'Use when' trigger, satisfying both what and when. It is held back by generic action verbs ('manage', 'automate') instead of concrete capabilities and limited keyword variation.

Suggestions

Replace generic verbs with concrete Citrix operations (e.g., 'manage delivery groups, machines, sessions, and catalogs') to lift specificity.

Add natural trigger variations and synonyms users might say (e.g., 'Citrix DaaS', 'Citrix Virtual Apps and Desktops', 'brokered sessions').

Tighten the 'what' clause so capabilities read as specific actions rather than abstract 'manage data' phrasing.

Dimension	Reasoning	Score
Specificity	Names the Citrix domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete operations like 'extract' or 'fill', matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Citrix data') are present; the trigger is explicit but the 'what' is somewhat generic, fitting the anchor where both exist yet could be more specific.	4 / 5
Trigger Term Quality	'Citrix' and 'interact with Citrix data' are relevant keywords, but coverage is essentially a single domain term missing common variations or synonyms, fitting the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	'Citrix integration' is a clear, distinct niche with a specific trigger unlikely to fire for unrelated skills, but the generic action verbs slightly dilute distinctiveness versus the clearest-niche anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/citrix/SKILL.md
Commit: f484c82

Reviewed: ~9 hours 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.