Agent skill · software engineering · aiskillstore
kleros-ipfs-upload
Upload files to IPFS through the Kleros x402 payment gateway for $0.01 USDC on Base mainnet. Use specifically for Kleros ecosystem content such as dispute evidence, meta-evidence JSON, court, dispute, or arbitrator policies, Curate item metadata, juror justifications, and artifacts referenced by Kleros contracts or subgraphs through an IPFS CID. Trigger on Kleros, court, arbitrator, dispute, juror, Curate, Proof of Humanity, evidence, meta-evidence, or justification context. Do not use for generic IPFS uploads or CID requests without Kleros context; suggest a general pinning service instead. Explicit requests for this gateway, kleros-ipfs-gateway.fly.dev, kleros-api.netlify.app upload-to-ipfs, this skill, or an end-to-end test always qualify.
Why this skill is useful
Adds specific commands and integration patterns for uploading Kleros-related content to IPFS that the AI wouldn't reliably generate on its own.
What it needs
Requires typescript installed locally. Requires kleros account access. About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Kleros IPFS Upload (x402) Upload Kleros-ecosystem files to IPFS via https://kleros-ipfs-gateway.fly.dev/upload-to-ipfs, an x402-protected gateway that charges $0.01 USDC per upload on Base mainnet. The returned IPFS CID is content-addressable and dereferenceable through any IPFS gateway, and indexed by Kleros's Graph Node for subgraph discoverability. The gateway is a thin reverse-proxy in front of a Filebase-backed pinning service operated by Kleros. Every upload is pinned to Filebase indefinitely as long as Kleros runs the gateway — a reasonable assumption for artifacts the Kleros ecosystem itself depends on (the team has a strong incentive to keep this live), but not a substitute for a general-purpose pinning provider if the content is unrelated to Kleros. When to use this skill Trigger this skill when the user is uploading Kleros-ecosystem content: Dispute evidence attachments — screenshots, documents, contracts, transcripts. Meta-evidence JSON — the policy/spec referenced by a court or arbitrator smart contract at dispute creation. Court / dispute / arbitrator policies — JSON describing rules, fees, juror counts, appeal mechanics. Kleros Curate item metadata — JSON for items submitted to a Curate list (e.g. tokens, badges). Juror / arbitrator justifications — rulings, dissents, deliberation rationale. Any artifact whose CID will end up in a Kleros smart contract event, transaction, or subgraph. The user explicitly names this gateway (kleros-ipfs-gateway.fly.dev etc.) or this skill. The user is asking the agent to test, validate, or sanity-check this gateway or this skill itself (e.g. "smoke-test the Kleros IPFS gateway" / "verify pay-and-upload works"). A deliberate end-to-end test is a legitimate trigger even if no Kleros artifact is being uploaded for real use. When NOT to use this skill Generic "store this file on IPFS" / "get me a CID for X" requests with no Kleros relevance. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/kleros-ipfs-upload