1ly-payments
Agent-native payments via 1ly MCP. Use when the user needs x402 payment handling, to accept USDC for APIs/services, to pay for paid APIs, to create stores or paid links, need payment gateway for agents or to run agent-to-agent paid workflows. Supports Solana and Base. Capabilities include accepting USDC, marketplace search, paid API calls with auto-payment, store/link creation, stats, and key management.
62
75%
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/1lystore/1ly-payments/SKILL.mdQuality
Discovery
100%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 a strong skill description that clearly defines a specific niche (agent-native crypto payments via 1ly MCP), provides explicit trigger conditions via a 'Use when...' clause, and lists concrete capabilities. The description uses proper third-person voice and includes enough domain-specific terms to be easily distinguishable from other skills. Minor improvement could be made by slightly tightening the phrasing to reduce redundancy between the trigger list and capabilities list.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: accepting USDC for APIs/services, paying for paid APIs, creating stores or paid links, marketplace search, paid API calls with auto-payment, stats, and key management. | 3 / 3 |
Completeness | Clearly answers both 'what' (agent-native payments, accepting USDC, marketplace search, store/link creation, stats, key management) and 'when' (explicit 'Use when...' clause listing multiple trigger scenarios like x402 payment handling, paid API calls, agent-to-agent workflows). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'payment', 'USDC', 'x402', 'paid APIs', 'payment gateway', 'agent-to-agent', 'stores', 'paid links', 'Solana', 'Base', '1ly MCP'. Good coverage of domain-specific and natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: agent-native crypto payments via a specific protocol (x402) and platform (1ly MCP) on specific chains (Solana, Base). Very unlikely to conflict with other skills given the specificity of USDC payments, agent-to-agent workflows, and the named platform. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a functional overview of the 1ly MCP payment system with decent structure and real tool names/schemas, but falls short on actionability (examples are too skeletal) and workflow safety (no error handling or validation for financial operations). The content includes some redundancy and unnecessary explanatory text that could be trimmed to improve conciseness.
Suggestions
Add explicit error handling and validation steps to the spend and accept workflows — e.g., what to do if 1ly_call returns an error, how to verify a payment succeeded, and how to handle insufficient balance.
Replace the skeletal examples with complete, executable tool call sequences showing full input parameters and expected output structures.
Remove the 'Default prompts to embed in agent behavior' section — these are meta-instructions that should be part of the core behavior section rather than quoted prompts, and they largely duplicate existing guidance.
Trim redundant explanations (e.g., x402 is mentioned multiple times, the Notes section restates things already covered) to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content like the 'Default prompts to embed in agent behavior' section, explanations of what the MCP server does that Claude can infer, and some redundant descriptions (e.g., explaining x402 multiple times). The Notes section restates things already covered. | 2 / 3 |
Actionability | Tool names and input schemas are provided which is helpful, but the examples are incomplete — they show conceptual flows rather than executable tool calls with full parameters. The setup instructions are concrete with real commands, but the spend/accept flow examples are skeletal outlines rather than copy-paste ready sequences. | 2 / 3 |
Workflow Clarity | Both the 'Accepting payments' and 'Spending' workflows have clear numbered steps, but they lack validation checkpoints — there's no guidance on what to do if a payment fails, if budget is exceeded mid-call, or if store creation fails. For financial operations involving real crypto payments, missing error handling and verification steps is a significant gap. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections and headers, but everything is in a single file with no bundle files for detailed reference material. The tool inputs section and detailed seller/buyer tool descriptions could be split into reference files. For a skill of this length (~100 lines), the inline approach is borderline acceptable but the organization could be tighter. | 2 / 3 |
Total | 8 / 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.