Name: payumoney
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

payumoney

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

Quality

66%

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

Quality

Content

76%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 a strong, action-dense integration guide: overwhelmingly concrete executable CLI commands with clean sectioning and a useful polling feedback loop. Its main weakness is workflow safety — destructive financial operations (refunds, payouts) run without explicit validation or user-confirmation checkpoints — plus a dangling 'Step 2' reference.

Suggestions

Add an explicit validation/confirmation step before executing financial or destructive actions, e.g. 'Before running refund or payout actions, show the user the resolved inputSchema and confirm; payments and refunds are irreversible.'

Fix the undefined 'Step 2' reference by numbering the connection workflow steps explicitly (1. Install, 2. Authenticate, 3. Connect, ...) so 'skip to Step 2' resolves.

Tighten the opening paragraph and editorial sentences ('so you can focus on the integration logic rather than auth plumbing') to lift conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is dominated by concrete commands and a flags table with only minor editorial padding ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and a light introductory explanation of what PayUmoney is. It is efficient with minor instances of over-explanation; not a 5 because the opening paragraph and a few editorial sentences could be trimmed.	4 / 5
Actionability	The body is built from fully executable, copy-paste-ready commands (install, login, connection ensure/get --wait, action list/run, request proxy) plus a concrete flags reference table, covering the common cases end to end. Placeholders like CONNECTION_ID and <actionId> are necessary and clearly meant to be filled, so this meets the 'fully executable; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	A clear sequence exists (install -> authenticate -> connection ensure -> poll --wait -> handle READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR -> search actions -> run/proxy) with a poll-until-READY feedback loop, but there are no validation/confirmation checkpoints before running destructive financial operations (refunds, payouts), which caps workflow clarity at 3. A referenced 'Step 2' is also never defined, leaving a sequencing gap.	3 / 5
Progressive Disclosure	The single-file body is well-structured with a clear header hierarchy (Overview, Working with PayUmoney, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) and no nested or buried references, making navigation easy. It is not a 5 because no one-level-deep external references are used (none are strictly needed) and the 'Popular actions' / Overview sections are thin, leaving minor organization gaps.	4 / 5
	Total	16 / 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 has an explicit what-and-when structure anchored to a distinctive named service, but its action language is generic fluff ('manage data, records, and automate workflows') and trigger coverage is limited to the single term 'PayUmoney'. It is clearly above baseline but falls short of the concrete, keyword-rich examples.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete PayUmoney operations, e.g. 'Issue refunds, send payout links, and view settlements via the PayUmoney API.'

Add natural trigger terms and synonyms users would actually say — 'refunds', 'payout links', 'settlements', 'payment gateway', 'PayU' — to the 'Use when' clause.

Make the 'when' clause specific rather than circular, e.g. 'Use when the user wants to process refunds, generate payout links, or check settlements on PayUmoney.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('PayUmoney integration') but its actions are generic and abstract — 'Manage data, records, and automate workflows' names no concrete PayUmoney operations (e.g. refunds, payouts, settlements). It sits at the 'names the domain but actions are minimal or generic' anchor and is not a 3 because it lacks 1-2 concrete actions like 'Processes PDF files and extracts content'.	2 / 5
Completeness	Both 'what' (PayUmoney integration; manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with PayUmoney data') are explicitly present, and an explicit 'Use when' clause avoids the cap at 3. It is not a 5 because the 'what' is vague and the 'when' is circular/generic rather than using concrete trigger phrases.	4 / 5
Trigger Term Quality	'PayUmoney' is a relevant natural keyword, but no synonyms or related natural phrases (refunds, settlements, payout links, payment gateway, PayU) are included, and 'interact with PayUmoney data' restates the domain. This matches 'some relevant keywords but missing common variations or synonyms'; not a 4 because coverage is essentially a single keyword.	3 / 5
Distinctiveness Conflict Risk	PayUmoney is a specific named service with a distinctive trigger term, giving low conflict risk; the only overlap is with closely related payment-gateway skills. Not a 5 because the generic 'manage data, records, automate workflows' phrasing could loosely overlap with other integration 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/payumoney/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.