Name: xebialabs
Rating: 59.2 (1 reviews)
Author: membranedev

xebialabs

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

Quality

68%

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/xebialabs/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 body is highly actionable with executable commands and a well-sequenced, validated connection workflow. Minor conciseness padding and inconsistent step numbering, plus optional externalization of reference detail, keep it from the top band.

Suggestions

Remove the duplicated action-list command in 'Popular actions' (already shown under 'Searching for actions') and trim the introductory 'what XebiaLabs is' paragraph.

Fix the step numbering so 'Step 2' is explicitly titled and the '1b' wait step is renumbered consistently within the connection flow.

Consider moving the full flags table and clientAction schema into a references/ file and linking to it from the main flow to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening 'what XebiaLabs is' paragraph and the repeated action-list command (shown in both 'Searching for actions' and 'Popular actions') could be tightened, matching the score-3 anchor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands (login, connection ensure, action list/run, request) with a flags table and JSON-input examples covering common cases.	5 / 5
Workflow Clarity	The connection flow is sequenced with state-check validation checkpoints and a re-poll feedback loop, but numbering is inconsistent (a '1b' step and an untitled 'Step 2' reference), leaving minor gaps from the score-5 anchor.	4 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and no nested references; the detailed clientAction schema and flags table could live in a reference file, a minor organization gap from a score of 5.	4 / 5
	Total	16 / 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 covers what and when with an explicit trigger clause, but its action verbs are generic and trigger-term coverage is narrow. Tightening the capabilities and adding synonyms would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('manage data, records') with concrete XebiaLabs actions such as 'orchestrate releases, trigger tasks, and inspect pipeline status'.

Add natural trigger synonyms users say, e.g. 'release orchestration', 'XL Release', 'Deployit', or 'deployment pipelines'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to run or monitor XebiaLabs release tasks and pipelines.'

Dimension	Reasoning	Score
Specificity	Names the XebiaLabs domain and 2-3 actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete and comprehensive, matching the score-3 anchor.	3 / 5
Completeness	It answers both 'what' (manage data/records/workflows) and 'when' (explicit 'Use when the user wants to interact with XebiaLabs data'), though neither side is highly specific, fitting the score-4 anchor.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with XebiaLabs data' surfaces the natural term 'XebiaLabs', but misses common variations and synonyms like release, deployment, XL Release, or Deployit.	3 / 5
Distinctiveness Conflict Risk	'XebiaLabs integration' is a clearly named niche with minimal conflict risk, but the generic action phrasing prevents a score of 5.	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/xebialabs/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.