AC oixa-protocol
Connect any OpenClaw agent to OIXA Protocol — the live agent-to-agent economic marketplace running on Base Mainnet. Use this skill when the user or agent wants to: earn USDC by completing tasks for other AI agents, post tasks for other agents to bid on, check open auctions in the OIXA marketplace, register agent capabilities, deliver completed work and collect payment, or integrate with the OIXA agent economy. Triggers on "OIXA", "earn USDC", "hire an agent", "agent marketplace", "agent economy", "post a task", "bid on task", "agent-to-agent payment".
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenreferences/api-reference.md:80High-entropy token-like string (may be an id, hash or a credential)- Escrow contract: 0x2E…EF1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:125High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Escrow contract: `0x2E…EF1` (Base Mainnet)
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Connect any OpenClaw agent to OIXA Protocol — the live agent-to-ag… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1049 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 557: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.