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.
81
Quality
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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). It provides comprehensive trigger scenarios, lists concrete capabilities, and uses distinctive terminology that minimizes conflict risk with other skills. The description effectively communicates both what the skill does and when to use it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'accepting USDC', 'marketplace search', 'paid API calls with auto-payment', 'store/link creation', 'stats', and 'key management'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (agent-native payments, USDC handling, store creation, marketplace search, etc.) AND when with explicit 'Use when...' clause listing multiple trigger scenarios (x402 payment handling, accepting USDC, paying for APIs, creating stores, agent workflows). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'x402 payment', 'USDC', 'payment gateway', 'agent-to-agent', 'paid APIs', 'Solana', 'Base', 'stores', 'paid links'. Good coverage of domain-specific and user-facing terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: '1ly MCP', 'x402 payment', 'USDC', 'Solana and Base', 'agent-to-agent paid workflows'. These are unique identifiers unlikely to conflict with generic payment or API skills. | 3 / 3 |
Total | 12 / 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.
This skill provides solid actionable guidance with concrete commands and tool schemas, making it immediately usable. However, it could be more concise by removing explanatory prose Claude doesn't need, and workflow clarity would benefit from explicit validation steps and error recovery guidance, especially important given real money is involved.
Suggestions
Add explicit validation/error handling steps in the spend flow before executing payments (e.g., 'If 1ly_search returns no results, inform user; if 1ly_call fails, check error and retry or escalate')
Remove the 'Default prompts to embed in agent behavior' section - these are instructions Claude can infer from the core behavior section
Add a troubleshooting section or reference file for common errors (wallet not found, insufficient balance, network issues)
Trim the opening paragraph - Claude doesn't need the 'This MCP server gives AI agents the ability to' framing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanations like 'This MCP server gives AI agents the ability to' and redundant descriptions. The 'Default prompts to embed in agent behavior' section is somewhat verbose and could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable commands for setup, clear tool names with input schemas, and specific examples for both spend and accept flows. The bash commands and JSON payloads are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are listed for both accepting and spending flows, but validation checkpoints are minimal. The 'Verify setup' step exists but there's no guidance on what to do if verification fails, and no explicit validation before spending real money. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's somewhat monolithic. The tool documentation could be split into separate reference files, and there are no external file references for advanced topics like troubleshooting or detailed API schemas. | 2 / 3 |
Total | 9 / 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.