New skill proposal: `use-agent-marketplace`

[OliverDevDS]

Summary

Proposes a new skill documenting AgentBidBoard — an onchain bid marketplace connecting ERC-8004 agents with ERC-8183 job clients on Arc.

The gap

ERC-8004 and ERC-8183 exist independently but there is no documented pattern for how agents announce availability and clients discover them before creating jobs. This skill fills that gap with a reference contract deployed and validated on Arc Testnet.

What the skill covers

• Full bid lifecycle: postBid, acceptBid, cancelBid, getActiveBids
• Agent selection strategy: filter by capabilities, sort by reputation and price
• Bridge pattern: acceptBid() followed immediately by ERC-8183 createJob()
• Deploy instructions for custom instances
• 5 antipatterns with WRONG/CORRECT examples
• Proof of concept with Arc Testnet tx hashes

Reference implementation

• Contract: 0xFb72B52eaF2b1A2e0cf96F8eDA1386288fC74ad9 (Arc Testnet)
• Repository: https://github.com/OliverDevDS/arc-agent-marketplace
• Tests: 17/17 passing

[erhnysr]

Opened #37 implementing this skill.

It follows the use-arc/accept-agent-payments format and documents the full AgentBidBoard bid lifecycle (postBid, cancelBid, acceptBid, getActiveBids, getBidsByAgent) against your reference contract at 0xFb72B52eaF2b1A2e0cf96F8eDA1386288fC74ad9, with viem/TypeScript examples, agent-selection strategy, custom-instance deploy steps, and the acceptBid() → ERC-8183 createJob() bridge.

One thing I made explicit in the antipatterns section: since the contract stores but never verifies agentId/reputationScore and acceptBid() creates no job onchain, the skill frames the ERC-8004/ERC-8183 integration as an off-chain client-side convention and warns readers to verify identity/reputation out of band. Happy to adjust the framing if you'd prefer it worded differently.