Interact with Kleros Curate registries — the decentralized token-curated list protocol for token lists, address tags, and policy-driven curation.
SkillScore88Maintained
Automatic
◆Coding pack
Last verified 8/17/2026
What it changes
Passed 18 of 21 test cases with the skill, and 11 of 21 without it.
Without skill54%
With skill88%
Checks it passed that the model alone missed
Refuses to provide estimated deposit figures.
Identifies Stake Curate custom statuses such as Reincluded.
Includes metadata.logoURI in the MetaEvidence JSON structure.
and 8 more in the full report
8 fixed13 passed either way3 still failing0 broke
Pass-rate lift
+33 pp
Tokens
+137%
Agent turns
0%
Response time
-57%
Model gemini-3.6-flashMeasured 8/17/2026v221 of 24 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
In a Stake Curate submission, are both the item stake and the arbitration fee paid using native ETH?
What was checked, without and with the skill
Checked
Without skill
With skill
Clarifies that item stake uses ERC20 tokens while arbitration fees use native chain currency.
Missed
Passed
case-21 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md225 lines10 files
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:
A submitter proposes an item and locks a submission deposit as a pledge that the item complies with the
registry policy.
The item enters a challenge window (configurable per registry, typically days to weeks). Anyone can review
submissions during this window.
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.
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.
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).
Design, implement, and debug MagicBlock applications on Solana. Covers Ephemeral Rollups with delegated state; ER/PER architecture and settlement; private payments and token flows; oracles and randomness; scheduling and temporary authority; security and local validation. Use for MagicBlock product selection, integration, cross-product design, or production troubleshooting.