agent-payments

Agent skill for payments - invoke with $agent-payments

3.70x

Quality

36%

Does it follow best practices?

Impact

100%

3.70x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-payments/SKILL.md

Quality

Content

50%

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

The body pairs a concrete MCP toolkit with substantial descriptive and marketing-style padding, and lacks sequenced workflows with validation. It is moderately actionable but would benefit from trimming and from explicit verification steps for financial operations.

Suggestions

Trim marketing-style sections ("Quality standards", "Credit earning opportunities", "Cost optimization strategies") that describe philosophy rather than instruct; keep only what Claude cannot infer.

Add end-to-end worked examples composing the toolkit calls (e.g., check_balance -> if below threshold, configure_auto_refill -> verify new balance) so guidance is copy-paste ready.

Add validation checkpoints for payment operations (e.g., verify balance after refill, confirm a tier upgrade succeeded) since billing is a financial/destructive context requiring feedback loops.

Dimension	Reasoning	Score
Conciseness	The MCP toolkit block is tight, but sections like "Quality standards", "Credit earning opportunities", and "Cost optimization strategies" are marketing-style prose that describes philosophy Claude could infer, so it is mostly efficient but could be tightened.	2 / 3
Actionability	Real MCP signatures with parameters give concrete guidance, but there are no end-to-end worked examples composing the calls and much of the body describes rather than instructs, leaving it incomplete versus copy-paste-ready.	2 / 3
Workflow Clarity	The numbered "financial management approach" is a list of concerns rather than a sequenced process, and there are no validation checkpoints for payment/financial operations, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is a single >50-line file with content (pricing tiers, cost optimization, credit earning) that could be split out, giving some structure but no one-level-deep references.	2 / 3
	Total	8 / 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 thin and generic: it states the payments domain but no concrete capabilities and no explicit use-trigger, and the file contains a duplicate YAML block. It is distinguishable only by niche, not by described behavior.

Suggestions

Replace the generic "Agent skill for payments" with concrete capabilities, e.g. "Processes payments, manages credit balances, configures auto-refill, and handles tier upgrades within Flow Nexus."

Add an explicit "Use when..." trigger clause, e.g. "Use when the user asks about billing, credit balances, payment links, auto-refill, or subscription tiers."

Resolve the duplicate YAML frontmatter (two --- blocks in the file); keep a single frontmatter and fold the richer second description into it.

Dimension	Reasoning	Score
Specificity	The description "Agent skill for payments - invoke with $agent-payments" names a domain but lists no concrete actions, matching the vague/no-actions anchor rather than the domain-plus-actions anchor at 2.	1 / 3
Completeness	It gives only a weak "what" (no function described) and no "Use when..." clause for "when"; both sides are weak, which matches the level-1 anchor rather than the level-2 cap for a missing trigger.	1 / 3
Trigger Term Quality	"payments" is a natural keyword a user might say, but "invoke with $agent-payments" is invocation jargon and common variations (billing, credit, checkout, subscription) are missing, so it lands at the some-keywords-but-incomplete level.	2 / 3
Distinctiveness Conflict Risk	"payments" is a fairly distinct niche, but the description is too thin to reliably distinguish it from a generic billing skill, placing it at the somewhat-specific-but-overlapping level.	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
Path: .agents/skills/agent-payments/SKILL.md
Commit: 26c35b5

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