agent-payments

Agent skill for payments - invoke with $agent-payments

3.70x

Quality

—

Does it follow best practices?

Impact

100%

3.70x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers strong actionability through concrete MCP tool examples and is reasonably well-sectioned, but it is somewhat padded with marketing language and treats multi-step financial operations as descriptive phases rather than validated workflows. No bundle files exist, so all content sits in one monolithic SKILL.md.

Suggestions

Convert the 'financial management approach' into a sequenced workflow with explicit validation checkpoints (e.g. verify balance after refill, confirm tier change before applying).

Trim marketing fluff such as the closing 'sustainable growth of the Flow Nexus ecosystem' sentence and consolidate the earning-opportunity list if it is not core to payment operations.

Move stable reference material (pricing tiers, credit-earning rules, cost-optimization strategies) into separate reference files linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The toolkit code block and sectioned lists are mostly efficient and do not explain concepts Claude already knows, but marketing padding like 'supporting the sustainable growth of the Flow Nexus ecosystem and creator economy' and tangential earning-opportunity sections could be trimmed.	2 / 3
Actionability	The payments toolkit provides concrete, copy-paste-ready MCP tool calls with real parameters (e.g. configure_auto_refill with enabled/threshold/amount, create_payment_link with amount), matching the fully executable anchor.	3 / 3
Workflow Clarity	The 'financial management approach' is a numbered list of high-level phases rather than a sequenced workflow, and it lacks validation/verification checkpoints for sensitive operations like payment processing and tier upgrades, capping it at 2.	2 / 3
Progressive Disclosure	The body is a single monolithic file with no bundle references, and distinct topics (pricing tiers, earning opportunities, cost optimization) that could live in separate reference files are all inline, fitting the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

22%

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 frontmatter description is weak: it names the payments domain but lists no concrete actions and provides no 'Use when' trigger guidance, leaving both what and when underspecified. Note the file contains a second, stronger description block in the body, but per the parsing rules only the first frontmatter block is the description field.

Suggestions

Replace the description with specific actions, e.g. 'Check credit balances, process payments, configure auto-refill, and manage subscription tiers within Flow Nexus.'

Add an explicit trigger clause such as 'Use when the user asks about credit balances, billing, payments, or tier upgrades in Flow Nexus.'

Include natural term variations (credits, billing, subscriptions, rUv) so the skill matches how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	The description only names the domain ("Agent skill for payments") with no concrete actions listed, matching the vague 'Helps with documents' anchor rather than naming specific operations.	1 / 3
Completeness	It states neither what the skill concretely does (only 'for payments') nor any 'Use when...' trigger guidance, so both what and when are missing or very weak.	1 / 3
Trigger Term Quality	"payments" is a natural keyword a user might say, but coverage is thin with no common variations (billing, credits, subscriptions), and "$agent-payments" is invocation syntax rather than a natural trigger.	2 / 3
Distinctiveness Conflict Risk	"payments" gives a recognizable niche but the description is generic enough that it could overlap with other payment/billing skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: 03d4f84

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