kleros-skills

Use when a request involves Kleros, decentralized justice, or decentralized dispute resolution. Applies to interacting with Kleros Curate token-curated registries (Light Curate, Stake Curate / PGTCR, Scout), uploading dispute evidence or metadata to IPFS via the Kleros x402 gateway, submitting or challenging registry items, funding appeals, deploying new registries, and reading on-chain arbitration state. Covers PNK staking, juror selection, ERC-792 Arbitrable/Arbitrator interfaces, Kleros court hierarchy, and ecosystem tooling on Ethereum, Gnosis, and Sepolia.

Interact with Kleros Curate registries across Ethereum Mainnet, Gnosis Chain, and Sepolia. Use when the user mentions Curate, Light Curate/LightGeneralizedTCR/LGTCR, Stake Curate/PermanentGTCR/PGTCR, Scout, token-curated registry/TCR, token lists, address/CDN tags, Goldsky, MetaEvidence, Verify Your List, or Curate calls such as addItem, removeItem, challengeItem, challengeRequest, and fundAppeal. Covers registry discovery and queries; policy/schema inspection; submissions, removals, challenges, evidence, appeals, rewards, execution; factory deployment; and frontend verification on all three networks. Also trigger for registry/list operations paired with Kleros, arbitrator, dispute, juror, or PNK context, and whenever the user names or tests kleros-curate. Do NOT use for non-Kleros registries or generic IPFS uploads without Curate context; route standalone uploads to kleros-ipfs-upload.

Upload one Kleros-ecosystem file per paid request to IPFS through the Kleros x402 gateway for $0.01 USDC on Base mainnet. Use for dispute evidence, MetaEvidence JSON, court/dispute/arbitrator policies, Curate item metadata, juror justifications, or any artifact a Kleros contract or subgraph will reference by CID. Trigger when the request mentions Kleros, court, arbitrator, dispute, juror, Curate, Proof of Humanity, evidence, meta-evidence, justification, explicitly names this gateway or skill, or asks to test or validate it. Do NOT use for generic IPFS/CID requests without Kleros context; recommend a general-purpose pinning service. Each request accepts exactly one file: different bytes require separate paid uploads, while identical bytes should reuse one CID.

Report a problem, point of confusion, coverage gap, or praise about any Kleros skill (kleros-skills root, kleros-ipfs-upload, kleros-curate, openclaw-skill) directly to maintainers via a structured GitHub issue. Trigger when a skill's instructions were wrong, unclear, incomplete, or when you want to flag something that worked well. Do NOT trigger for Kleros protocol disputes, Curate registry challenges, or on-chain arbitration questions — those belong to kleros-curate. Do NOT trigger for general Kleros product or support questions unrelated to skill content — direct those to kleros.io.

Kleros protocol knowledge for AI agents — dispute resolution, Curate registries, IPFS evidence uploads, and arbitration integration. Use when: (1) uploading dispute evidence or metadata to IPFS, (2) submitting, challenging, or appealing items in Curate registries, (3) deploying new Curate registries, (4) the user mentions Kleros, PNK, Curate, arbitration, or decentralized justice, (5) working with ERC-792 Arbitrable/Arbitrator interfaces. NOT for: generic IPFS uploads with no Kleros context, non-Kleros dispute systems, or general Ethereum development — use ethskills for those.