Use it from a coding agent

Install

Four markdown files into .claude/skills/peal/ in your project. No package, no registry, no account.

curl -fsSL https://peal.network/skill/install.sh | sh

Then ask for what you want, in your own words:

use the peal skill to add sealed bid auctions to my marketplace
for the vintage camera listing, closing Monday at 6pm, reserve $50

What it does with that

The skill is a procedure, not a reference card. Given a sentence like the one above, the agent works through five steps, and the order matters because the shape of the integration depends on what is already in your codebase.

1. Surveys your application first. Whether there is a server or only a front end, where listings live, how state is stored, where the buy button is, and how you already handle time. It tells you what it found before it writes anything.
2. Pins the deadline. "Monday at 6pm" becomes an exact instant in your timezone, confirmed back to you in full before anything is created, because an auction that closes at the wrong hour cannot be undone.
3. Chooses where the code runs. Bids are sealed in the browser, because a plaintext bid must never reach a server, including yours. Your server creates the auction and reads results.
4. Writes it against your stack, from tested integrations for Next.js, Express, a static page, or a non-JavaScript backend.
5. Verifies before reporting success. It runs a script that opens a real auction with a short deadline, bids on it, waits for it to open and checks the board. About ninety seconds, and it exercises the whole path.

More examples that work: "collect quotes from my suppliers privately until Friday" · "let people vote on this without seeing a running tally" · "my agents keep front running each other, seal their actions until the round ends".

If piping a script to a shell is not something you do, read install.sh first. It is four curl commands and a mkdir; it writes nothing else and runs nothing else. Or copy the files yourself from /skill/SKILL.md.

Why a skill rather than documentation

An agent that has read a reference page can call the endpoints. That is not the hard part. The hard part is the handful of decisions that produce code which looks right and is wrong, and which no endpoint description would warn anybody about:

• Money as a float instead of integer minor units, which is fine until an auction is large enough for the rounding to matter and there is no arguing with a number that came out wrong in public.
• Sealing the digits of a bid without padding, which puts its magnitude on the wire. The ciphertext length ranks the whole auction for anyone watching, before a single bid opens.
• Sending the seller's private contact key to the server, which would let us read every contact detail the scheme exists to protect.
• Treating a slot count as a participant count, when batches are padded with decoys precisely so they are not the same number.
• Handling the null that every v1 read returns before the deadline as an error, or as an empty result, when it is the guarantee working.

The skill leads with those, because an agent that gets them right the first time is the whole point of installing it.

What is inside

• SKILL.md: the procedure above, the mistakes that produce code which looks right and is wrong, and the trust model stated plainly enough that an agent will not overclaim it to a user.
• reference/recipes.md: working integrations for Next.js, Express, a static page and a non-JavaScript backend, including the one that catches everybody: a URL import of the client works in a browser and throws in Node.
• reference/time.md: turning "Monday at 6pm" into an exact instant, with a timezone helper checked against daylight saving, a 45 minute offset and a negative one.
• reference/verify.md: the end to end script, and what each failure means when it does not pass.
• reference/api.md: every endpoint, its parameters and its responses.
• reference/auctions.md: the money rules, contact details and the check code.
• reference/errors.md: every error code and every limit, as tables.

Other tools

The files are plain markdown with YAML frontmatter, which is the Claude Code skill format. Anything that reads a project instruction file can use the same content: point it at .claude/skills/peal/SKILL.md, or paste it.

For a model with web access and no skill installed, llms.txt is the short version, written to be quoted.

An MCP server is on the roadmap, which is the other way an agent could reach this without any files at all.