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 underdeveloped. It provides no concrete actions, no trigger guidance, and no distinguishing details—just a vague domain label ('payments') and an invocation command. It would be nearly impossible for Claude to reliably select this skill from a pool of even a few related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Processes payment transactions, issues refunds, checks payment status, and retrieves invoice details.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about payments, refunds, charges, billing, invoices, or transaction history.'
Remove the invocation instruction ('invoke with $agent-payments') from the description, as it is operational detail rather than selection-relevant information, and replace it with distinguishing capability details.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Agent skill for payments' is extremely vague—it doesn't describe what the skill actually does (e.g., process payments, refund transactions, check payment status). | 1 / 3 |
Completeness | The description barely addresses 'what' (just 'payments') and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only keyword is 'payments,' which is overly generic. There are no natural user terms like 'refund,' 'charge,' 'invoice,' 'billing,' 'transaction,' or file/format references that a user might naturally say. | 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 marketing document or persona description than an actionable skill file. While it includes useful MCP function signatures, the majority of content is descriptive fluff about responsibilities, quality standards, and strategies that don't help Claude execute specific payment tasks. Critical workflow sequences for payment processing and error handling are entirely absent.
Suggestions
Replace the descriptive persona and responsibility lists with concrete step-by-step workflows (e.g., 'To process a payment: 1. Check balance with mcp__flow-nexus__check_balance(), 2. If insufficient, create payment link, 3. Verify payment completed, 4. Confirm updated balance').
Add explicit validation and error-handling steps for payment operations, such as confirming payment success, handling failed transactions, and verifying balance updates after auto-refill configuration.
Remove or move to a separate reference file the static content like pricing tiers, credit earning opportunities, and cost optimization strategies—these don't need to consume tokens in the main skill file.
Add concrete examples showing complete input/output for common payment scenarios (e.g., checking balance and deciding whether to trigger auto-refill).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Heavily padded with information Claude already knows or doesn't need restated (quality standards, cost optimization strategies, credit earning opportunities with specific amounts). The persona framing ('You are a Flow Nexus Payments Agent') and extensive lists of general financial principles waste tokens on context that doesn't help Claude execute tasks. | 1 / 3 |
Actionability | The JavaScript toolkit section provides concrete function signatures with parameters, which is useful. However, the code is not fully executable (no usage workflow showing how to combine calls), and much of the content is descriptive rather than instructive (e.g., 'Cost optimization strategies you recommend' is vague guidance, not actionable steps). | 2 / 3 |
Workflow Clarity | There are no clear multi-step workflows with sequencing or validation checkpoints. The 'financial management approach' is a list of abstract responsibilities, not a sequenced process. For payment processing (a risky/destructive operation), there's no validation, confirmation, or error-handling workflow defined. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no clear separation between quick-start essentials and detailed reference material. Pricing tiers, credit earning tables, and cost optimization strategies are all inlined when they could be separated or omitted. | 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/ruflo
- Commit
ccb062f
- 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.