Name: paymob
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

paymob

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

Quality

68%

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

Quality

Content

75%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 concrete, executable Membrane CLI commands and a well-structured connection workflow with state feedback loops. Its main weaknesses are a redundant action-discovery section and minor sequencing/labeling gaps rather than any structural problem.

Suggestions

Merge the 'Searching for actions' and 'Popular actions' sections, which both demonstrate `membrane action list` with slightly different syntax, to remove redundancy.

Label the 'Step 2' target explicitly (e.g. '## Step 2: Discover and run actions') so the cross-reference from the connection section resolves.

Add a brief validation note for `membrane action run` output (check the `output`/`error` field before reporting success), since payment actions can be consequential.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but includes redundant action-discovery sections ('Searching for actions' vs 'Popular actions') and mild fluff like 'so you can focus on the integration logic rather than auth plumbing', fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready `membrane` commands covering the common cases (install, login, connection ensure, action list/run, request proxy) plus a flags table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connect→poll→state sequence is clearly laid out with explicit feedback loops for READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, but 'Step 2' is referenced without a labeled header and running actions lacks success/error validation, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Content is organized into clear sections with no external references needed, but at ~140 lines it exceeds the simple-skill (<50 line) exception and has minor organization gaps (redundant action-list sections), fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

61%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 'Use when' trigger with a named domain, but the capability list is generic fluff ('manage data, records') rather than concrete Paymob actions. Distinctiveness is strong thanks to the unique Paymob proper noun.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Paymob capabilities (e.g. 'Create and capture payments, manage customers and PaymentIntents, refund transactions, automate workflows').

Expand trigger terms with natural variations users might say (e.g. 'Paymob payments, PaymentIntents, refunds, checkout').

Tighten the 'what' to mirror the entity list already in the body (PaymentIntents, Customers) so the description signals specific capabilities.

Dimension	Reasoning	Score
Specificity	The description names the Paymob domain but its actions ('Manage data, records, and automate workflows') are generic nouns and verbs rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Paymob data'), but the 'what' is generic so it does not reach the concrete-trigger anchor of 5.	4 / 5
Trigger Term Quality	'Paymob' is the natural keyword a user would say and appears in the trigger clause, but there are no synonyms, variations, or file/extension terms, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Paymob' is a unique proper-noun trigger tied to a specific payments gateway, giving a clear niche with minimal risk of triggering the wrong skill.	5 / 5
	Total	14 / 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/paymob/SKILL.md
Commit: f484c82

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