New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Kleros Curate

by internet-court in internet-court/internet-court-skill

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

MITAuto-check passedLegal & Compliance

Install Kleros Curate

skills CLI
$ npx skills add internet-court/internet-court-skill --skill kleros-curate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install internet-court/internet-court-skill kleros-curate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/vendored/kleros/kleros-curate .claude/skills/kleros-curate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
kleros-curate
GitHub stars
6.6k
Used in
1 other repo
Token cost
~3.8k tokens
SKILL.md length
1,707 words
Files
11 (incl. references)
Skills in repo
80
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 5 steps: A submitter proposes an item and locks a… → The item enters a challenge window… → If nobody challenges within the window,… → …
  • The user mentions Curate
  • SKILL.md covers Non-negotiables, Which Curate flavor are you…, Action index and Common workflows, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Kleros Curate is an agent skill from internet-court/internet-court-skill. 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…

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/light-curate.md`, `references/scout-registries.md` and `references/shared-abi-fragments.md`).

It sits in Legal & Compliance, covering Dispute resolution. It works with Ethereum. The repository describes itself as: The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, and dispute resolution as one open, catch-all… The licence is MIT.

When your agent uses it

  • The user mentions Curate
  • Light Curate/LightGeneralizedTCR/LGTCR
  • Stake Curate/PermanentGTCR/PGTCR
  • Token-curated registry/TCR

Example prompts

  • “/kleros-curate”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. A submitter proposes an item and locks a submission deposit as a pledge that the item complies with the
  2. The item enters a challenge window (configurable per registry, typically days to weeks). Anyone can review
  3. If nobody challenges within the window, the item is accepted and the submitter's deposit is returned in
  4. If a challenger believes the submission violates the policy, they lock a challenge deposit and open a
  5. The winner captures the loser's deposit as a bounty. The two-sided stake mechanism rewards accuracy and

What it can do on your machine

Read from SKILL.md and the folder at commit fa89195. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kleros Curate loads about 3.8k tokens when it runs, and up to ~30k if it reads all its reference files. Until then it costs about 228 tokens; SKILL.md has 1,707 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~228
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~30k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from internet-court/internet-court-skill at commit fa89195, republished under its MIT licence (© internet-court). 1,707 words, ~3,760 tokens.

Download SKILL.mdSave it as .claude/skills/kleros-curate/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
kleros-curate
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.

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.

Three contract flavors:

  • Light Curate (LGTCR) — LightGeneralizedTCR: optimistic challenge window, native-token deposits, the most widely deployed flavor. Used by the majority of Curate registries across Ethereum, Gnosis, and Sepolia.
  • Stake Curate (PGTCR) — PermanentGTCR: permanent ERC20 stake (not returned on item removal), Goldsky subgraph as primary data source, different status model (Submitted / Reincluded / Disputed / Absent
    • withdrawal flow). Identified by PGTCR-specific hallmark read calls (see references/stake-curate.md).
  • Scout — LGTCR contracts on Gnosis, specialized for 4 well-known registries (contract address tags, token lists, address tags, CDN mappings). Scout IS an overlay on LGTCR — it is not a separate contract type. Working with Scout always requires both references/scout-registries.md (Scout-specific context) and references/light-curate.md (LGTCR contract operations).

Non-negotiables

These rules apply across all Curate flavors. They are always in context; reference files may not repeat them.

  • Never guess / invent / approximate amounts, addresses, schemas, or parameters.
  • Onchain state + onchain logs are the source of truth for deposits, arbitration cost, challenge deposits, appeal status, and MetaEvidence URI.
  • Never assume a "standard token schema" — only the current MetaEvidence for that registry is authoritative.
  • Never rewrite the schema: item.json.columns must be copied verbatim from MetaEvidence; only values is dynamic.
  • Never upload or submit half-baked artifacts: no malformed JSON, broken MetaEvidence, placeholder values, unsupported field types, or unreachable policy files.
  • Never author unsupported MetaEvidence field types: for URL fields use type: "link", not url; validate every metadata.columns[].type before upload.
  • Production registries need a logo: do not deploy a production list with missing metadata.logoURI.
  • Strongly prefer PDF policy documents for registry policies. Use a non-PDF policy only after the user explicitly accepts the review and compatibility risk.
  • Never include "typical ranges" or estimates for deposits or fees — only report live-read values.
  • eth_getCode before declaring any address is or isn't a contract.

Which Curate flavor are you using?

Step 1 — Keyword scan (zero cost)

  • Mentions "Verify Your List", list verification, list-of-lists, frontend visibility, or making a deployed registry discoverable → Verification target is Light Curate (LGTCR) on all three supported networks → Read references/verify-your-list.md AND references/light-curate.md; do not ask the generic flavor question for the verification target. Detect the flavor of the registry being listed separately only when the live verification policy makes it relevant.

  • Mentions "Scout", "token list", "address tags", "CDN" → Scout (overlay on Light Curate — LGTCR contracts on Gnosis) → Read references/scout-registries.md AND references/light-curate.md (both required; Scout adds context on top of LGTCR operations)

  • Mentions "PGTCR", "Stake Curate", "PermanentGTCR", "Goldsky" → Stake Curate (PGTCR) → Read references/stake-curate.md

  • Mentions "Curate", "LGTCR", "LightGeneralizedTCR", "Light Curate", "addItem", "registry", or no flavor hint → Light Curate (LGTCR) (also the default) → Read references/light-curate.md

Step 2 — Ambiguous ("Curate" with no flavor hint)

  • Interactive session: ask one question — "Which Curate flavor? Light Curate (optimistic challenge window, native-token deposits), Stake Curate (permanent ERC20 stake, Goldsky subgraph), or Scout (4 Gnosis registries for contract/token tagging)?"

  • One-shot / non-interactive: default to Light Curate, then progressively correct:

    • If user provides a contract address: check if it matches one of the 4 known Scout registry addresses → load Scout overlay (read references/scout-registries.md AND references/light-curate.md)
    • If contract introspection reveals PGTCR hallmarks → pivot to Stake Curate (read references/stake-curate.md for hallmark calls)
    • Otherwise: proceed as Light Curate

Step 3 — Contract-type verification (if address provided)

See the flavor reference file for hallmark calls — SKILL.md does not embed function signatures here (contract-type detection belongs in each flavor's reference file).

Action index

Submit item to a registry → references/light-curate.md (LGTCR) or references/stake-curate.md (PGTCR)

Challenge / remove an item → flavor reference file

Submit evidence → flavor reference file

Fund an appeal → flavor reference file

Deploy a new registry (factory) → flavor reference file (factory section)

Fetch MetaEvidence (policy + schema) → references/shared-metaevidence.md

Compute deposits → references/shared-deposits.md

Build item.json → references/shared-item-json.md

Verify / make a deployed list visible on the Curate frontend -> references/verify-your-list.md

Upload to IPFS → references/shared-ipfs-upload.md

ABI / function signatures → references/shared-abi-fragments.md grep: grep -n "function\|event" references/shared-abi-fragments.md

Scout registry addresses + seed templates → references/scout-registries.md grep: grep -n "0x\|ATQ\|Address Tags\|Tokens\|CDN" references/scout-registries.md

Show full SKILL.md (788 more words)Show less

Common workflows

Submit an item (any flavor):

  1. references/shared-metaevidence.md — fetch schema (columns) and policy URI
  2. references/shared-item-json.md — build the item.json payload
  3. references/shared-ipfs-upload.md — upload item.json to IPFS, get CID
  4. references/shared-deposits.md — compute exact msg.value
  5. Flavor reference (light-curate.md or stake-curate.md) — send the addItem transaction

Challenge or remove an item:

  1. references/shared-metaevidence.md — fetch the applicable policy (clearing policy for removal; registration policy for challenge)
  2. references/shared-ipfs-upload.md — upload evidence JSON to IPFS
  3. references/shared-deposits.md — compute the challenge deposit
  4. Flavor reference — send the challenge or removeItem transaction

Deploy a new registry:

  1. references/shared-metaevidence.md - prepare valid MetaEvidence JSON (policy URI + column schema + logoURI)
  2. references/shared-ipfs-upload.md — upload MetaEvidence JSON to IPFS
  3. references/shared-abi-fragments.md - get known factory/arbitrator addresses and deploy ABI
  4. Flavor reference — call the factory deploy function
  5. references/verify-your-list.md - submit the new registry to the network's list-of-lists if frontend visibility is required

Frontend visibility after deployment:

  • Deploying a registry does not automatically make it visible on the Curate frontend.
  • Verifying a list gives it more visibility, makes it findable in the frontend, and marks it as a listed registry for users.
  • List-of-lists submission is not mandatory, but it is highly recommended for public registries. Skip it only when the list is intentionally stealth/private.
  • On Ethereum Mainnet, Gnosis Chain, and Sepolia, the canonical verification registries are Light Curate. Use references/verify-your-list.md for the chain-specific addresses and verification safeguards, then follow the standard LGTCR submission workflow. The registry being listed may be another Curate flavor if the live verification policy permits it.

Reference files

These 9 files are loaded on demand — only when needed for the current task. The action index above points to the right file for each operation. Loading an unnecessary reference file wastes context.

references/light-curate.md Light Curate (LightGeneralizedTCR) operations end-to-end: minimum inputs to ask the user, registry discovery via eth_getCode and hallmark reads, MetaEvidence retrieval, item.json construction, submit item, challenge / remove item, submit evidence, fund an appeal, deploy a new registry via factory. Read this file for any LGTCR contract interaction — and always alongside references/scout-registries.md when working on Scout.

references/stake-curate.md Stake Curate (PermanentGTCR) operations end-to-end: PGTCR hallmark detection (distinguishes PGTCR from LGTCR), ERC20 approval + stake deposit flow, Goldsky subgraph as primary MetaEvidence source with onchain fallback, PGTCR status model (Submitted / Reincluded / Disputed / Absent), item withdrawal flow, deploy factory. Read this file for any PGTCR contract interaction.

references/scout-registries.md Scout-specific overlay for the 4 known Gnosis registries (Tokens / Address Tags / Contract Domain Names / CDN). Contains: the 4 registry contract addresses used for address-based routing, seed-first submission pattern (fill from existing seed template, then submit), item.json templates per registry, image guidance, incentives information. Always read alongside references/light-curate.md — Scout IS LGTCR at the contract layer; this file adds Scout-only context on top.

references/verify-your-list.md Three-network workflow for making a deployed registry visible and verified in the Curate frontend. Contains the canonical Ethereum Mainnet, Gnosis Chain, and Sepolia LightGeneralizedTCR verification addresses, keeps the transaction target distinct from the registry being listed, and delegates to the standard LGTCR MetaEvidence, item.json, IPFS, deposit, simulation, and request-finalization procedures.

references/shared-metaevidence.md Shared MetaEvidence retrieval applicable to all Curate flavors: eth_getLogs method with the correct topic0, latest applicable MetaEvidence selection, LGTCR registration-vs-clearing classification, Goldsky subgraph path for PGTCR, MetaEvidence JSON structure, policy URI extraction, and MetaEvidence authoring guardrails. Read this file before fetching MetaEvidence for any registry, regardless of flavor.

references/shared-deposits.md Shared deposit computation covering all Curate flavors: submission deposit formula for LGTCR, challenge deposit formula for LGTCR, PGTCR stake vs arbitration deposit distinction (ERC20 stake is separate from the native-token arbitration cost), arbitrationCost() read pattern, msg.value assembly rule. Read this file before computing any deposit or constructing any transaction value.

references/shared-item-json.md Strict item.json construction rules: the columns + values schema format, verbatim-copy rule for columns (copy from MetaEvidence without modification - values is the only dynamic part), GTCR field type allowlist, forbidden aliases, placeholder rejection, pre-upload validation, and NewItem event sampling to verify field order before submitting. Read this file before building any item payload for any Curate registry.

references/shared-abi-fragments.md Shared ABI fragments for all Curate contracts: LightGeneralizedTCR read and write function signatures, PermanentGTCR read and write function signatures, IArbitrator interface ABI, key event signatures (MetaEvidence, ItemStatusChange, RequestSubmitted, etc.), known LightGTCRFactory addresses, and known Kleros V1 arbitrator addresses. Use grep -n "function\|event\|address" to navigate this file. Read when you need function selectors, calldata encoding, or event topic hashes.

references/shared-ipfs-upload.md Shared IPFS upload guidance for Curate workflows: durability rationale (external pins can disappear after onchain anchoring), required recommended path via the kleros-ipfs-upload skill and Kleros x402 endpoint, /ipfs/<CID> format rule (avoid double-slash when building URLs), and explicit risk warning for any user-approved external pinning source. Read before any IPFS upload step inside a Curate workflow.

Feedback

Something broken or confusing in this skill? Report it: fetch feedback/SKILL.md — helps maintainers fix what agents silently trip over.

© internet-court, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in vendored/kleros/kleros-curate of internet-court/internet-court-skill.

  • SKILL.md
  • 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

Open the folder on GitHubat commit fa89195

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in internet-court/internet-court-skill, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Kleros Curate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kleros Curate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kleros Curate this skillinternet-court/internet-court-skill6.6k1 repos~3.8kAutomated safety check: PassMIT
Litigation Deadline Calendarlawve-ai/awesome-legal-skills847—~4.3kAutomated safety check: PassMIT
Moot Court Simulation Buildercat-xierluo/legal-skills721—~1.4kAutomated safety check: PassCC-BY-NC-4.0
Intake To Draftstella/stella259—~537Automated safety check: PassApache-2.0
Finnish Legal Matter Intakeakunikkola/claude-for-legal-finland109—~2.1kAutomated safety check: PassMIT
Review SwarmSteelMorgan/1c-agent-based-dev-framework115—~7.9kAutomated safety check: PassCustom licence

Similar skills

  • Litigation Deadline Calendar

    lawve-ai/awesome-legal-skills

    Calendar litigation and arbitration deadlines from a scheduling order.

    847 GitHub stars~4.3k tokensUpdated 8 days ago
    Legal & ComplianceAuto-check passed

  • Moot Court Simulation Builder

    cat-xierluo/legal-skills

    Chinese-language skill that organizes a case file into a multi-role mock trial with judge, parties and clerk, producing a transcript, issue review and a to-strengthen list.

    721 GitHub stars~1.4k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed

  • Intake To Draft

    stella/stella

    Collects the facts of an unpaid invoice, then drafts a payment demand letter.

    259 GitHub stars~537 tokensUpdated today
    Legal & ComplianceAuto-check passed

  • Finnish Legal Matter Intake

    akunikkola/claude-for-legal-finland

    Starts a new Finnish legal matter by scanning documents for deadlines first, then summarizing parties and goals, interviewing for missing details and setting up a case workspace.

    109 GitHub stars~2.1k tokensUpdated 3 mo ago
    Legal & ComplianceAuto-check passed

  • Review Swarm

    SteelMorgan/1c-agent-based-dev-framework

    MUST use WHEN a code diff needs second-opinion or multi-model review: light tier = one eligible independent cross-family reviewer selected from enabled participants outside the caller family (also…

    115 GitHub stars~7.9k tokensUpdated 10 days ago
    Legal & ComplianceAuto-check passed

  • Persistence State

    AbdelStark/worldforge

    A skill your agent uses for WorldForge local state: run workspaces and artifacts under .worldforge/ (run manifests, evidence bundles, retention/prune), the WorldForge(statedir=...) directory, and…

    108 GitHub stars~921 tokensUpdated 22 days ago
    Legal & ComplianceAuto-check passed

More from internet-court/internet-court-skill

All 80 skills in this repo

  • Kleros IPFS Upload

    internet-court/internet-court-skill

    Uploads one Kleros-related file per paid request to IPFS through the Kleros x402 gateway for 0.01 USDC on Base, returning a CID that Kleros contracts can reference.

    6.6k GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check: notes

  • 0G Compute Network Guide

    internet-court/internet-court-skill

    Guides building on the 0G Compute Network, a decentralized GPU marketplace for AI inference and fine-tuning, with SDK patterns and CLI commands.

    6.6k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • PNP Prediction Markets on Solana

    internet-court/internet-court-skill

    Creates, trades and settles permissionless prediction markets on Solana with any SPL token as collateral, including social-media and custom-oracle markets.

    6.6k GitHub stars~7.5k tokensUpdated 1 mo ago
    Auto-check: notes

  • BNB Chain MCP Server

    internet-court/internet-court-skill

    Connects an agent to the BNB Chain MCP server to read blocks and contracts, move tokens and NFTs, register ERC-8004 agents and use Greenfield storage.

    6.6k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • GenLayer ERC-7710 Connector

    internet-court/internet-court-skill

    Specifies how a GenLayer Intelligent Contract decision about an agent's performance becomes an ERC-7710 revocation or policy change, through a relayer or bridge and an EVM controller.

    6.6k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

  • GenLayer Agent Supervision Adapter

    internet-court/internet-court-skill

    Specifies how a GenLayer Intelligent Contract should supervise an AI agent, with review rubrics, evidence schemas and continue, warn, constrain or revoke decisions.

    6.6k GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

Works with

Categories

Questions about Kleros Curate

What does Kleros Curate do?

Interact with Kleros Curate registries across Ethereum Mainnet, Gnosis Chain, and Sepolia. Kleros Curate is an agent skill from internet-court/internet-court-skill. Interact with Kleros Curate registries across Ethereum Mainnet, Gnosis Chain, and Sepolia.

When should I use Kleros Curate?

Kleros Curate fits situations like: the user mentions Curate; light Curate/LightGeneralizedTCR/LGTCR; stake Curate/PermanentGTCR/PGTCR; token-curated registry/TCR.

How do I install Kleros Curate in Claude Code?

Run `npx skills add internet-court/internet-court-skill --skill kleros-curate -a claude-code`. Or copy the skill folder (vendored/kleros/kleros-curate in internet-court/internet-court-skill) into .claude/skills/kleros-curate in your project. Claude Code loads it when a task matches its description.

How do I install Kleros Curate in Codex?

Run `npx skills add internet-court/internet-court-skill --skill kleros-curate -a codex`. Or copy the skill folder (vendored/kleros/kleros-curate in internet-court/internet-court-skill) into .agents/skills/kleros-curate in your project. Codex loads it when a task matches its description.

Can I use Kleros Curate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add internet-court/internet-court-skill --skill kleros-curate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kleros-curate, .gemini/skills/kleros-curate, .github/skills/kleros-curate and .opencode/skills/kleros-curate in your project.

What does Kleros Curate need to run?

SKILL.md names no scripts, command-line tools or credentials: Kleros Curate is instructions for the agent only.

Does Kleros Curate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Kleros Curate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Kleros Curate use?

Kleros Curate is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kleros Curate use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 26k tokens, read only when the agent opens those files.

What are the alternatives to Kleros Curate?

Skills that share tags, products or a category with Kleros Curate: Litigation Deadline Calendar (lawve-ai/awesome-legal-skills, 847 stars), Moot Court Simulation Builder (cat-xierluo/legal-skills, 721 stars), Intake To Draft (stella/stella, 259 stars) and Finnish Legal Matter Intake (akunikkola/claude-for-legal-finland, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kleros Curate?

internet-court (a GitHub organization) maintains it in internet-court/internet-court-skill, which has 6,551 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on August 19, 2026.

Source: internet-court/internet-court-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.