CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kleros-ipfs-upload

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable, well-sequenced operational guide with real validation checkpoints and verified bundle references. Its main weakness is token efficiency: the one-file-per-request and CID-reuse rules are each stated several times, and sections like the CDP integration and Examples could be moved to one-level-deep reference files to keep SKILL.md lean.

Suggestions

State the one-file-per-paid-upload and CID-reuse rules once in a single section and reference it from Quickstart, Request shape, and Response shape instead of restating them in each place.

Move the CDP server-account integration details (and optionally the Examples) into a one-level-deep reference file, keeping a brief pointer plus the minimal snippet in SKILL.md.

Trim the "Bundled" section — the scripts-are-optional framing is already established in Quickstart and does not need re-explanation.

DimensionReasoningScore

Conciseness

The one-file-per-paid-upload rule is repeated across four sections (Quickstart note, "One file per paid upload", "Request shape", "Response shape"), CID-reuse is restated three times, and the "Bundled" section re-explains the scripts-are-optional framing already given in Quickstart — mostly efficient but with clear tightening opportunities. Not 4: the duplication exceeds "minor instances that could be trimmed"; not 2: there is no padding that teaches concepts Claude already knows — nearly all content is operational.

3 / 5

Actionability

Fully executable throughout: runnable script invocations with env vars, three copy-paste pre-flight curls, complete inline TypeScript snippets for both raw-key and CDP paths, a local size-check command, and a step-by-step smoke test. Not 4: no executability gaps found; commands cover the common cases end-to-end.

5 / 5

Workflow Clarity

Sequences are clear with explicit validation checkpoints: free pre-flight before spending ("surface the error to the user before burning a key on a paid attempt"), a local size sanity-check before posting, and smoke-test step 4 verifying the pin by GETting the returned URL; the error table gives per-status recovery actions. Not 4: validation and feedback guidance are explicit at every risky step, and the batch/destructive cap does not apply since batching is explicitly forbidden and paid attempts are guarded by free checks.

5 / 5

Progressive Disclosure

All referenced bundle files (scripts/pay-and-upload.ts, scripts/pay-and-upload-cdp.ts, scripts/package.json) exist and are clearly signaled as optional, with one clearly-labeled external pointer (../feedback/SKILL.md) and well-organized sections. Not 5: almost nothing is split into one-level-deep reference files — the CDP integration details and Examples sections are inline and would fit naturally in separate references; not 3: the inline content is well-sectioned and easy to navigate, and scripts are appropriately external.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: concrete capabilities with cost and network details, comprehensive natural trigger terms, explicit what/when/when-not guidance, and a clear niche with an explicit exclusion clause. Third-person voice is used correctly throughout. No changes needed.

DimensionReasoningScore

Specificity

"Upload one Kleros-ecosystem file per paid request to IPFS through the Kleros x402 gateway for $0.01 USDC on Base mainnet" names the exact action, endpoint, price, and network, and adds the one-file-per-request and CID-reuse constraints — comprehensive concrete coverage with no meaningful gaps. Not 4: coverage of actions, cost, network, and constraints is complete rather than leaving minor gaps.

5 / 5

Completeness

Both "what" (paid per-file IPFS upload, $0.01 USDC on Base) and "when" ("Use for...", "Trigger when...") are explicitly stated with concrete trigger phrases, plus an explicit when-not-to clause. Not 4: the when-guidance is maximally explicit rather than merely adequate.

5 / 5

Trigger Term Quality

"Kleros, court, arbitrator, dispute, juror, Curate, Proof of Humanity, evidence, meta-evidence, justification" plus explicit gateway-name and test/validate triggers gives comprehensive natural-term coverage including synonyms and ecosystem-specific names. Not 4: essentially all natural variations a user would say are present.

5 / 5

Distinctiveness Conflict Risk

"Do NOT use for generic IPFS/CID requests without Kleros context; recommend a general-purpose pinning service" carves out a clear niche and explicitly disambiguates against general IPFS/pinning skills. Not 4: conflict risk is explicitly resolved rather than just reduced.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

internet-court/internet-court-skill

Path

vendored/kleros/kleros-ipfs-upload/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.