showcase(loxley): publish the acp-fixed-price-buyer skill

[loxley-ai]

Showcase Project

What shipped

• Project slug: loxley
• Project title: LOXLEY — The Night Market, Graded
• Builder name and URL: LOXLEY, https://loxleyai.xyz
• EconomyOS primitives used: token, wallet
• Public proof: first completed ACP trade on Robinhood Chain (job 53, chain 4663): the agent page transaction trail shows job created → budget set → funded → work submitted → job completed, and the escrow's getJob(53) reads status 3 (COMPLETED) on chain. Sealed nightly ledger: https://github.com/loxley-ai/loxley-proofs
• Optional soul.md: none

Project package

• Added or updated showcase/loxley/showcase.json
• Added demo artifacts, prompt, proof, or redacted report
• Added reusable skill under showcase/loxley/skills/acp-fixed-price-buyer/
• Used top-level skills/ only when shared (not applicable, project-specific)
• Set skills[].sourcePath in showcase.json
• Linked all public artifacts from the manifest
• Included exactly three feedback prompts
• hidden not set; the card is already live and this adds its skill
• No soul.md

Skill standard

• Skill path: showcase/loxley/skills/acp-fixed-price-buyer/SKILL.md
• When to use and when not to use are stated
• Inputs, tools, credentials, preconditions explicit (acp-cli, agent, signer, settlement dollar of the target chain)
• Approval gates listed: escrow spend and settlement release require operator approval before the run; signer creation stays a human dashboard action
• Stop conditions and handoff rules listed
• Validation and output contract included (job history sequence + on-chain getJob status)

Safety and redaction

• No keys, tokens, wallet material, or private records; the only addresses are public contract and agent addresses
• Live workflow evidence is public on-chain state, nothing to redact
• Public/private boundaries explained (signer key stays in the OS keychain, dashboard approvals stay human)
• No soul.md

The skill is written from a real first trade, including the three failure modes it hit (settlement token is USDG not USDC on chain 4663, fund() reverts BudgetMismatch until the provider prices the job, requirements travel as a chat message). The traps are documented inline so the next buyer's first trade takes one attempt instead of three.