payment
Payment processing and management. Handle invoices, transactions, and payment gateway integrations.
29
23%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/payment/SKILL.mdQuality
Discovery
32%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 description identifies the payment processing domain and lists a few relevant capabilities, but it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms are decent but miss many common user phrases related to payments, billing, and specific gateway names.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about billing, payment processing, invoicing, refunds, or integrating payment gateways like Stripe or PayPal.'
Expand trigger terms to include common variations users would say: 'billing', 'refunds', 'checkout', 'subscriptions', 'Stripe', 'PayPal', 'charges', 'receipts'.
List more specific concrete actions such as 'generate and send invoices, process refunds, configure webhook endpoints, reconcile payment records' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (payment processing) and lists some actions (handle invoices, transactions, payment gateway integrations), but these are somewhat general rather than deeply specific concrete actions like 'generate invoices, process refunds, reconcile transactions, configure Stripe webhooks'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also only moderately detailed, this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'invoices', 'transactions', 'payment gateway', and 'payment processing', but misses common user variations such as 'billing', 'refunds', 'Stripe', 'PayPal', 'checkout', 'subscriptions', or 'charges'. | 2 / 3 |
Distinctiveness Conflict Risk | The payment/invoicing domain is reasonably specific and unlikely to conflict with most other skills, but 'transactions' is broad enough to overlap with database or e-commerce skills, and 'integrations' could overlap with general API integration skills. | 2 / 3 |
Total | 7 / 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 is essentially a placeholder or feature overview with no actionable content. It lists capabilities and supported gateways but provides zero concrete implementation guidance—no code, no API patterns, no workflows, and no references to detailed documentation. For a domain as sensitive and complex as payment processing, the lack of validation steps, error handling, and concrete integration examples makes this skill ineffective.
Suggestions
Add concrete, executable code examples for at least one gateway (e.g., Stripe) showing how to create an invoice, process a payment, and issue a refund with actual API calls.
Define explicit multi-step workflows with validation checkpoints for payment operations, e.g., 'verify amount → create charge → confirm status → handle errors → log transaction'.
Create separate reference files for each gateway integration (e.g., STRIPE.md, PAYPAL.md) and link to them from the main skill with clear navigation.
Replace the natural language 'Usage Examples' with actual code snippets or tool invocation patterns that Claude can execute.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes feature lists and gateway lists that are essentially just labels without actionable detail. The features section reads like a marketing bullet list rather than useful instruction for Claude. | 2 / 3 |
Actionability | There is no executable code, no API calls, no concrete commands, and no specific integration patterns. The 'Usage Examples' are just natural language prompts, not actionable implementation guidance. Claude would not know how to actually process a payment from this skill. | 1 / 3 |
Workflow Clarity | There is no workflow defined for any payment operation—no steps for creating invoices, processing payments, handling refunds, or integrating with any gateway. For operations involving financial transactions (destructive/irreversible), the complete absence of validation checkpoints and sequenced steps is a critical gap. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow document with no references to supporting files, no detailed guides for individual gateways, and no structured navigation. Given the breadth of topics claimed (4 gateways, 5 features), there should be significant supporting material referenced. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.