Agent skill · AI & Agents

kleros-curate

Interact with Kleros Curate registries — the decentralized token-curated list protocol for token lists, address tags, and policy-driven curation. Use this skill when the user mentions Curate, Light Curate, LightGeneralizedTCR, LGTCR, LightCurate, Stake Curate, PermanentGTCR, PGTCR, Scout, token-curated registry, TCR, curated list, decentralized registry, registry, token list, address tags, CDN tags, Goldsky, or Solidity functions addItem, removeItem, challengeItem, challengeRequest. Covers all three flavors — Light Curate (LGTCR, optimistic challenge window), Stake Curate (PGTCR, permanent ERC

Internet Court1,389★ · +222/wk · 1 repos on radarProfile →
claude-codecodexNOASSERTION
Install
npx skills add internet-court/internet-court-skill --skill kleros-curate --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 11
SKILL.md size: 14 KB
Bundled scripts: none
Path: vendored/kleros/kleros-curate/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,536 · +147 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 r

What's inside
Steps it walks through
  1. Non-negotiables
  2. Which Curate flavor are you using?
  3. Action index
  4. Common workflows
  5. Reference files
  6. Feedback
Ships with 10 files
  • LICENSE
  • references/light-curate.md
  • references/scout-registries.md
  • references/shared-abi-fragments.md
  • references/shared-deposits.md
  • references/shared-ipfs-upload.md
  • references/shared-item-json.md
  • references/shared-metaevidence.md
  • references/stake-curate.md
  • references/verify-your-list.md
More from internet-court-skill
All skills →
About this skill
What does the kleros-curate skill do?

Interact with Kleros Curate registries — the decentralized token-curated list protocol for token lists, address tags, and policy-driven curation. Use this skill when the user mentions Curate, Light Curate, LightGeneralizedTCR, LGTCR, LightCurate, Stake Curate, PermanentGTCR, PGTCR, Scout, token-curated registry, TCR, curated list, decentralized registry, registry, token list, address tags, CDN tags, Goldsky, or Solidity functions addItem, removeItem, challengeItem, challengeRequest. Covers all three flavors — Light Curate (LGTCR, optimistic challenge window), Stake Curate (PGTCR, permanent ERC

How do I install it?

Run `npx skills add internet-court/internet-court-skill --skill kleros-curate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From internet-court/internet-court-skill, a repository with 1,536 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going