Name: ixopay
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ixopay

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/ixopay/SKILL.md

Quality

Content

63%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 delivers strong, executable CLI guidance with a well-sequenced connection workflow and explicit state checks. It is held back by an unnecessary introductory explainer, an oversized inline entity list, and the absence of any external reference files for this length of skill.

Suggestions

Trim the opening 'IXOPAY is a payment orchestration platform...' paragraph or move it to a reference, since Claude does not need the platform explained.

Move the 37-item entity list into a references/ file (e.g. ENTITIES.md) and link to it from the overview to reduce token cost.

Fix the dangling step references (label 'Step 1'/'Step 2' consistently, or remove the '1b'/'Step 2' labels) so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI instructions, but the opening paragraph explaining what IXOPAY is and the 37-item inline entity list are padding that Claude did not need and could be trimmed or externalized.	3 / 5
Actionability	Provides concrete, copy-paste-ready bash commands for install, login, connection, action search/run, and proxying, with only minor gaps such as placeholder endpoints in the proxy example.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence with state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though step labels are inconsistent (a 'Step 2' and '1b' with no matching '1a'/'Step 1').	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives inline in one file with reasonable section headers, but the bulky entity enumeration and reference-style material would be better split into a separate file for a skill of this length.	3 / 5
	Total	14 / 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 states both what the skill does and when to use it, anchored to a distinct named platform. Its main weakness is generic action language that undersells IXOPAY's payment-specific capabilities and narrow trigger coverage.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with payment-specific ones, e.g. 'manage payments, refunds, settlements, and payouts'.

Broaden the 'Use when' clause with concrete triggers like 'when the user mentions IXOPAY, payment orchestration, PSP routing, or transaction reconciliation'.

Consider mentioning the API/docs context (e.g. 'interact with the IXOPAY API') to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (IXOPAY) and lists several actions ('Manage data, records, and automate workflows'), but the actions are generic rather than specific to payment orchestration capabilities like refunds, settlements, or routing.	3 / 5
Completeness	Answers both 'what' ('IXOPAY integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with IXOPAY data.'), though the 'when' trigger is somewhat narrow.	4 / 5
Trigger Term Quality	Includes the natural product keyword 'IXOPAY' and 'IXOPAY data', but misses common variations, synonyms, or concrete payment-domain phrases a user might say.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named platform (IXOPAY) giving it a clear niche, but the generic 'manage data, records, and automate workflows' phrasing creates minor overlap risk with general data-management skills.	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/ixopay/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.