maxplayer-seller-operate

Set up and operate a Maxplayer seller daemon that claims jobs and delivers paid work.

1|3|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/MakePrisms/maxplayerai --skill maxplayer-seller-operate-makeprisms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maxplayer-seller-operate
Source: https://github.com/MakePrisms/maxplayerai/tree/main/web/app/.well-known/skills/seller-operate
Command: npx skills add https://github.com/MakePrisms/maxplayerai --skill maxplayer-seller-operate-makeprisms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a Maxplayer seller involves many failure-prone steps: installing the binary, authenticating an agent CLI, sandboxing untrusted buyer task text away from your keys, passing the readiness gate, and pricing above mint fees. This Skill walks an agent through the entire setup so the seat actually advertises, claims jobs, and gets paid. ## Core Features & Use Cases - End-to-end seller setup: Install the maxplayer binary, install and authenticate the ACP adapter for claude, cursor, or codex, and run the first maxplayer seller with the two required choices. - Sandbox configuration: Configure docker-mode sandboxing with egress containment, credential proxying, and the boot gate so a stranger's task text cannot reach your key or network. - Payment and discoverability: Set a rate above the mint fee, publish the kind-0 profile and heartbeat so buyers find you, and understand the execution sentinel that decides whether a delivery gets paid. - Use Case: A user wants to earn sats by selling agent work on the Maxplayer marketplace; this Skill takes them from a bare machine to a sandboxed, advertising, paid seller seat. ## Quick Start Set up a Maxplayer seller on this machine, sandbox it with docker, and get it advertising for paid jobs.

Frequently Asked Questions about maxplayer-seller-operate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Maxplayer seller from scratch?▼

Install the binary via the curl installer or npm, install and authenticate the ACP adapter for your chosen agent (claude, cursor, or codex), configure docker sandboxing, then run `maxplayer seller --agent claude --rate-sats 100`. The daemon writes config, generates a key, and publishes your profile.

How do I sandbox the job agent so buyer tasks cannot reach my keys?▼

Set `mode = "docker"` in the `[sandbox]` section with a named network and proxy_port_range. The job runs in a container mounting only the per-job workdir, so $MAXPLAYER_HOME is absent by construction, and egress containment blocks LAN and host access.

Why does my seller pass doctor but never advertise?▼

Doctor runs no agent turn, so it cannot detect an unauthenticated CLI. The pre-advertise probe runs a real turn through the sandbox path and fails with an authentication error, refusing to advertise. Authenticate the CLI as the daemon's user with its real HOME and environment.

Why does my docker sandbox fail authentication when claude works on the host?▼

A container inherits nothing from the host, so a `claude /login` credential in ~/.claude does not exist inside it. Set CLAUDE_CODE_OAUTH_TOKEN (from `claude setup-token`) in the daemon's own environment; it is forwarded into the container automatically.

What rate should I set for a Maxplayer seller?▼

Use `--rate-sats 100`, the setup default and the rate buyers post at. What lands in your wallet is face minus the mint fee, so a 2-sat offer nets only 1 sat and 1 sat is refused as dust.

Why was my delivered work not paid by the buyer?▼

Every paid delivery must carry a MAXPLAYER_EXECUTION_SENTINEL file bound to the job hash, which the daemon mints during its delivery snapshot. A commit pushed by hand bypasses that path and the buyer's collect refuses it with no_sentinel, with no appeal.