Name: xeditor
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

xeditor

Xeditor integration. Manage data, records, and automate workflows. Use when the user wants to interact with Xeditor 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/xeditor/SKILL.md

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.

The content is highly actionable with comprehensive, executable Membrane CLI commands and a well-structured connection workflow including polling checkpoints. Its main weaknesses are minor redundancy and inlined reference material that could be progressively disclosed.

Suggestions

De-duplicate the 'action list' command between the 'Searching for actions' and 'Popular actions' sections, keeping a single canonical form.

Replace or trim the informational 'Xeditor Overview' bullet list so the body leads with action-oriented content.

Add a concrete recovery step for CONFIGURATION_ERROR / SETUP_FAILED states beyond 'check the error field', e.g. re-run 'membrane connection ensure' or surface the error to the user.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the 'action list' invocation is shown twice in slightly different forms and the decorative 'Xeditor Overview' bullet list adds little actionable value.	3 / 5
Actionability	It provides fully copy-paste-ready commands covering install, login (including headless), connect with polling, action search, action run with JSON input, and proxy requests plus a flags table.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with polling checkpoints and a state-based feedback loop (READY / CLIENT_ACTION_REQUIRED -> re-poll), but CONFIGURATION_ERROR recovery is left as a vague 'check the error field'.	4 / 5
Progressive Disclosure	Sections are well-organized and the single inline file is mostly appropriate for a CLI guide, though at over 150 lines reference material such as the clientAction schema and flags table is inlined rather than split out.	4 / 5
	Total	16 / 20 Passed

Description

57%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 adequately complete with an explicit 'Use when' trigger, but its action language is generic rather than specific to Xeditor's structured-content domain. Trigger coverage relies almost entirely on the product name with no synonyms.

Suggestions

Replace generic verbs with Xeditor-specific actions, e.g. 'Edit XML documents, manage sections, and apply templates in Xeditor'.

Add natural trigger synonyms beyond the product name, such as 'structured content', 'XML documents', or 'publishing workflows'.

Tighten the 'Use when' clause to concrete scenarios, e.g. 'Use when the user wants to edit or manage Xeditor XML documents and records.'

Dimension	Reasoning	Score
Specificity	It names the domain (Xeditor) but the actions 'Manage data, records, and automate workflows' are generic and apply to almost any data app rather than concrete Xeditor-specific operations.	2 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Xeditor data' trigger, though the when clause could be more specific.	4 / 5
Trigger Term Quality	'Xeditor' is the natural product-name keyword a user would say, but the description offers no synonyms or variations such as 'XML', 'structured content', or 'documents'.	3 / 5
Distinctiveness Conflict Risk	The 'Xeditor' product name is a distinctive trigger with low conflict risk, but the generic 'manage data' phrasing leaves minor overlap with other integration skills.	4 / 5
	Total	13 / 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/xeditor/SKILL.md
Commit: f484c82

Reviewed: 3 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.