# Manage Kleros Curate Registries

Kleros Curate workflows require exact policy metadata, schemas, deposits, and chain-specific contract steps. This skill gives Claude, Codex, and Claude Code a structured process for safe registry preparation and review.

## Install

```bash
npx skillstore add internet-court/kleros-curate
```

## Metadata

- Status: approved
- Slug: internet-court-kleros-curate
- Skillstore revision: r1
- Version status: missing
- Tree hash: 37d52d68e9adabdeb6e226e41090ad46e67e1582357c32d5ff942dd13fcf2c74
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/kleros/kleros-curate
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, filesystem, external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/internet-court-kleros-curate
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-kleros-curate/manifest

## Capabilities

- Chooses the correct Curate flavor from user context or contract hallmarks.
- Explains Light Curate, Stake Curate, and Scout submission workflows.
- Guides MetaEvidence retrieval and item schema validation before upload.
- Computes required deposit inputs from live onchain reads instead of estimates.
- Prepares challenge, removal, evidence, appeal, deployment, and verification steps.
- Documents IPFS path rules for Curate artifacts and evidence files.

## Use Cases

- Submit a Registry Item: Prepare item metadata, validate schema fields, upload artifacts, and calculate the required transaction value.
- Challenge a Bad Entry: Review policy rules, prepare evidence, compute challenge deposits, and outline the challenge transaction.
- Launch a Public Registry: Prepare MetaEvidence, policy files, constructor parameters, deployment checks, and frontend verification steps.

## Prompt Templates

### Identify the Curate Flavor

```
I have a Kleros Curate registry task. Help me identify whether it uses Light Curate, Stake Curate, or Scout.
```

### Prepare an Item Submission

```
Help me submit an item to this Curate registry. Fetch the current MetaEvidence, validate the schema, and list each required value.
```

### Review a Challenge

```
Review this Curate item against the current policy. Tell me whether a challenge is justified and what evidence is needed.
```

### Plan a Registry Deployment

```
Plan a new Kleros Curate registry deployment. Check MetaEvidence requirements, deposits, arbitrator settings, IPFS artifacts, and verification steps.
```

## Limitations

- It does not execute transactions without separate wallet tooling and user approval.
- It depends on live chain, subgraph, gateway, and policy data being reachable.
- It cannot guarantee that jurors will accept a submitted item or challenge.
- It should not be used for non-Kleros registries or unrelated IPFS uploads.

## Best Practices

- Fetch live onchain state before computing deposits, fees, appeal windows, or MetaEvidence references.
- Copy MetaEvidence columns exactly and change only the item values required by the registry.
- Ask for explicit user approval before upload, challenge, deployment, or transaction submission.

## Anti Patterns

- Do not estimate deposits, schema fields, chain addresses, or challenge periods from memory.
- Do not submit placeholder JSON, malformed MetaEvidence, or inaccessible policy documents.
- Do not use generic IPFS uploads for Curate artifacts without explaining durability risks.

## Security Audit

- Audited at: 2026-07-19T10:35:39.661\+00:00
- Summary: Of 110 static findings, 109 are documentation or Markdown false positives. One relative link crosses the skill boundary, and semantic review found missing prompt isolation plus inconsistent approval gates for onchain actions. No prompt injection text was found in the packaged files.

## Stats

- Views: 0
- Downloads: 6
- Favorites: 1
- Popularity score: 0