Name: equensworldline
Rating: 62.4 (1 reviews)
Author: membranedev

equensworldline

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

82%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 throughout and a clear, checkpointed connection workflow, supported by clean section organization. Its main weaknesses are minor padding in the introductory prose and slightly inconsistent step numbering that muddies the 'Step 2' references.

Suggestions

Trim the opening company-background paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Label the 'Searching for actions' section as 'Step 2' (or remove the 'skip to Step 2' references) so the workflow numbering is internally consistent.

Consider moving the proxy flags table and clientAction state-machine detail into a referenced file to improve progressive disclosure for this 150-line skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, dominated by copy-paste commands, a flags table, and a tight state-machine breakdown, with only minor over-explanation such as the opening company-background paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing'.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure, action list/run with JSON input, proxy requests) plus a concrete flags table, matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The install → login → connect → wait → search → run sequence is clear with explicit state-checking checkpoints and a poll-again feedback loop for CLIENT_ACTION_REQUIRED, but 'skip to Step 2' references point to an unlabeled step and numbering is inconsistent ('1b' with no 'Step 2' heading), leaving minor gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly headed sections (install, auth, connecting, searching, actions, proxy, best practices) with no nested references, though some inline material like the proxy flags table and clientAction state machine could justify a separate reference file.	4 / 5
	Total	17 / 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 correctly pairs a 'what' and a 'when' clause around a distinctive named product, but its action verbs are generic and the trigger offers no synonyms beyond the brand name. Tightening the action list and adding concrete trigger phrases would lift the weaker dimensions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete capabilities such as 'query transactions, fetch reports, and run payment workflows'.

Expand the 'Use when' clause with concrete trigger phrases like 'when the user mentions EquensWorldline payments, transactions, or merchant reports'.

Dimension	Reasoning	Score
Specificity	Names the domain ('EquensWorldline integration') and enumerates a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete like 'extract' or 'fill', matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It explicitly answers both 'what' ('EquensWorldline integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with EquensWorldline data.'), but the 'when' clause is generic rather than listing concrete triggers, matching the anchor where both are present yet 'when' could be more specific.	4 / 5
Trigger Term Quality	The trigger relies on the single brand keyword 'EquensWorldline' in 'Use when the user wants to interact with EquensWorldline data', which is relevant but lacks synonyms or natural variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product 'EquensWorldline' with a brand-specific trigger gives it a clear niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.	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/equensworldline/SKILL.md
Commit: f484c82

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