[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7N0TYETWBQRB7QDB0BXNF":3,"skill-same:01M7D7N0TYETWBQRB7QDB0BXNF":62},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7D7N0TYETWBQRB7QDB0BXNF","mpp-agent",null,"Pay HTTP 402 APIs via Machine Payments Protocol (MPP).","GrupoANDevelopment-m\u002Falberto-ai","GrupoANDevelopment-m","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257455179?v=4","01M7D69X2N2KEVN0SJF6WGM6SH","Antônio  Ndombe","01M7D69X3P5JTT8H8S904N3888",0,"MIT","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Foptional\u002Fpayments\u002Fmpp-agent\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mpp-agent\ndescription: Pay HTTP 402 APIs via Machine Payments Protocol (MPP).\nversion: 0.1.0\nauthor: Teknium (teknium1), Hermes Agent\nlicense: MIT\nplatforms: [linux, macos]\nmetadata:\n  hermes:\n    tags: [Payments, MPP, HTTP-402, Tempo, Stripe]\n    related_skills: [stripe-link-cli, stripe-projects]\n---\n\n# MPP Agent Skill\n\nWraps the Machine Payments Protocol (MPP, https:\u002F\u002Fmpp.dev) clients so Hermes can pay for per-request API access against servers that respond with `HTTP 402 Payment Required`.\n\nThree client options, all distributed via npm. Pick the lightest one that solves the user's need. Gated `[linux, macos]` while the broader payments tooling matures on Windows.\n\n## When to Use\n\n- A merchant API returns `HTTP 402` with a `www-authenticate` header — and the user wants to actually pay it, not just log the response.\n- The user asks to \"pay per request\", \"set up an agent wallet\", \"use Tempo \u002F Privy \u002F AgentCash\", or wants to discover MPP-priced services.\n- A Stripe Link spend has produced a Shared Payment Token (SPT) and the agent needs to attach it to the 402 challenge — in that flow, prefer `link-cli mpp pay` (see the `stripe-link-cli` skill).\n\n## Choosing a client\n\n| Tool | When | Setup |\n|---|---|---|\n| `link-cli` | User already has Stripe Link set up, or the 402 challenge advertises `method=\"stripe\"` | see the `stripe-link-cli` skill |\n| Tempo Wallet | MPP services with spend controls, service discovery | `tempo wallet login` |\n| Privy Agent CLI | Multi-chain wallets, browser-based funding | `privy-agent-wallets login` |\n| AgentCash | 300+ pre-priced APIs via one USDC.e balance | `npx agentcash onboard` |\n| `mppx` | Dev + debugging, smallest dep surface | `npm install -g mppx` then `mppx account create` |\n\nDefault: if the user already has Stripe Link configured or the 402 challenge specifies `method=\"stripe\"`, use `link-cli mpp pay` (the `stripe-link-cli` skill). Otherwise `mppx` for one-off paid calls and debugging, and Tempo Wallet when the user wants persistent spend controls.\n\n## Prerequisites\n\n- Node.js 20+ on `PATH`\n- A funded wallet (Tempo \u002F Privy \u002F AgentCash) OR an `mppx` account\n- For Tempo \u002F Privy \u002F AgentCash: follow their respective onboarding skills:\n  - `https:\u002F\u002Ftempo.xyz\u002FSKILL.md`\n  - `https:\u002F\u002Fagents.privy.io\u002Fskill.md`\n  - `https:\u002F\u002Fagentcash.dev\u002Fskill.md`\n\nUse `web_extract` to fetch any of those SKILL.md files if the user picks one.\n\n## Procedure (mppx, fastest path)\n\nRun all commands through the `terminal` tool.\n\n### 1. Install + create an account\n\n```\nnpm install -g mppx\nmppx account create\n```\n\nStore the resulting account credentials wherever the CLI tells you (the CLI writes them under its own config — do not paste them into the agent transcript).\n\n### 2. Inspect the merchant's 402 challenge\n\nIf the user gives you a URL, probe it first to confirm it actually speaks MPP:\n\n```\ncurl -i \u003Curl>\n```\n\nA real MPP 402 looks like:\n\n```\nHTTP\u002F1.1 402 Payment Required\nwww-authenticate: tempo amount=0.1 currency=...\n```\n\n### 3. Pay the request\n\n```\nmppx \u003Curl>\n```\n\nFor non-GET methods or request bodies:\n\n```\nmppx \u003Curl> --method POST --data '\u003Cjson>'\n```\n\n`mppx` handles the 402 challenge\u002Fcredential dance automatically and prints the merchant's actual response on success.\n\n### 4. Verify the receipt\n\n`mppx` attaches the receipt header automatically. To inspect:\n\n```\nmppx \u003Curl> -v\n```\n\n## Procedure (Tempo Wallet)\n\nThe Tempo Wallet skill at https:\u002F\u002Ftempo.xyz\u002FSKILL.md is the canonical reference; fetch it with `web_extract` and follow it. Headline:\n\n```\ntempo wallet login\ntempo wallet pay \u003Curl>\n```\n\nSpend controls and service discovery live in the wallet UI at https:\u002F\u002Fwallet.tempo.xyz.\n\n## Pitfalls\n\n- **`HTTP 402` without `method=\"stripe\"` cannot be paid by Stripe Link.** If the challenge advertises only Tempo \u002F other methods, use `mppx` (or whichever wallet matches) — Link will reject it. Conversely, if it advertises `method=\"stripe\"`, prefer Link via the `stripe-link-cli` skill so the spend goes through the user's approved card.\n- **Multiple challenges in one header.** `www-authenticate` may list several methods (e.g. `tempo, stripe`). The Link CLI's `mpp decode` will pick the Stripe one; `mppx` will pick Tempo. There's no single \"right\" client — pick by which wallet the user has funded.\n- **Zero-amount challenges.** Some MPP endpoints charge `$0.00` and just want a proof credential. These work without a funded wallet. Don't refuse them as \"broken.\"\n- **Wallet keys never enter agent context.** All four clients store keys under their own config dirs (or generate per-session ephemeral keypairs, in Privy's case). Do not `cat`\u002F`read_file` them.\n- **Server-side MPP is a different skill.** If the user wants to ADD 402 to their own API, this skill is wrong — point them at https:\u002F\u002Fmpp.dev\u002Fquickstart\u002Fserver and the `mppx\u002Fnextjs` \u002F `mppx\u002Fhono` \u002F `mppx\u002Fexpress` \u002F `mppx\u002Felysia` middlewares. A dedicated `mpp-server` skill may land later.\n\n## Verification\n\n```\nmppx --version && mppx account list\n```\n\nExit code 0 means installed and an account exists.\n","# MPP Agent Skill\n\nWraps the Machine Payments Protocol (MPP, https:\u002F\u002Fmpp.dev) clients so Hermes can pay for per-request API access against servers that respond with `HTTP 402 Payment Required`.\n\nThree client options, all distributed via npm. Pick the lightest one that solves the user's need. Gated `[linux, macos]` while the broader payments tooling matures on Windows.\n\n## When to Use\n\n- A merchant API returns `HTTP 402` with a `www-authenticate` header — and the user wants to actually pay it, not just log the response.\n- The user asks to \"pay per request\", \"set up an agent wallet\", \"use Tempo \u002F Privy \u002F AgentCash\", or wants to discover MPP-priced services.\n- A Stripe Link spend has produced a Shared Payment Token (SPT) and the agent needs to attach it to the 402 challenge — in that flow, prefer `link-cli mpp pay` (see the `stripe-link-cli` skill).\n\n## Choosing a client\n\n| Tool | When | Setup |\n|---|---|---|\n| `link-cli` | User already has Stripe Link set up, or the 402 challenge advertises `method=\"stripe\"` | see the `stripe-link-cli` skill |\n| Tempo Wallet | MPP services with spend controls, service discovery | `tempo wallet login` |\n| Privy Agent CLI | Multi-chain wallets, browser-based funding | `privy-agent-wallets login` |\n| AgentCash | 300+ pre-priced APIs via one USDC.e balance | `npx agentcash onboard` |\n| `mppx` | Dev + debugging, smallest dep surface | `npm install -g mppx` then `mppx account create` |\n\nDefault: if the user already has Stripe Link configured or the 402 challenge specifies `method=\"stripe\"`, use `link-cli mpp pay` (the `stripe-link-cli` skill). Otherwise `mppx` for one-off paid calls and debugging, and Tempo Wallet when the user wants persistent spend controls.\n\n## Prerequisites\n\n- Node.js 20+ on `PATH`\n- A funded wallet (Tempo \u002F Privy \u002F AgentCash) OR an `mppx` account\n- For Tempo \u002F Privy \u002F AgentCash: follow their respective onboarding skills:\n  - `https:\u002F\u002Ftempo.xyz\u002FSKILL.md`\n  - `https:\u002F\u002Fagents.privy.io\u002Fskill.md`\n  - `https:\u002F\u002Fagentcash.dev\u002Fskill.md`\n\nUse `web_extract` to fetch any of those SKILL.md files if the user picks one.\n\n## Procedure (mppx, fastest path)\n\nRun all commands through the `terminal` tool.\n\n### 1. Install + create an account\n\n```\nnpm install -g mppx\nmppx account create\n```\n\nStore the resulting account credentials wherever the CLI tells you (the CLI writes them under its own config — do not paste them into the agent transcript).\n\n### 2. Inspect the merchant's 402 challenge\n\nIf the user gives you a URL, probe it first to confirm it actually speaks MPP:\n\n```\ncurl -i \u003Curl>\n```\n\nA real MPP 402 looks like:\n\n```\nHTTP\u002F1.1 402 Payment Required\nwww-authenticate: tempo amount=0.1 currency=...\n```\n\n### 3. Pay the request\n\n```\nmppx \u003Curl>\n```\n\nFor non-GET methods or request bodies:\n\n```\nmppx \u003Curl> --method POST --data '\u003Cjson>'\n```\n\n`mppx` handles the 402 challenge\u002Fcredential dance automatically and prints the merchant's actual response on success.\n\n### 4. Verify the receipt\n\n`mppx` attaches the receipt header automatically. To inspect:\n\n```\nmppx \u003Curl> -v\n```\n\n## Procedure (Tempo Wallet)\n\nThe Tempo Wallet skill at https:\u002F\u002Ftempo.xyz\u002FSKILL.md is the canonical reference; fetch it with `web_extract` and follow it. Headline:\n\n```\ntempo wallet login\ntempo wallet pay \u003Curl>\n```\n\nSpend controls and service discovery live in the wallet UI at https:\u002F\u002Fwallet.tempo.xyz.\n\n## Pitfalls\n\n- **`HTTP 402` without `method=\"stripe\"` cannot be paid by Stripe Link.** If the challenge advertises only Tempo \u002F other methods, use `mppx` (or whichever wallet matches) — Link will reject it. Conversely, if it advertises `method=\"stripe\"`, prefer Link via the `stripe-link-cli` skill so the spend goes through the user's approved card.\n- **Multiple challenges in one header.** `www-authenticate` may list several methods (e.g. `tempo, stripe`). The Link CLI's `mpp decode` will pick the Stripe one; `mppx` will pick Tempo. There's no single \"right\" client — pick by which wallet the user has funded.\n- **Zero-amount challenges.** Some MPP endpoints charge `$0.00` and just want a proof credential. These work without a funded wallet. Don't refuse them as \"broken.\"\n- **Wallet keys never enter agent context.** All four clients store keys under their own config dirs (or generate per-session ephemeral keypairs, in Privy's case). Do not `cat`\u002F`read_file` them.\n- **Server-side MPP is a different skill.** If the user wants to ADD 402 to their own API, this skill is wrong — point them at https:\u002F\u002Fmpp.dev\u002Fquickstart\u002Fserver and the `mppx\u002Fnextjs` \u002F `mppx\u002Fhono` \u002F `mppx\u002Fexpress` \u002F `mppx\u002Felysia` middlewares. A dedicated `mpp-server` skill may land later.\n\n## Verification\n\n```\nmppx --version && mppx account list\n```\n\nExit code 0 means installed and an account exists.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":37,"description":7},"Teknium (teknium1), Hermes Agent","0.1.0",{"hermes":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"Payments","MPP","HTTP-402","Tempo","Stripe",[35,36],"stripe-link-cli","stripe-projects",[38,39],"linux","macos","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Foptional\u002Fpayments\u002Fmpp-agent","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m","https:\u002F\u002Fid-preview--d5bef06d-6c9e-4563-a3d4-a855b9d61610.lovable.app\u002F","Eu sou Antonio B. B. Ndombe \r\nEu sou um Pesquisador e desenvolvedor de sistema autonomia cognitivos, fundador de sistemas ODCs ( organismos digital conscientes)","2026-11-04 06:53:39",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill mpp-agent",{"tool":54,"command":55},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill mpp-agent",{"tool":57,"command":58},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill mpp-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Foptional\u002Fpayments\u002Fmpp-agent\u002FSKILL.md",true,[],[63,71,78,85,92,99],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DASC6FSCJP49JZBSK0NY1Z","nemoclaw-user-reference","Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-reference\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7DAS5S79VK33XFGVAM2TFWF","nemoclaw-user-overview","Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-overview\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DAS0PQEMET5MNGZ1ABSZVS","nemoclaw-user-monitor-sandbox","Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-monitor-sandbox\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DARQYGF7E9A69VH6S3CGN9","nemoclaw-user-manage-sandboxes","Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-sandboxes\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DARH8BRTG51TRCAB7YWDJ4","nemoclaw-user-manage-policy","Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-policy\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DARAT62M2VR37590VCZ5NS","nemoclaw-user-get-started","Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",[],[]]