Is Kleros Ipfs Upload safe and trustworthy?

tashan scores Kleros Ipfs Upload on public evidence — see the measured signals. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Kleros Ipfs Upload?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

‹ The Index

Kleros Ipfs Upload

skill

Upload one Kleros-ecosystem file per paid request to IPFS through the Kleros x402 gateway for $0.01 USDC on Base mainnet. Use for dispute evidence, MetaEvidence JSON, court/dispute/arbitrator policies, Curate item metadata, juror justifications, or any artifact a Kleros contract or subgraph will reference by CID. Trigger when the request mentions Kleros, court, arbitrator, dispute, juror, Curate, Proof of Humanity, evidence, meta-evidence, justification, explicitly names this gateway or skill, or asks to test or validate it. Do NOT use for generic IPFS/CID requests without Kleros context; recommend a general-purpose pinning service. Each request accepts exactly one file: different bytes require separate paid uploads, while identical bytes should reuse one CID.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Other — see all ranked ›

Install (Claude Code):

cp -r kleros-ipfs-upload ~/.claude/skills/

Adoption: 1 repos

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

source ↗ · skill:kleros/kleros-ipfs-upload

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-03 · scorer s5 · how · something wrong here?