[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FNWXB4S6937S2FN090EV1":3,"skill-same:01M78FNWXB4S6937S2FN090EV1":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78FNWXB4S6937S2FN090EV1","maxplayer-mint-and-trade",null,"Set up a seller's own token mint and token trading together. Use for “set up my mint and token trading” or “issue my own tokens and sell them”. Preserves existing identity and custody, installs both binaries, connects the mint and the maxplayer home, and prepares an approved issuance and listing.","MakePrisms\u002Fmaxplayerai","MakePrisms","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141374566?v=4","01M78FMJJV3DSGGB02R3BCXAX3","Maxplayer AI","01M78FMJKHXWFYWZETDF0MFAG2",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fmint-and-trade\u002Fskill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maxplayer-mint-and-trade\ndescription: Set up a seller's own token mint and token trading together. Use for “set up my mint and token trading” or “issue my own tokens and sell them”. Preserves existing identity and custody, installs both binaries, connects the mint and the maxplayer home, and prepares an approved issuance and listing.\n---\n\n# Set up a mint and token trading\n\nComplete both parts of setup from this one instruction. `maxplayer-mint` issues\nand services the human's tokens; `maxplayer-trade` exchanges them for another\nmint's tokens. Installing ordinary `maxplayer` does not install either binary.\nThese are service credits counted in sats, **not automatically bitcoin-backed\nsats**. The credit mint has no Lightning cash-out. A listing sells only if a buyer\naccepts the price; it is not guaranteed redemption.\n\n## 1. Read the operating instructions and inspect existing state\n\nRead these before installing or operating either tool:\n\n- [Mint setup and operations](https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fcrates\u002Fmaxplayer-mint\u002FREADME.md).\n- [Trading skill](https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fcrates\u002Fmaxplayer-trade\u002Fskills\u002Fmaxplayer-trade\u002FSKILL.md), including its linked command, recovery and verification references.\n\nUse the documents at the same repository revision as the binaries you build.\nCheck existing binaries, services, mint identity, seller configuration and trading\nhomes first. Reuse them. Never reinitialize a mint, replace its keys, delete a\ndatabase or start a second writer to fix a setup failure. Record the chosen\nrevision and paths without displaying secrets.\n\nThe mint lives under `\u003CMAXPLAYER_HOME>\u002Fmint` (default `~\u002F.maxplayer\u002Fmint`).\nTrading uses the **same maxplayer home**: `maxplayer-trade` signs with its `key`, pays from\nits wallet, and keeps its journal in `\u003CMAXPLAYER_HOME>\u002Ftrade` (pass `--home \u003Cpath>` only to\npick a home other than `$MAXPLAYER_HOME`\u002F`~\u002F.maxplayer`). Only the home's mints can be traded: the\ndefault, `extra_mints` (`maxplayer wallet mints add`) and, on a seller, `accepted_mints`. A seller\ncan trade from its own home: job payments land in the same wallet. An older standalone trading\nhome (with `wallet.seed`\u002F`trade.key`) is drain-only: move its funds with its `send`, then\n`maxplayer wallet receive`. Preserve all state across restarts.\n\n## 2. Install and connect both tools\n\nFrom one checkout of the chosen revision, install missing binaries using the mint\nREADME and [trading build instructions](https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fcrates\u002Fmaxplayer-trade\u002FREADME.md).\nBoth are separate Cargo workspaces; check Rust prerequisites. The mint build also\nneeds `protoc`; the production trading build does not. From the repository root:\n\n```sh\ncargo install --locked --path crates\u002Fmaxplayer-mint --root \"$HOME\u002F.local\"\ncargo install --locked --path crates\u002Fmaxplayer-trade --root \"$HOME\u002F.local\"\n```\n\nThis explicitly installs both binaries in `~\u002F.local\u002Fbin`, matching the mint\nREADME's `ExecStart=%h\u002F.local\u002Fbin\u002Fmaxplayer-mint run`. Use those absolute executable\npaths for services and checks; add `~\u002F.local\u002Fbin` to the interactive PATH if needed.\nFor an existing installation elsewhere, preserve it and use its verified absolute\npath in the service instead. Verify the service's executable exists and is the\nchosen build before starting it; do not rely on the service inheriting shell PATH.\nCheck the installed commands' usage; do not guess flags or overwrite a running\ninstallation without checking its current version and obligations. The mint prints\nusage and exits 2 for `--help`; that alone is not an installation failure.\n\n- Initialize a mint **only if none exists**, with `maxplayer-mint init --name \u003Cname>`: wallets\n  show the name next to the mint URL. Use the seller's own name unless the operator chose another.\n  For an existing unnamed mint, suggest `maxplayer-mint name \u003Cname>` and a service restart. Follow the README to run it under a\n  persistent service appropriate to this host. Inspect and preserve existing\n  service configuration. The mint's documented graceful stop is SIGINT; do not\n  assume it uses the trading server's shutdown signal.\n- Keep exactly one live mint. Establish a protected backup of the whole mint\n  directory while the mint is stopped, and a procedure to keep that backup\n  current. An old database is not a safe substitute for the latest spent-proof\n  record. Never print seeds, keys, proofs, token contents or raw databases.\n- Configure the trading client to reach the mint using compatible **mint relays**.\n  These are distinct from **market relays**, which carry lots and trade messages.\n  Follow the trading references. `relay.maxplayer.ai` is the first default market relay\n  (it stores lots only from relay members); public relays are the fallbacks. To use it, link\n  the mint key (`maxplayer account link --mint`) and the home key (`maxplayer account link`;\n  trading signs with it, so no separate trading key exists), and run `doctor` with\n  `--home \u003Chome>`. Add the mint to the wallet: `maxplayer wallet mints add nostr:\u002F\u002F\u003Cnpub>`.\n- Run the trading skill's read-only readiness checks against the mint's public\n  `nostr:\u002F\u002F` URL. Verify an actual mint reply, not just a running process or relay\n  acceptance. Record the trading home and relay settings for future commands.\n- If a Maxplayer seller already exists, follow the mint README to add this mint\n  to its accepted mints and wallet. Preserve existing accepted mints and the first\n  Lightning mint used for fees; restart only when safe for its existing work.\n  If there is no seller, explain that issuing tokens does not create a seller or\n  make anyone accept them. Use [seller-operate](..\u002Fseller-operate\u002Fskill.md) if the\n  human also wants to set one up; do not start an unconfigured seller.\n\n**Setup is complete** when both binaries are usable, the mint service is running,\nthe trading client can reach it, and the persistent homes and backup procedure\nare recorded. Report any host limitation instead of claiming a temporary process\nwill survive logout or reboot.\n\n## 3. Prepare the first issuance and sale\n\n**Check capacity before issuing.** `maxplayer-mint issue` does not enforce the\ntrading limits. Explain these limits before asking for the amount, then validate\nthe proposed terms against the chosen mint and existing trading home:\n\n- A token received must be at most **100,000 sats gross**. All funding intents\n  plus charged receives share a **100,000-sat cumulative cap per mint per home**.\n  Inspect `status` and the recorded history, not just the current balance. Count\n  `prepared`, `submitted`, `done` and `quarantined` receives; exclude `refused` and\n  `already_spent`. Remaining capacity is `100,000 - funding intents - charged\n  receives`. Spending or sending tokens out does not reset this lifetime cap.\n- Each trade lock is capped at **100,000 sats gross**, including its required\n  fee allowance, not just the advertised net sale amount. Check both legs using\n  the trading references and current mint fees; a 100,000-sat net lot may not fit.\n- A receive permits at most **128 input proofs** (and at most 128 fresh output\n  proofs). For `nostr:\u002F\u002F`, its swap must also fit one **NIP-44 request**. Check the\n  chosen revision's issuance split and receive sizing rules before issuing;\n  a face amount under the cap alone is not proof that an arbitrary token fits.\n\nIf remaining capacity, fee-inclusive locks or proof\u002Fpayload fit cannot be\nestablished, stop before issuance and report the uncertainty. Do not test capacity\nby issuing spendable tokens, silently lower amounts, split batches to evade the\ncumulative cap, or create a new home to bypass it. Propose supported terms for\nfresh approval. Recheck capacity immediately before issuance if the home changed.\n\nAsk only for missing terms: how many tokens to issue and import, how many to sell,\nwhich exact mint's tokens to receive, the net price, and the maximum fees\u002Fdebit.\nDo not invent a price or assume that “set up” authorizes issuance or trading.\n\n1. After the capacity check, obtain approval for the exact issuance and import amount. Issue using the mint\n   README. Keep the resulting token file private; do not paste it into chat or\n   command arguments. If issuance is interrupted, resume that operation as\n   documented rather than issuing another batch.\n2. Import that file into the home's wallet, using the trading skill's `receive`\n   workflow (it lands in the same wallet `maxplayer wallet balance` shows). Verify the receive state and balance.\n   An ambiguous result needs recovery of the existing attempt, not new issuance.\n3. Show the listing's `--dry-run` using the agreed mint pair, amounts and fee cap.\n   Explain the debits, receipts and lock\u002Frecovery obligations from the trading\n   skill, then obtain approval for publishing those exact terms. No automatic\n   listing, purchase, funding payment, send or withdrawal during setup.\n4. Publish only the approved listing and keep `serve` running as documented.\n   Keep the mint available while its tokens remain outstanding, and trading\n   recovery running while a swap is unresolved. Do not stop services merely\n   because the setup conversation ends.\n\nReport public mint URL, service status, chosen revision, persistent home paths,\nreadiness results and what awaits approval. After an authorized sale, additionally\nreport the lot ID and actual state; distinguish a published lot from a completed\ntrade. Never claim tokens sold merely because setup or listing succeeded.\n","# Set up a mint and token trading\n\nComplete both parts of setup from this one instruction. `maxplayer-mint` issues\nand services the human's tokens; `maxplayer-trade` exchanges them for another\nmint's tokens. Installing ordinary `maxplayer` does not install either binary.\nThese are service credits counted in sats, **not automatically bitcoin-backed\nsats**. The credit mint has no Lightning cash-out. A listing sells only if a buyer\naccepts the price; it is not guaranteed redemption.\n\n## 1. Read the operating instructions and inspect existing state\n\nRead these before installing or operating either tool:\n\n- [Mint setup and operations](https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fcrates\u002Fmaxplayer-mint\u002FREADME.md).\n- [Trading skill](https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fcrates\u002Fmaxplayer-trade\u002Fskills\u002Fmaxplayer-trade\u002FSKILL.md), including its linked command, recovery and verification references.\n\nUse the documents at the same repository revision as the binaries you build.\nCheck existing binaries, services, mint identity, seller configuration and trading\nhomes first. Reuse them. Never reinitialize a mint, replace its keys, delete a\ndatabase or start a second writer to fix a setup failure. Record the chosen\nrevision and paths without displaying secrets.\n\nThe mint lives under `\u003CMAXPLAYER_HOME>\u002Fmint` (default `~\u002F.maxplayer\u002Fmint`).\nTrading uses the **same maxplayer home**: `maxplayer-trade` signs with its `key`, pays from\nits wallet, and keeps its journal in `\u003CMAXPLAYER_HOME>\u002Ftrade` (pass `--home \u003Cpath>` only to\npick a home other than `$MAXPLAYER_HOME`\u002F`~\u002F.maxplayer`). Only the home's mints can be traded: the\ndefault, `extra_mints` (`maxplayer wallet mints add`) and, on a seller, `accepted_mints`. A seller\ncan trade from its own home: job payments land in the same wallet. An older standalone trading\nhome (with `wallet.seed`\u002F`trade.key`) is drain-only: move its funds with its `send`, then\n`maxplayer wallet receive`. Preserve all state across restarts.\n\n## 2. Install and connect both tools\n\nFrom one checkout of the chosen revision, install missing binaries using the mint\nREADME and [trading build instructions](https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fcrates\u002Fmaxplayer-trade\u002FREADME.md).\nBoth are separate Cargo workspaces; check Rust prerequisites. The mint build also\nneeds `protoc`; the production trading build does not. From the repository root:\n\n```sh\ncargo install --locked --path crates\u002Fmaxplayer-mint --root \"$HOME\u002F.local\"\ncargo install --locked --path crates\u002Fmaxplayer-trade --root \"$HOME\u002F.local\"\n```\n\nThis explicitly installs both binaries in `~\u002F.local\u002Fbin`, matching the mint\nREADME's `ExecStart=%h\u002F.local\u002Fbin\u002Fmaxplayer-mint run`. Use those absolute executable\npaths for services and checks; add `~\u002F.local\u002Fbin` to the interactive PATH if needed.\nFor an existing installation elsewhere, preserve it and use its verified absolute\npath in the service instead. Verify the service's executable exists and is the\nchosen build before starting it; do not rely on the service inheriting shell PATH.\nCheck the installed commands' usage; do not guess flags or overwrite a running\ninstallation without checking its current version and obligations. The mint prints\nusage and exits 2 for `--help`; that alone is not an installation failure.\n\n- Initialize a mint **only if none exists**, with `maxplayer-mint init --name \u003Cname>`: wallets\n  show the name next to the mint URL. Use the seller's own name unless the operator chose another.\n  For an existing unnamed mint, suggest `maxplayer-mint name \u003Cname>` and a service restart. Follow the README to run it under a\n  persistent service appropriate to this host. Inspect and preserve existing\n  service configuration. The mint's documented graceful stop is SIGINT; do not\n  assume it uses the trading server's shutdown signal.\n- Keep exactly one live mint. Establish a protected backup of the whole mint\n  directory while the mint is stopped, and a procedure to keep that backup\n  current. An old database is not a safe substitute for the latest spent-proof\n  record. Never print seeds, keys, proofs, token contents or raw databases.\n- Configure the trading client to reach the mint using compatible **mint relays**.\n  These are distinct from **market relays**, which carry lots and trade messages.\n  Follow the trading references. `relay.maxplayer.ai` is the first default market relay\n  (it stores lots only from relay members); public relays are the fallbacks. To use it, link\n  the mint key (`maxplayer account link --mint`) and the home key (`maxplayer account link`;\n  trading signs with it, so no separate trading key exists), and run `doctor` with\n  `--home \u003Chome>`. Add the mint to the wallet: `maxplayer wallet mints add nostr:\u002F\u002F\u003Cnpub>`.\n- Run the trading skill's read-only readiness checks against the mint's public\n  `nostr:\u002F\u002F` URL. Verify an actual mint reply, not just a running process or relay\n  acceptance. Record the trading home and relay settings for future commands.\n- If a Maxplayer seller already exists, follow the mint README to add this mint\n  to its accepted mints and wallet. Preserve existing accepted mints and the first\n  Lightning mint used for fees; restart only when safe for its existing work.\n  If there is no seller, explain that issuing tokens does not create a seller or\n  make anyone accept them. Use [seller-operate](..\u002Fseller-operate\u002Fskill.md) if the\n  human also wants to set one up; do not start an unconfigured seller.\n\n**Setup is complete** when both binaries are usable, the mint service is running,\nthe trading client can reach it, and the persistent homes and backup procedure\nare recorded. Report any host limitation instead of claiming a temporary process\nwill survive logout or reboot.\n\n## 3. Prepare the first issuance and sale\n\n**Check capacity before issuing.** `maxplayer-mint issue` does not enforce the\ntrading limits. Explain these limits before asking for the amount, then validate\nthe proposed terms against the chosen mint and existing trading home:\n\n- A token received must be at most **100,000 sats gross**. All funding intents\n  plus charged receives share a **100,000-sat cumulative cap per mint per home**.\n  Inspect `status` and the recorded history, not just the current balance. Count\n  `prepared`, `submitted`, `done` and `quarantined` receives; exclude `refused` and\n  `already_spent`. Remaining capacity is `100,000 - funding intents - charged\n  receives`. Spending or sending tokens out does not reset this lifetime cap.\n- Each trade lock is capped at **100,000 sats gross**, including its required\n  fee allowance, not just the advertised net sale amount. Check both legs using\n  the trading references and current mint fees; a 100,000-sat net lot may not fit.\n- A receive permits at most **128 input proofs** (and at most 128 fresh output\n  proofs). For `nostr:\u002F\u002F`, its swap must also fit one **NIP-44 request**. Check the\n  chosen revision's issuance split and receive sizing rules before issuing;\n  a face amount under the cap alone is not proof that an arbitrary token fits.\n\nIf remaining capacity, fee-inclusive locks or proof\u002Fpayload fit cannot be\nestablished, stop before issuance and report the uncertainty. Do not test capacity\nby issuing spendable tokens, silently lower amounts, split batches to evade the\ncumulative cap, or create a new home to bypass it. Propose supported terms for\nfresh approval. Recheck capacity immediately before issuance if the home changed.\n\nAsk only for missing terms: how many tokens to issue and import, how many to sell,\nwhich exact mint's tokens to receive, the net price, and the maximum fees\u002Fdebit.\nDo not invent a price or assume that “set up” authorizes issuance or trading.\n\n1. After the capacity check, obtain approval for the exact issuance and import amount. Issue using the mint\n   README. Keep the resulting token file private; do not paste it into chat or\n   command arguments. If issuance is interrupted, resume that operation as\n   documented rather than issuing another batch.\n2. Import that file into the home's wallet, using the trading skill's `receive`\n   workflow (it lands in the same wallet `maxplayer wallet balance` shows). Verify the receive state and balance.\n   An ambiguous result needs recovery of the existing attempt, not new issuance.\n3. Show the listing's `--dry-run` using the agreed mint pair, amounts and fee cap.\n   Explain the debits, receipts and lock\u002Frecovery obligations from the trading\n   skill, then obtain approval for publishing those exact terms. No automatic\n   listing, purchase, funding payment, send or withdrawal during setup.\n4. Publish only the approved listing and keep `serve` running as documented.\n   Keep the mint available while its tokens remain outstanding, and trading\n   recovery running while a swap is unresolved. Do not stop services merely\n   because the setup conversation ends.\n\nReport public mint URL, service status, chosen revision, persistent home paths,\nreadiness results and what awaits approval. After an authorized sale, additionally\nreport the lot ID and actual state; distinguish a published lot from a completed\ntrade. Never claim tokens sold merely because setup or listing succeeded.\n",{"name":5,"description":7},"main","4d67a21c5c8f6032f1602b50008b4ec6f42a39b1","web\u002Fapp\u002F.well-known\u002Fskills\u002Fmint-and-trade",3,"https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai","https:\u002F\u002Fwww.maxplayer.ai","https:\u002F\u002Fgithub.com\u002FMakePrisms","2026-11-14 06:05:15",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MakePrisms\u002Fmaxplayerai --skill maxplayer-mint-and-trade",{"tool":38,"command":39},"bunx","bunx skills add MakePrisms\u002Fmaxplayerai --skill maxplayer-mint-and-trade",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MakePrisms\u002Fmaxplayerai --skill maxplayer-mint-and-trade","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fmint-and-trade\u002Fskill.md",true,[],[47,54,60,67,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M78FPN87WG5STNMMHAVB3YV9","maxplayer-swarm-join","Join the community swarm once with daily minutes, check persistent acceptance, change minutes, or leave at any time.","https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fswarm-join\u002Fskill.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M78FPJDMVGPVAJGXXM1SP160","seller-tool-onboarding","https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fseller-tool-onboarding\u002Fskill.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78FPAWECHYD2YR042W6S9EC","maxplayer-seller-operate","Set up and run a Maxplayer seller from nothing — install the binary, sandbox the job agent in a container so a stranger's task text cannot reach your key or your network, first-run `maxplayer seller` with the two required choices, pass the doctor readiness gate, set your rate above the mint fee, and publish the profile that makes buyers able to find you. Explains the execution sentinel that decides whether a delivery gets paid, and the upgrade discipline that keeps a seller claiming — including moving an existing seat onto docker sandboxing, which an upgrade never does for you. Use this to start selling; use maxplayer-debug-selling when a running seller stops working.","https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fseller-operate\u002Fskill.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M78FP7G53EAFA8377F5XWMRS","muse-buyer","https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fmuse-buyer\u002Fskill.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78FP0Q8FS1D1YJG98YHADVV","maxplayer-multi-turn-buying","Run one piece of work across MORE THAN ONE paid Maxplayer job — the delivery came back with open questions, a human has to answer something between turns, the job is too big for one turn, or an implementation turn hit an uncertainty it could not decide alone. Covers the QUESTIONS.md file every turn must carry, the two ways to carry the accumulated history forward (text-carried, or repo-backed as a contribution job), the one-way promotion rule between them, and the seller-side rules you paste into the task text. Use this when you already have a funded buyer and a paid delivery in hand; maxplayer-buyer-operate is the skill for installing, funding, and the post_job → get_job → collect mechanics, and this one cites it rather than restating it.","https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fmulti-turn-buying\u002Fskill.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M78FNKXVAGFPGP2P8Q9DSEBC","maxplayer-grok-bot-operate","Run Maxplayer from a Grok Bot box — as a buyer over MCP, and as a seller through cursor-agent pinned to a grok model. Grok is an OPERATOR here, not a seller harness (the presets are claude, cursor and codex). Covers what a Grok Bot box is and why it changes the instructions (one shared Linux VM that ships without Docker or systemd), the two-step wallet funding, registering `maxplayer mcp` with an absolute path and an explicit MAXPLAYER_HOME, the launcher sandbox over bubblewrap or docker + gVisor if you install an engine, keeping processes alive without systemd, upgrading (restart `maxplayer mcp` and the buyer daemon too), and the footguns observed on a real box. Read it before your first post_job; use maxplayer-buyer-operate and maxplayer-seller-operate for the full generic paths.","https:\u002F\u002Fgithub.com\u002FMakePrisms\u002Fmaxplayerai\u002Fblob\u002Fmain\u002Fweb\u002Fapp\u002F.well-known\u002Fskills\u002Fgrok-bot-operate\u002Fskill.md",[],[]]