agent-agentic-payments
Agent skill for agentic-payments - invoke with $agent-agentic-payments
56
Quality
32%
Does it follow best practices?
Impact
100%
2.22xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-agentic-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 deficient across all dimensions. It functions more as a label than a description, providing only a name and invocation command without explaining what the skill does, what actions it performs, or when it should be selected. Claude would have no basis for choosing this skill appropriately.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Process payments, handle refunds, verify transactions, manage subscriptions').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions payments, billing, charges, refunds, or transaction processing').
Remove the invocation command from the description and replace with capability-focused content that explains the skill's purpose and scope.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for agentic-payments' is completely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no explanation of capabilities or use cases. | 1 / 3 |
Trigger Term Quality | The only terms present are 'agent', 'agentic-payments', and the invocation command. These are technical/internal terms, not natural keywords a user would say when needing payment functionality. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no distinguishing characteristics. 'Agentic-payments' hints at a domain but without specifics, it could conflict with any payment-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionable code examples with realistic MCP tool calls, making it immediately usable. However, it suffers from verbosity with sections like 'Real-world use cases' and 'Security standards' that don't add operational value. The workflow lacks explicit validation checkpoints critical for payment operations, and the monolithic structure would benefit from splitting detailed content into referenced files.
Suggestions
Add explicit validation checkpoints to the workflow (e.g., 'Verify mandate signature before authorizing payment', 'Confirm consensus threshold met before proceeding')
Remove or drastically condense 'Real-world use cases you enable' and 'Security standards' sections - Claude understands these concepts
Split API reference into a separate REFERENCE.md file, keeping only 2-3 essential examples in SKILL.md
Add error handling examples showing what to do when signature verification fails or consensus times out
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., 'Real-world use cases you enable', 'Security standards' lists) that Claude already understands. The API examples are useful but surrounded by verbose context that could be trimmed. | 2 / 3 |
Actionability | Provides concrete, executable JavaScript code examples for all major operations with realistic parameters. The MCP tool calls are copy-paste ready with clear parameter structures and example values. | 3 / 3 |
Workflow Clarity | The 6-step workflow is listed but lacks explicit validation checkpoints and error recovery steps. For payment operations involving cryptographic signing and multi-agent consensus, there should be explicit 'verify before proceeding' gates and failure handling. | 2 / 3 |
Progressive Disclosure | Content is monolithic with no references to external files for detailed documentation. The API reference, use cases, and security standards could be split into separate files, with SKILL.md serving as a concise overview. | 2 / 3 |
Total | 9 / 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
b2618f9
- 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.