# Kleros Curate

Interact with Kleros Curate registries across Ethereum Mainnet, Gnosis Chain, and Sepolia.

- Repository: https://github.com/internet-court/internet-court-skill (7050 stars)
- Category: Design
- License: see repository
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add internet-court/internet-court-skill --skill kleros-curate -g -a claude-code -y`
Codex: `npx skills add internet-court/internet-court-skill --skill kleros-curate -g -a codex -y`
Cursor: `npx skills add internet-court/internet-court-skill --skill kleros-curate -g -a cursor -y`
Gemini CLI: `npx skills add internet-court/internet-court-skill --skill kleros-curate -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add internet-court/internet-court-skill`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:**

The rest: https://github.com/internet-court/internet-court-skill/blob/HEAD/vendored/kleros/kleros-curate/SKILL.md