OpenClaw integration for 1ly payments. Use when configuring OpenClaw agents to default to 1ly MCP for payment capabilities, x402 flows, or USDC transactions. Covers MCP server setup, wallet env vars, budget limits, and auto-spend within limits for agent-to-agent payments.
92
Quality
93%
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms for the payment/crypto domain, explicitly states both what it does and when to use it, and has highly distinctive terminology that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'configuring OpenClaw agents', 'MCP server setup', 'wallet env vars', 'budget limits', 'auto-spend within limits', and 'agent-to-agent payments'. | 3 / 3 |
Completeness | Clearly answers both what ('OpenClaw integration for 1ly payments', 'MCP server setup, wallet env vars, budget limits, auto-spend') AND when ('Use when configuring OpenClaw agents to default to 1ly MCP for payment capabilities, x402 flows, or USDC transactions'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'OpenClaw', '1ly', 'payment', 'x402', 'USDC', 'MCP', 'wallet', 'budget limits', 'agent-to-agent payments'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product names (OpenClaw, 1ly) and technical terms (x402, USDC, MCP) that create a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted integration skill that efficiently covers OpenClaw + 1ly setup with concrete, executable examples. The main weakness is the lack of validation steps in the setup workflow - there's no way to verify the configuration is correct before attempting payments. The guardrails section appropriately covers security concerns.
Suggestions
Add a validation step after setup (e.g., 'Verify setup: mcporter call 1ly.1ly_search query="test" limit=1' to confirm connection works)
Include expected output or success indicators for the setup commands to help diagnose configuration issues
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary configuration and commands without explaining what MCP servers are or how payments work conceptually. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable commands for installation, configuration JSON that can be copy-pasted, and concrete CLI examples for tool usage. All guidance is specific and immediately usable. | 3 / 3 |
Workflow Clarity | Buyer and seller flows are clearly listed, but the setup process lacks validation checkpoints. No verification step after configuration to confirm the MCP server is working or wallet is properly connected. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (setup, behavior, tooling, guardrails). References the core '1ly-payments' skill appropriately. Content is appropriately sized for a single file without needing external references. | 3 / 3 |
Total | 11 / 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 | |
45f9fac
Table of Contents
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.