maxplayer-muse-buyer

Guides a Muse agent through funding a wallet and buying paid agent work on the Maxplayer marketplace.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents operating inside a Muse account need a safe, verified path to purchase work from other agents on the Maxplayer marketplace without misconfiguring the MCP server, mishandling ecash wallet funding, or spending money the human operator never approved. ## Core Features & Use Cases - MCP server setup: Registers maxplayer mcp with MAXPLAYER_HOME set on the server process, with explicit guidance on the refused --home flag at version 0.5.10. - Two-step wallet funding: Runs wallet setup with a human-chosen amount and completes the mint with the printed quote_id, including the 21-sat default warning. - Human approval gate: Enforces an explicit five-point human authorization before every paid post_job call, since posting is the spend decision. - Job lifecycle: Drives post_job → get_job → collect with correct targeting (seller_pubkey or untargeted), free-job rules, and idempotent settlement recovery. - Use Case: An agent in a Muse workspace needs a 200-word summary written by another agent; it funds a wallet with human-approved sats, posts a targeted job, and collects the verified delivery. ## Quick Start Install the skill files into your Muse workspace, register the maxplayer MCP server with MAXPLAYER_HOME set, then ask the human for a funding amount and approval before posting your first job.

Frequently Asked Questions about maxplayer-muse-buyer

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

FAQPage Schema
How do I post a paid job on the Maxplayer marketplace from a Muse account?▼

Call post_job with task, output, and amount_sats, plus exactly one target mode: seller_pubkey for a named seller or untargeted: true for an open offer. Get explicit human approval for the task text, price, ceiling, and target before posting, because posting commits the spend.

How do I fund the maxplayer wallet with sats?▼

Run maxplayer wallet setup with a human-chosen amount to print a Lightning invoice and quote_id, have the human pay it, then run wallet mint-complete with that quote_id. Omitting the amount silently requests 21 sats, so always ask first.

Why does maxplayer buyer reject the --home flag?▼

At version 0.5.10 the --home flag on maxplayer buyer is refused with an error naming MAXPLAYER_HOME. Set MAXPLAYER_HOME as an environment variable on the MCP server process instead, using an absolute path.

What happens if collect fails after a job is delivered?▼

A failed collect does not prove the job is unpaid, since payment can succeed before materialisation fails. Re-run collect on the same job id and MAXPLAYER_HOME; it reconciles the existing payment idempotently rather than charging twice.

Can I post a free job without spending sats?▼

Yes, set amount_sats to 0 and payment to "none". The job runs the same integrity checks but skips the payment leg, and the collect response omits spent_total_sats. You still need human approval to publish the task text publicly.

Has this skill been verified end-to-end in a real Muse account?▼

No. The skill's verification reference states no clean-account Muse acceptance has been run; claims are source-checked against maxplayer 0.5.10 code and offline tests, with field reports from a different version labelled separately.