Agent skill · software engineering · aiskillstore
kleros-curate
Interact with Kleros Curate token-curated registries for token lists, address tags, and policy-driven curation. Use for Curate, Light Curate or LightGeneralizedTCR (LGTCR), Stake Curate or PermanentGTCR (PGTCR), Scout, TCRs, curated lists, decentralized registries, token lists, address or CDN tags, Goldsky, and addItem, removeItem, challengeItem, or challengeRequest. Covers submitting, challenging, removing, and appealing registry items; deploying registries; browsing or querying entries; checking address tags; adding tokens; and funding appeal rounds. Also use for registry operations in a Kleros, arbitrator, dispute, juror, or PNK context. Do not use for non-Kleros registries or generic IPFS uploads; use kleros-ipfs-upload for Kleros IPFS content. Explicit requests for this skill or its tests always qualify.
Why this skill is useful
Adds executable scripts for interacting with Kleros Curate contracts, including submission, challenge, and querying operations that are not publicly documented.
What it needs
Requires ethereum, web3 installed locally. Requires kleros account access. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Kleros Curate Kleros Curate is a decentralized verification system for exclusive, policy-driven registries. Registries are governed by a policy document stored on IPFS — every submission is judged against that policy, and jurors consult it if a dispute arises. The deposit/challenge/arbitration cycle: 1. A submitter proposes an item and locks a submission deposit as a pledge that the item complies with the registry policy. 2. The item enters a challenge window (configurable per registry, typically days to weeks). Anyone can review submissions during this window. 3. If nobody challenges within the window, the item is accepted and the submitter's deposit is returned in full — compliant submissions carry no permanent inclusion cost. 4. If a challenger believes the submission violates the policy, they lock a challenge deposit and open a Kleros dispute. Impartial Kleros jurors read the policy and render a verdict. 5. The winner captures the loser's deposit as a bounty. The two-sided stake mechanism rewards accuracy and discourages frivolous challenges in both directions. Why use Curate: Earn by curating: users can profit by finding non-compliant entries in challengeable registries. In Stake Curate especially, successful challengers can recover their challenge deposit and win the item's stake. Launch your own verification market: projects can create a Curate list for almost any verifiable standard, define their own policy, deposits, challenge windows, arbitrator/court, and governance. The result is a fast, low-overhead registry that can power a public Curate view or a custom frontend. Why onchain-first matters: Deposit amounts, arbitration costs, MetaEvidence URIs, and challenge windows are all live onchain state — they change when registry governors update parameters. Any cached or estimated value is a liability: an agent that submits the wrong deposit amount will have its transaction revert. Always read live values before acting. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/kleros-curate