Name: rafay-systems
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

rafay-systems

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

Quality

66%

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/rafay-systems/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 concrete, executable Membrane CLI integration guide with a well-sequenced, state-checked connection workflow and tidy section structure. Its main weakness is mild verbosity and conversational padding rather than technical gaps.

Suggestions

Trim explanatory padding (e.g., 'so you can focus on the integration logic rather than auth plumbing') to respect the token budget.

Tighten the clientAction field list into a compact table or move it to a reference file to reduce inline reference bulk.

Add a short error-recovery note for CONFIGURATION_ERROR/SETUP_FAILED states to complete the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes conversational padding ('so you can focus on the integration logic rather than auth plumbing') and restated explanations that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready bash commands throughout (install, login, connection ensure/get, action list/run, request) plus a flags table, with only minor gaps such as placeholder CONNECTION_ID handling.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced (ensure -> poll --wait -> branch on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with state-based checkpoints and a retry loop after user action, though error-recovery detail is thin.	4 / 5
Progressive Disclosure	Well-organized into clear sections with all content at one level and no nested references; no bundle files exist, and the inline reference-style material (clientAction fields, proxy flags table) is reasonably placed though could optionally be split out.	4 / 5
	Total	15 / 20 Passed

Description

66%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 is in third person, names a clear niche, and includes an explicit 'Use when' trigger, satisfying the completeness floor. It is held back by somewhat generic action verbs and limited trigger-term variety.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Rafay-specific capabilities (e.g., 'provision clusters, deploy addons, run workflows') to lift specificity.

Add natural trigger synonyms or scenarios (e.g., 'Use when managing Rafay clusters, blueprints, or workflows') to broaden trigger-term coverage.

Mention key Rafay resource types the skill covers (clusters, blueprints, workflows) so the 'when' clause signals concrete use cases.

Dimension	Reasoning	Score
Specificity	Names the Rafay Systems domain plus two to three actions ('Manage data, records, and automate workflows'), but 'manage data, records' is generic and coverage of the platform's real capabilities is not comprehensive.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'when' clause are present; the 'when' is concrete enough to exceed the 3 cap though it could be more specific about trigger scenarios.	4 / 5
Trigger Term Quality	Includes the explicit trigger phrase 'Use when the user wants to interact with Rafay Systems data' and the natural term 'Rafay Systems', but lacks synonyms or varied phrasings users might actually say.	3 / 5
Distinctiveness Conflict Risk	Targets a clear, named niche ('Rafay Systems integration') with distinct triggers, giving it minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/rafay-systems/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.