agent-payments
Agent skill for payments - invoke with $agent-payments
43
11%
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 is an extremely weak description that provides almost no useful information for skill selection. It names only a broad domain ('payments') without specifying any concrete actions, trigger conditions, or distinguishing characteristics. It reads more like a label than a functional description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Processes payments, issues refunds, checks transaction status, manages recurring billing'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about processing a payment, issuing a refund, checking a transaction, or managing invoices'
Remove the invocation syntax ('invoke with $agent-payments') from the description and replace it with capability details that help Claude distinguish this skill from other potentially similar skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Agent skill for payments' which is extremely vague. It names a broad domain ('payments') but lists zero concrete actions. No specific capabilities like processing payments, issuing refunds, checking balances, etc. are mentioned. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no specific actions) and 'when should Claude use it' (no 'Use when...' clause or equivalent trigger guidance). Both are missing or extremely weak. | 1 / 3 |
Trigger Term Quality | The only keyword is 'payments', which is overly generic. It lacks natural user terms like 'pay', 'invoice', 'refund', 'charge', 'transaction', 'billing', etc. The invocation syntax '$agent-payments' is technical jargon, not a natural user trigger. | 1 / 3 |
Distinctiveness Conflict Risk | 'Payments' is extremely broad and could overlap with billing skills, invoicing skills, financial processing skills, or any other payment-adjacent functionality. There is nothing to distinguish this skill's specific niche. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%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 overview or agent persona description than an actionable skill file. While it provides useful MCP tool signatures, the majority of the content is descriptive padding about pricing tiers, earning opportunities, and quality standards that don't help Claude execute tasks. It critically lacks concrete workflows, decision trees, and validation steps for financial operations.
Suggestions
Replace descriptive sections (pricing tiers, credit earning opportunities, quality standards) with concrete decision workflows, e.g., 'When user asks to upgrade: 1. Check current tier with user_stats, 2. Confirm upgrade intent, 3. Call user_upgrade, 4. Verify new tier status'
Add validation and confirmation steps for payment and tier change operations—these are financial/destructive actions that should never proceed without explicit user confirmation
Remove the persona preamble and responsibility lists; instead provide a concise tool reference table and specific decision logic for when to use each tool
Add concrete examples of common user requests mapped to exact tool call sequences with expected outputs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly 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 product documentation rather than actionable instructions. The persona preamble ('You are a Flow Nexus Payments Agent, an expert in...') and lists of responsibilities are padding. | 1 / 3 |
Actionability | The JavaScript code block provides concrete MCP tool calls with parameter examples, which is useful. However, the rest of the content is descriptive rather than instructive—it lists what the agent should do conceptually (e.g., 'Track credit usage and predict refill needs') without specifying how to execute those tasks or providing decision logic for when to use which tool. | 2 / 3 |
Workflow Clarity | There are no clear multi-step workflows, no sequencing of operations, and no validation checkpoints. The numbered list under 'financial management approach' describes abstract responsibilities, not executable steps. For payment processing and tier upgrades (which are potentially destructive/financial operations), there are no confirmation or validation steps defined. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with bold headers, which provides some structure. However, it's a monolithic file with no references to external documentation, and several sections (pricing tiers, credit earning opportunities, cost optimization strategies) could be split out or omitted entirely. No bundle files exist to reference. | 2 / 3 |
Total | 6 / 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/ruflo
- Commit
844f68d
- 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.