CtrlK
BlogDocsLog inGet started
Tessl Logo

worldline

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/worldline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 executable commands and good section structure, but it carries some over-explanation and its workflow has a dangling step reference plus no validation for destructive proxy calls.

Suggestions

Trim the conceptual intro and 'rather than auth plumbing' commentary so the body starts directly with the install/auth commands Claude needs.

Resolve the dangling 'skip to Step 2' reference by labeling the target section (e.g. '## Step 2: Search and run actions') or rewording the jump.

Add a validation/checkpoint note for destructive proxy requests (e.g. confirm before `-X DELETE`, verify the response status before proceeding).

DimensionReasoningScore

Conciseness

The body is mostly command-driven and efficient, but it opens by explaining what Worldline is, adds commentary like 'rather than auth plumbing', and duplicates the `action list` invocation across two sections.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands for install, login, connection, action search/run, and proxying, plus a thorough flags table covering the common cases.

5 / 5

Workflow Clarity

The connect flow has a clear sequence with state-polling feedback loops, but it references 'Step 2' with no labeled Step 2, and destructive proxy operations (e.g. DELETE) have no validation checkpoint, capping the score per the batch/destructive rule.

3 / 5

Progressive Disclosure

Content is well-organized into clear headed sections with appropriately inline CLI guidance and no bundle files to split out; minor gaps remain such as the unresolved 'Step 2' reference and the duplicated action-list instructions.

4 / 5

Total

15

/

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 both what and when and names a specific platform, but its action verbs are generic and it omits the natural payment-domain trigger terms a user would actually say.

Suggestions

Replace generic verbs with concrete payment actions, e.g. 'Process payments, issue refunds, and manage merchants and transactions.'

Add natural trigger keywords users would say, such as 'payments', 'transactions', 'refunds', or 'payouts', alongside 'Worldline'.

Sharpen the 'Use when' clause with concrete triggers, e.g. 'Use when the user wants to process Worldline payments, look up transactions, or automate payout workflows.'

DimensionReasoningScore

Specificity

Names the Worldline domain and several actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete payment-specific operations like processing payments or issuing refunds.

3 / 5

Completeness

Both 'what' (manage data/records/automate workflows) and 'when' ('Use when the user wants to interact with Worldline data') are present, but the when-clause is generic rather than listing concrete triggers.

4 / 5

Trigger Term Quality

The keyword 'Worldline' appears, but no payment-domain synonyms users would naturally say (payments, transactions, refunds, merchant) are included.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Worldline platform gives a clear niche with minimal conflict risk, though the generic 'manage data/records' actions leave minor overlap with other data skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.