agent-payments
Agent skill for payments - invoke with $agent-payments
40
7%
Does it follow best practices?
Impact
100%
3.70xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-payments/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is critically underspecified. It provides no concrete actions, no trigger guidance, and no distinguishing details—just the word 'payments' and an invocation command. It would be nearly impossible for Claude to reliably select this skill over others or know when it is appropriate to use.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Processes payment transactions, issues refunds, queries payment status, and manages billing records.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about payments, refunds, invoices, billing, charges, or transaction history.'
Remove or de-emphasize the invocation syntax ('$agent-payments') and instead focus on describing capabilities and use cases that help Claude distinguish this skill from other financial or billing-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Agent skill for payments' which is extremely vague. No concrete actions are listed—it doesn't describe what it does with payments (process them, refund them, query them, etc.). | 1 / 3 |
Completeness | The 'what' is essentially absent beyond the word 'payments', and there is no 'when' clause or explicit trigger guidance whatsoever. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only relevant keyword is 'payments', which is very generic. It lacks natural variations users might say like 'pay', 'invoice', 'billing', 'charge', 'refund', 'transaction', etc. The '$agent-payments' invocation syntax is technical jargon, not a natural trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | 'Payments' is extremely broad and could overlap with billing skills, invoicing skills, financial reporting skills, or any other money-related skill. There is nothing to distinguish this skill's specific niche. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a product requirements document or marketing brief than an actionable skill for Claude. It is heavily padded with descriptive content (pricing tiers, earning opportunities, quality standards, optimization strategies) that either Claude doesn't need or should be in separate reference files. The most valuable part—the MCP function signatures—lacks workflow context, error handling, and validation steps critical for financial operations.
Suggestions
Remove all descriptive/marketing content (quality standards, credit earning opportunities, cost optimization strategies) or move them to a separate REFERENCE.md file, keeping SKILL.md focused on how to use the payment tools.
Add explicit multi-step workflows with validation for key operations like processing a payment (check balance → create link → verify completion → update balance) and configuring auto-refill, including error handling and rollback steps.
Document expected return values and error states for each MCP function so Claude knows how to handle failures in financial operations.
Remove the persona framing ('You are a Flow Nexus Payments Agent...') and responsibility lists—replace with concise, actionable instructions that assume Claude's competence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude doesn't need spelled out (pricing tiers, credit earning opportunities, cost optimization strategies, quality standards). Much of this reads like marketing copy or a product spec rather than actionable instructions. The 'You are a...' persona framing and lists of responsibilities add significant token bloat. | 1 / 3 |
Actionability | The toolkit section provides concrete function signatures with parameters, which is useful. However, the functions are presented as a reference list without context on when to use each one, error handling, or expected return values. The rest of the content is descriptive rather than instructive—listing strategies and responsibilities without executable guidance. | 2 / 3 |
Workflow Clarity | There are no clear multi-step workflows for payment processing, which is a financial/destructive operation requiring validation checkpoints. The numbered list under 'financial management approach' describes abstract responsibilities, not sequenced steps. No validation, error handling, or feedback loops are defined for payment operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no clear hierarchy. Pricing tiers, credit earning details, cost optimization strategies, and quality standards could all be separated into reference documents. Everything is dumped inline with no navigation structure. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
f547cec
- Reviewed
Table of Contents
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.