payment
Payment processing and management. Handle invoices, transactions, and payment gateway integrations.
36
Quality
23%
Does it follow best practices?
Impact
Pending
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 relevant capabilities, but suffers from missing explicit trigger guidance ('Use when...') which is critical for skill selection. The trigger terms are adequate but not comprehensive, and the description could be more specific about concrete actions supported.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions payments, invoices, billing, checkout, Stripe, PayPal, or payment processing'.
Expand trigger terms to include common variations: 'billing', 'checkout', 'refunds', 'subscriptions', and specific gateway names like 'Stripe' or 'PayPal'.
List more specific concrete actions such as 'create and send invoices', 'process refunds', 'set up recurring billing', or 'integrate payment APIs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (payment processing) and lists some actions (handle invoices, transactions, payment gateway integrations), but lacks comprehensive detail on specific operations like 'create invoices', 'process refunds', or 'reconcile payments'. | 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 rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'invoices', 'transactions', and 'payment gateway', but misses common variations users might say such as 'billing', 'checkout', 'Stripe', 'PayPal', 'refunds', or 'payment processing'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to payments domain, but 'transactions' and 'integrations' are generic terms that could overlap with database skills, API integration skills, or financial analysis 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 feature overview or README rather than actionable guidance. It lists capabilities and supported gateways but provides zero implementation details, code examples, or workflows. For payment processing—a domain requiring careful validation and error handling—the complete absence of concrete steps and safety checkpoints is a significant gap.
Suggestions
Add executable code examples for at least one gateway (e.g., Stripe invoice creation with actual API calls and response handling)
Define a clear workflow for payment processing with validation checkpoints: verify amount -> process -> confirm -> handle errors
Include gateway-specific reference files (e.g., STRIPE.md, PAYPAL.md) with concrete integration details and link to them from the main skill
Expand safety rules into actionable verification steps (e.g., 'Before processing, confirm amount with user and log transaction ID')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief and doesn't over-explain concepts Claude knows, but the feature list and gateway list are somewhat generic and don't add actionable value beyond what the description already conveys. | 2 / 3 |
Actionability | The skill provides no concrete code, API calls, commands, or executable guidance. The 'Usage Examples' are just natural language prompts, not implementation details. There's no actual instruction on HOW to create invoices, process payments, or integrate with any gateway. | 1 / 3 |
Workflow Clarity | No workflow is defined for payment processing, which is a multi-step operation requiring validation. There are no sequences, checkpoints, or verification steps for handling transactions, refunds, or error recovery. | 1 / 3 |
Progressive Disclosure | The content is a flat list with no references to detailed documentation, API guides, or gateway-specific instructions. For a skill covering 4+ payment gateways and multiple operations, there should be clear navigation to detailed materials. | 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
45f9fac
- 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.