maxplayer-debug-buying

Diagnose stuck Maxplayer buyer jobs using daemon status fields and wallet commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Maxplayer buyer job looks dead — a seller claimed but was never awarded, a claim lapsed, a seller says they were never paid, or your available budget is lower than your balance — the failures are silent. This Skill maps each symptom to the exact maxplayer buyer status field or wallet command that reveals the cause and the fix. ## Core Features & Use Cases - Status-driven diagnosis: Reads parked_awards, pending_award_attempts, unrecorded_confirmed_awards, reconcile, and wallet.mint from the buyer daemon's JSON snapshot to pinpoint silent failures. - Symptom playbooks: Covers parked awards from insufficient available budget, stuck reservations leaking budget headroom, wedged PENDING_SPENT proofs blocking all outbound payments, mint mismatches and the real-mint fence, and sellers owed money from unrecorded confirmed awards. - Use Case: A seller claims your job but the claim lapses at its 300s deadline with no error. Run maxplayer buyer status, find the award parked with reservation refused, fund the wallet with maxplayer wallet setup, and re-post the job. ## Quick Start Ask the agent to run maxplayer buyer status and diagnose why your posted job was claimed but never awarded.

Frequently Asked Questions about maxplayer-debug-buying

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

FAQPage Schema
Why was my Maxplayer job claimed but never awarded?▼

Check parked_awards in maxplayer buyer status. A non-empty entry means the money guard refused the reservation because available budget was below the job amount; an empty list means the claim was filtered out by the mint filter and never selected.

How do I debug a stuck Maxplayer buyer payment?▼

Run maxplayer buyer status for a JSON snapshot of the daemon state, then check maxplayer wallet balance for spendable sats. For wedged sends, run maxplayer wallet complete-locked followed by maxplayer wallet reconcile.

Why is my available budget lower than my wallet balance?▼

An in-flight award is holding a reservation against your balance, visible in pending_award_attempts. The hold releases at the deadline reconcile or when the seller reports a releasable failure; there is no manual release command.

What happens when buyer and seller use different Cashu mints?▼

With allow_real_mints = true (the default), the buyer attempts a cross-mint Lightning hop to a mint the seller accepts. With it false, you are pinned to dev mints and cannot pay sellers who only accept real mints.

A seller says they were never paid after I awarded the job. What do I check?▼

Look at unrecorded_confirmed_awards in maxplayer buyer status, which lists awards published to the relay but missing a local row. Run maxplayer collect <job_id> to fold in the accept, verify, and pay path for that job.