openclaw-1ly-payments
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.
67
82%
Does it follow best practices?
Impact
—
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 narrow, specific domain (OpenClaw + 1ly payment integration) with concrete actions and explicit trigger guidance. It uses third person voice correctly, includes relevant domain-specific trigger terms, and has a clear 'Use when' clause. The description is concise yet comprehensive for its niche.
| 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. These are concrete, actionable capabilities. | 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 trigger terms users would say: 'OpenClaw', '1ly', 'payments', 'x402', 'USDC', 'MCP server', 'wallet', 'budget limits', 'agent-to-agent payments'. Good coverage of domain-specific terms a user working in this space would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining OpenClaw, 1ly, x402, and USDC in the context of agent-to-agent payments. Very unlikely to conflict with other skills given the specificity of the domain and technology stack. | 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 setup instructions with concrete commands and configuration examples for OpenClaw + 1ly integration. Its main weaknesses are the lack of validation/verification steps in the workflow (e.g., confirming the MCP server is running after setup) and a missing reference link to the dependent '1ly-payments' skill. The content is mostly concise but could trim some explanatory prose.
Suggestions
Add a validation step after MCP server setup, e.g., 'Verify: mcporter list 1ly should show available tools' to confirm correct installation.
Link to the referenced '1ly-payments' skill explicitly so users can navigate to it, or inline the critical assumptions from that skill.
Add error handling guidance for common failure modes (e.g., invalid wallet path, exceeded budget, API key issues).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary explanation (e.g., 'This skill assumes the core 1ly toolset from the 1ly-payments skill' and some verbose agent behavior descriptions). The tool conventions and setup sections are reasonably lean but could be tightened. | 2 / 3 |
Actionability | Provides fully executable commands for installation, configuration JSON that's copy-paste ready, and concrete CLI examples for tool usage. The buyer/seller flows are specific and actionable. | 3 / 3 |
Workflow Clarity | Steps are listed and sequenced for setup, and buyer/seller flows are outlined. However, there are no validation checkpoints—no step to verify the MCP server is running, no way to confirm the config is valid, and no error recovery guidance for failed payments or misconfiguration. | 2 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it references a '1ly-payments' skill without linking to it. With no bundle files, there's no progressive disclosure structure—everything is inline, though the content length is moderate enough that this is acceptable. | 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
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.