CtrlK
BlogDocsLog inGet started
Tessl Logo

payfast

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

52

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

61%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 concrete executable membrane commands and a solid connection workflow, but it is padded with editorializing and lacks validation/verification steps for the destructive payment operations at its core.

Suggestions

Add verification guidance after running actions or proxy requests, especially for destructive operations like creating charges, issuing payouts, or deleting records.

Trim editorializing sentences (e.g. the Stripe/PayPal analogy, 'fastest way to get a connection', 'burn less tokens') that do not add executable value.

Resolve the dangling 'skip to Step 2' reference by labeling the subsequent sections as numbered steps or removing the cross-reference.

DimensionReasoningScore

Conciseness

The body is mostly efficient command examples, but includes unnecessary editorializing such as the PayFast overview analogy, 'so you can focus on the integration logic rather than auth plumbing', and 'This is the fastest way to get a connection' that could be trimmed.

3 / 5

Actionability

It provides concrete, executable membrane commands throughout plus a thorough proxy options table; minor gaps are the placeholder values (CONNECTION_ID, <actionId>) and the absence of a complete end-to-end PayFast-specific action example.

4 / 5

Workflow Clarity

The connection setup has a clear sequence with a state-polling feedback loop, but the core data-manipulation workflows (running actions, proxy requests) lack validation/verification steps, and the destructive-payment cap applies; a 'skip to Step 2' reference also points to no labeled Step 2.

3 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clear, navigable sections; minor gaps include inline detail (e.g. clientAction handling, proxy options) that could be split out and an unlabeled 'Step 2' reference.

4 / 5

Total

14

/

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 correctly identifies a distinct niche (PayFast) with an explicit 'Use when' trigger, but its capability phrasing is generic and lacks concrete PayFast-specific actions and natural trigger synonyms.

Suggestions

Replace generic verbs with concrete PayFast actions, e.g. 'Process payments, manage subscriptions, issue payouts, and automate workflows'.

Expand trigger terms to include natural phrases a user would say, such as 'payments', 'transactions', 'subscriptions', or 'payouts'.

Tighten the 'when' clause with concrete triggers, e.g. 'Use when the user wants to process PayFast payments, manage subscriptions, or query transaction data.'

DimensionReasoningScore

Specificity

The description names the PayFast domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete PayFast capabilities like processing payments, managing subscriptions, or issuing payouts.

2 / 5

Completeness

It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with PayFast data' trigger, but the 'when' could be more specific with concrete trigger phrases.

4 / 5

Trigger Term Quality

It includes the natural keyword 'PayFast' and 'PayFast data', but misses common variations and synonyms a user might say such as payments, transactions, subscriptions, payouts, or payment gateway.

3 / 5

Distinctiveness Conflict Risk

PayFast is a distinct niche with a brand-specific trigger that minimizes conflict risk, though the generic action phrasing ('manage data, records, automate workflows') creates minor overlap risk with similar integration skills.

4 / 5

Total

13

/

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.