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

paystack

Paystack integration. Manage Customers, Transactions, Plans, Products, Splits. Use when the user wants to interact with Paystack data.

Quality

73%

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

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.

A highly actionable integration skill with copy-paste CLI commands and a solid connection workflow. It loses points for an unnecessary introductory explainer and, more importantly, for missing validation checkpoints around destructive action/proxy operations.

Suggestions

Trim the opening Paystack explainer and marketing-style phrasing; assume Claude knows what a payments platform is.

Add an explicit validation/verification step after `membrane action run` and proxy requests (e.g. check the `output`/error fields, confirm idempotency before destructive POST/PUT/DELETE, retry or surface `error` on failure) to lift workflow clarity above the destructive-operation cap.

Either populate the "Popular actions" section with concrete examples or fold it into action discovery, and fix the "Subcriptions" typo / stray "MISCELLANEOUS" entry in the overview list.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and a flag table, but it opens by explaining what Paystack is ("Paystack is a payments platform that enables businesses to accept online payments...") and includes padded phrases like "so you can focus on the integration logic rather than auth plumbing", which the rubric penalizes as concepts Claude already knows.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a complete flag table — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The connection sequence is clearly ordered with state-based feedback loops (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, re-poll after action), but running actions and proxy requests can perform destructive POST/PUT/DELETE operations with no validation of the result beyond "The result is in the `output` field", which caps workflow clarity at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but it is organized into clear well-signaled sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with the external docs link clearly surfaced — good structure with only minor gaps such as a thin "Popular actions" section.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A strong, third-person description that pairs a concrete capability list with an explicit activation clause for a clearly distinct platform. The main weakness is a generic "Manage" verb and a trigger clause that could cite more specific user phrases.

Suggestions

Vary the verb beyond "Manage" — e.g. "Create and list Customers, verify Transactions, manage Plans and Products, configure Splits" — to show concrete actions.

Expand the "Use when..." clause with natural trigger phrases such as "when the user mentions Paystack payments, charges, refunds, or wants to query Paystack data".

Dimension	Reasoning	Score
Specificity	"Manage Customers, Transactions, Plans, Products, Splits" names the domain and lists several concrete capability areas, but reuses the single generic verb "Manage" rather than enumerating distinct actions, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	It has both a clear "what" ("Manage Customers, Transactions, Plans, Products, Splits") and an explicit "when" ("Use when the user wants to interact with Paystack data"), but the trigger clause is generic rather than packed with concrete trigger phrases, matching the anchor where 'when' could be more specific.	4 / 5
Trigger Term Quality	"Paystack" and "interact with Paystack data" plus the entity list give good natural keyword coverage, but a few common synonyms a user might say (payments, charges, refunds) are absent, so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Paystack integration" targets a specific named payments platform with distinct triggers, making overlap with other skills minimal and the niche clear.	5 / 5
	Total	17 / 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/paystack/SKILL.md
Commit: f484c82

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