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

Blog Docs Log in Get started

sofort

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

Quality

62%

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/sofort/SKILL.md

Quality

Content

67%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 well-structured and highly actionable with executable CLI commands and a state-machine connection workflow including a feedback loop, held back mainly by an unnecessary introductory explainer and slightly loose step numbering.

Suggestions

Trim or remove the opening SOFORT explainer paragraph; Claude already knows what SOFORT is, so lead with the integration steps instead.

Fix the step numbering (label the connect step '1a' and the wait step '1b', and explicitly label 'Step 2' for action discovery) so the sequence reads as a coherent ordered workflow.

Add a validation checkpoint before running payment/refund actions (e.g. confirm the action's inputSchema and intended effect before executing) given these are potentially irreversible financial operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens with a four-line explanation of what SOFORT is ('SOFORT is a direct online banking payment method popular in Germany...') and contains light filler ('so you can focus on the integration logic rather than auth plumbing'), matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, connection get --wait, action list/run, request) plus a flag table, but examples rely on unfilled placeholders (CONNECTION_ID, QUERY, <actionId>) with no fully concrete end-to-end run, fitting the 'mostly executable; minor gaps' anchor rather than copy-paste-ready 5.	4 / 5
Workflow Clarity	The connect-to-READY workflow is clearly sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and an explicit poll-after-user-action feedback loop, but the step numbering is loose ('1b' with no '1a', unlabeled 'Step 2') and there is no validation gate before running payment/refund actions.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but the body is well-organized into clearly headed sections (Overview, Working with SOFORT, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with minor organization gaps, fitting the 'good structure; most content appropriately placed' anchor.	4 / 5
	Total	15 / 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 covers both capability and trigger and is anchored to a distinctive brand niche, but its action language is generic and omits SOFORT's actual payment/transaction functionality, capping specificity and trigger-term quality.

Suggestions

Replace generic verbs with SOFORT-specific actions, e.g. 'Initiate SOFORT payments, retrieve transaction status, and issue refunds.'

Add concrete payment-domain trigger terms users naturally say, such as 'payment', 'transaction', 'bank transfer', and 'refund', to the 'Use when...' clause.

Tighten the 'when' clause to reference the actual trigger scenarios, e.g. 'Use when the user wants to start or check a SOFORT payment or issue a refund.'

Dimension	Reasoning	Score
Specificity	Names the SOFORT domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and omit SOFORT's actual payment capabilities (transactions, refunds), matching the 'actions are minimal or generic' anchor rather than the concrete-actions anchor at 3.	2 / 5
Completeness	States both what it does ('SOFORT integration. Manage data, records, and automate workflows.') and when to use it ('Use when the user wants to interact with SOFORT data.'), with the 'when' explicit but somewhat generic — matching the 'has both what and when; when could be more specific' anchor rather than the concrete-trigger-phrases anchor at 5.	4 / 5
Trigger Term Quality	Includes the natural brand keyword 'SOFORT' and a trigger ('interact with SOFORT data'), but is missing common payment-domain terms a user would actually say (payment, transaction, bank transfer, refund), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'SOFORT integration' niche and SOFORT-branded trigger give it a clear, distinct identity with minimal conflict risk, though the generic 'Manage data, records, and automate workflows' phrasing creates minor overlap with general CRM-style 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/sofort/SKILL.md
Commit: f484c82

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