Name: cashfree
Rating: 56.8 (1 reviews)
Author: membranedev

cashfree

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

Quality

65%

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/cashfree/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.

The content is highly actionable with concrete, copy-paste CLI commands and a solid connection-setup workflow, but it carries some marketing padding and — critically for a payments platform — lacks validation/verification checkpoints around running potentially irreversible financial actions. Structure is good for a single-file skill.

Suggestions

Add a verification/checkpoint step around `membrane action run` for destructive operations (e.g. confirm order/payment parameters and inspect the `output` state before proceeding, and how to handle failures).

Trim the marketing prose ("used by businesses of all sizes, from startups to large enterprises") and redundant reassurance ("so you can focus on the integration logic rather than auth plumbing").

Fix the step numbering inconsistency ("skip to Step 2" / "#### 1b." with no corresponding Step 1a or Step 2 header) so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as "It is used by businesses of all sizes, from startups to large enterprises..." and "so you can focus on the integration logic rather than auth plumbing", fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Commands are fully executable and copy-paste ready with flags explained — `membrane login`, `membrane connection ensure`, `membrane action run ... --input '{...}'`, and the proxy request table cover the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with state-checking and a poll loop, but running Cashfree actions (orders, payouts) is a destructive/financial operation with no validation or verification step before/after execution, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-sectioned into install, auth, connection, search, run, proxy, and best-practices blocks; the inline proxy-options table and clientAction spec are appropriately placed with only minor organization gaps, fitting the score-4 anchor.	4 / 5
	Total	15 / 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 is distinct and includes an explicit "Use when" trigger, but its capability list is generic rather than payments-specific and its trigger terms lack common synonyms. Tightening the verbs to concrete Cashfree actions and broadening the trigger phrases would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Cashfree actions, e.g. "Create orders, capture payments, issue refunds, and make payouts."

Broaden the trigger clause to natural synonyms: "Use when the user wants to collect payments, process refunds, send payouts, or manage orders via Cashfree."

Add file/term coverage such as the Cashfree API or developers.cashfree.com references that users actually mention.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Cashfree integration") but the actions are generic — "Manage data, records, and automate workflows" — with no concrete payments-specific verbs (collect payments, issue refunds, make payouts), matching the score-2 anchor of naming the domain with minimal/generic actions.	2 / 5
Completeness	Both a "what" ("Cashfree integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Cashfree data") are present, but the "when" could be more specific, matching the score-4 anchor; it is not a 3 because the "Use when..." clause is explicit, and not a 5 because neither clause names concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural trigger term is "Cashfree" in "Use when the user wants to interact with Cashfree data"; the relevant keyword is present but common variations (payments, payouts, refunds, orders) are missing, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Cashfree" with a trigger scoped to Cashfree data gives it a clear niche with minimal conflict risk against other skills, matching the score-5 anchor.	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/cashfree/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.