{"id":"02fcd640-189b-4542-81a2-52e6dcf955ff","entityType":"agent","slug":"clawhub-bubblevan-stablepay-agent-bootstrap","name":"StablePay Agent Bootstrap","canonicalUrl":"https://www.xpersona.co/agent/clawhub-bubblevan-stablepay-agent-bootstrap","canonicalPath":"/agent/clawhub-bubblevan-stablepay-agent-bootstrap","generatedAt":"2026-10-11T07:38:56.530Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T05:14:41.456Z","emptyReason":null},"description":"Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. Skill: StablePay Agent Bootstrap Owner: bubblevan Summary: Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. Tags: latest:1.4.0, mcp:1.4.0, payment:1.4.0, stablepay:1.4.0, web3:1.4.0 Version history: v1.4.0 | 2026-07-09T16:19:08.178Z | user Initial release v1.3.0 | 2026-07-09T15:46:48.699Z | user Initial release v1.2.0 | 2026-07-09T14:05:35.931Z | user Initial releas","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s1752nbybn39bye7hqb66b0bgh83rftj:stablepay-agent-bootstrap","sourceUrl":"https://clawhub.ai/bubblevan/stablepay-agent-bootstrap","homepage":"https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/bubblevan/stablepay-agent-bootstrap","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. Skill: StablePay Agent Bootstrap Owner: bubblevan Summary: "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:14:41.456Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:14:41.456Z","emptyReason":null},"stars":null,"forks":null,"downloads":1149,"packageName":null,"latestVersion":"1.4.0","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:14:41.395Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T05:14:41.456Z","lastCrawledAt":"2026-10-11T05:14:41.395Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T05:14:41.395Z","lastVerifiedAt":null,"highlights":[{"version":"1.4.0","createdAt":"2026-07-09T16:19:08.178Z","changelog":"Initial release","fileCount":3,"zipByteSize":4071},{"version":"1.3.0","createdAt":"2026-07-09T15:46:48.699Z","changelog":"Initial release","fileCount":3,"zipByteSize":3844},{"version":"1.2.0","createdAt":"2026-07-09T14:05:35.931Z","changelog":"Initial release","fileCount":3,"zipByteSize":4814},{"version":"1.1.0","createdAt":"2026-07-09T13:58:32.670Z","changelog":"Initial release","fileCount":3,"zipByteSize":5337},{"version":"1.0.0","createdAt":"2026-07-09T12:18:57.677Z","changelog":"Initial release","fileCount":3,"zipByteSize":5043}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s1752nbybn39bye7hqb66b0bgh83rftj:stablepay-agent-bootstrap","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:38:56.529Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-bubblevan-stablepay-agent-bootstrap/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T05:14:41.456Z","emptyReason":null},"readme":"Skill: StablePay Agent Bootstrap\n\nOwner: bubblevan\n\nSummary: Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor.\n\nTags: latest:1.4.0, mcp:1.4.0, payment:1.4.0, stablepay:1.4.0, web3:1.4.0\n\nVersion history:\n\nv1.4.0 | 2026-07-09T16:19:08.178Z | user\n\nInitial release\n\nv1.3.0 | 2026-07-09T15:46:48.699Z | user\n\nInitial release\n\nv1.2.0 | 2026-07-09T14:05:35.931Z | user\n\nInitial release\n\nv1.1.0 | 2026-07-09T13:58:32.670Z | user\n\nInitial release\n\nv1.0.0 | 2026-07-09T12:18:57.677Z | user\n\nInitial release\n\nArchive index:\n\nArchive v1.4.0: 3 files, 4071 bytes\n\nFiles: skill-card.md (2313b), SKILL.md (6208b), _meta.json (144b)\n\nFile v1.4.0:SKILL.md\n\n---\nname: stablepay-agent-bootstrap\nversion: 1.4.0\nauthor: Bubblevan\ndescription: Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor.\ntags:\n  - stablepay\n  - onboarding\n  - cli\n  - mcp\ncategory: Developer Tools\n---\n\n# StablePay Setup Skill\n\nUse this file as the only required entrypoint. Do not ask for extra docs before starting.\n\n## Success Condition\n\nLeave the environment in one of these states:\n\n1. StablePay is installed and `doctor` works.\n2. onboarding is complete and at least one follow-up command works.\n3. onboarding is paused on a real external step, and the exact resume command is provided.\n\n## Surface Model\n\n- `CLI` is the bootstrap, repair, and release-validation surface.\n- `MCP` is the ongoing in-agent runtime surface.\n- First-time setup: use `CLI` first.\n- After CLI succeeds: optionally add `MCP`.\n\n## First Step: Detect OS\n\nDetect the shell environment before choosing commands.\n\n- Windows PowerShell: prefer `npm.cmd` and `npx.cmd` when `npm` or `npx` are blocked by execution policy.\n- Linux/macOS/WSL: use `npm` and `npx`.\n\n## Rules\n\n- Use OS-native commands.\n- Prefer published-package flow unless the user explicitly wants local-repo validation.\n- For published-package flow, prefer `npx stablepay-agentpay-dev ...`.\n- For local-repo flow, prefer `node ./dist/cli.cjs ...`.\n- Treat `onboard --interactive` as a loop. Do not stop after the first prompt.\n- When onboarding reaches browser-based X verification, stop and wait for the user. This is a human-in-the-loop step.\n- Do not try to bypass X verification by searching local source, replaying hidden endpoints, or using mock verification paths.\n- Keep user-facing wording focused on meaningful choices, not internal runtime jargon.\n- Do not claim MCP is active until config is written or the server is confirmed connected.\n- Do not claim the package is release-ready until release verification succeeds.\n\n## Platform Notes\n\n- Windows: the npm package and CLI can work even when the local in-process wallet SDK path is unavailable. Do not assume \"installed\" means \"full local wallet runtime is ready\".\n- Linux/macOS/WSL: standard CLI bootstrap path is expected to work directly.\n\n## Published-Package Flow\n\n### 1. Install or update\n\n```bash\n# Windows\nnpm.cmd install -g stablepay-agentpay-dev\n\n# Linux/macOS/WSL\nnpm install -g stablepay-agentpay-dev\n```\n\nIf global install is unnecessary, skip this and use `npx` directly.\n\n### 2. Verify CLI\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev doctor\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev doctor\n```\n\nIf this fails because the entrypoint is missing or broken, report it as a packaging failure.\n\n### 3. Run onboarding\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev onboard --interactive\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev onboard --interactive\n```\n\nExpected question types:\n\n- create a new wallet or bind an existing one\n- wallet identity details\n- payment limits\n- X verification\n- reward status follow-up\n\nImportant:\n\n- If X verification is still pending, treat it as a pause point, not a successful completion.\n- If the CLI gives a resume session ID or resume command, preserve it and tell the user exactly how to continue.\n- At that point, stop autonomous execution. Wait for the user to complete the browser step and return with the verification result or tweet URL.\n\n### 4. Validate post-onboarding behavior\n\nRun at least one:\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev status\nnpx.cmd stablepay-agentpay-dev balance\nnpx.cmd stablepay-agentpay-dev merchant list\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev status\nnpx stablepay-agentpay-dev balance\nnpx stablepay-agentpay-dev merchant list\n```\n\nBalance semantics:\n\n- `balance` is the StablePay gateway balance for the active DID.\n- It is not the wallet app's total asset value.\n- It is not the native SOL balance.\n\n### 5. Optionally configure MCP\n\nOnly after CLI bootstrap works:\n\n```json\n{\n  \"mcpServers\": {\n    \"stablepay\": {\n      \"command\": \"npx\",\n      \"args\": [\"stablepay-agentpay-dev\", \"mcp\"]\n    }\n  }\n}\n```\n\n## Local-Repo Flow\n\nUse this only when the user wants to validate the working tree before publish.\n\n### 1. Build\n\n```bash\nnpm.cmd run check\nnpm.cmd run build\n```\n\n### 2. Validate CLI\n\n```bash\nnode ./dist/cli.cjs doctor\nnode ./dist/cli.cjs onboard --interactive\nnode ./dist/cli.cjs status\n```\n\n### 3. Release verification\n\n```bash\nnpm.cmd run release:verify\n```\n\n## Publish Flow\n\n```bash\nnpm.cmd version patch\nnpm.cmd run release:verify\nnpm.cmd publish --access public\n```\n\nPost-publish smoke test:\n\n```bash\nnpx stablepay-agentpay-dev doctor\nnpx stablepay-agentpay-dev onboard --interactive\nnpx stablepay-agentpay-dev status\n```\n\n## Failure Classification\n\n### Packaging failure\n\nExamples:\n\n- `npx` cannot find the command\n- `bin` entry is missing\n- `dist/cli.cjs` is missing from the package\n\nReport:\n\n- failed command\n- concrete packaging symptom\n- whether the local repo path still works\n\n### Runtime failure\n\nExamples:\n\n- wallet runtime unavailable\n- onboarding cannot continue because no usable wallet path exists\n\nReport:\n\n- CLI is installed or not\n- which layer is blocked\n- OS context\n\n### Backend or network failure\n\nExamples:\n\n- doctor reaches local runtime but remote APIs fail\n- balance, reward, registration, or merchant calls fail\n\nReport:\n\n- local CLI state\n- failing remote-facing step\n- exact command that failed\n\n### External-verification pause\n\nExamples:\n\n- X verification must be completed in the browser before onboarding can continue\n- user must manually open the verification page and finish the external step\n\nReport:\n\n- onboarding reached a real pause point\n- what the user must do next\n- exact resume command\n\n## Completion Format\n\nReport in compact operator style:\n\n1. OS detected\n2. flow used: published package or local repo\n3. whether onboarding completed or paused\n4. which validation command succeeded\n5. whether MCP was configured\n6. remaining step, if any\n\nExample:\n\n> OS: Linux / WSL2  \n> Flow: published package  \n> Onboarding: paused at X verification  \n> Validation: `status` works  \n> MCP: not configured  \n> Next step: complete X verification, then resume onboarding with the saved session\n\nFile v1.4.0:_meta.json\n\n{\n  \"ownerId\": \"kn7264hkpbx4newe3f23dfmpk582m3mq\",\n  \"slug\": \"stablepay-agent-bootstrap\",\n  \"version\": \"1.4.0\",\n  \"publishedAt\": 1783613948178\n}\n\nFile v1.4.0:skill-card.md\n\n## Description:\n\nInstall, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[bubblevan](https://clawhub.ai/user/bubblevan)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to install and validate StablePay CLI onboarding, handle wallet and payment setup pauses, and optionally configure the StablePay MCP runtime for Codex, Claude Code, or Cursor.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The setup flow asks users to run and optionally persist an unpinned npm package during wallet and payment onboarding.\n\nMitigation: Use a pinned, verified version of stablepay-agentpay-dev, avoid global install unless necessary, and review the exact package before configuring MCP.\n\nRisk: Wallet identity, payment limits, and merchant-facing commands can affect payment behavior if configured incorrectly.\n\nMitigation: Verify wallet identity details, payment limits, and command targets before completing onboarding or running payment-related follow-up commands.\n\nRisk: Onboarding may pause at browser-based X verification, which requires a real external user action.\n\nMitigation: Stop autonomous execution at the verification step, preserve the exact resume command, and continue only after the user completes the browser step.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap)\n- [ClawHub publisher profile](https://clawhub.ai/user/bubblevan)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown operator guidance with inline shell commands and JSON configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include OS-specific command variants, validation results, and human-in-the-loop resume steps.]\n\n## Skill Version(s):\n\n1.4.0 (source: server release metadata and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.3.0: 3 files, 3844 bytes\n\nFiles: skill-card.md (2261b), SKILL.md (5741b), _meta.json (144b)\n\nFile v1.3.0:SKILL.md\n\n---\nname: stablepay-agent-bootstrap\nversion: 1.3.0\nauthor: Bubblevan\ndescription: Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor.\ntags:\n  - stablepay\n  - onboarding\n  - cli\n  - mcp\ncategory: Developer Tools\n---\n\n# StablePay Setup Skill\n\nUse this file as the only required entrypoint. Do not ask for extra docs before starting.\n\n## Success Condition\n\nLeave the environment in one of these states:\n\n1. StablePay is installed and `doctor` works.\n2. onboarding is complete and at least one follow-up command works.\n3. onboarding is paused on a real external step, and the exact resume command is provided.\n\n## Surface Model\n\n- `CLI` is the bootstrap, repair, and release-validation surface.\n- `MCP` is the ongoing in-agent runtime surface.\n- First-time setup: use `CLI` first.\n- After CLI succeeds: optionally add `MCP`.\n\n## First Step: Detect OS\n\nDetect the shell environment before choosing commands.\n\n- Windows PowerShell: prefer `npm.cmd` and `npx.cmd` when `npm` or `npx` are blocked by execution policy.\n- Linux/macOS/WSL: use `npm` and `npx`.\n\n## Rules\n\n- Use OS-native commands.\n- Prefer published-package flow unless the user explicitly wants local-repo validation.\n- For published-package flow, prefer `npx stablepay-agentpay-dev ...`.\n- For local-repo flow, prefer `node ./dist/cli.cjs ...`.\n- Treat `onboard --interactive` as a loop. Do not stop after the first prompt.\n- Keep user-facing wording focused on meaningful choices, not internal runtime jargon.\n- Do not claim MCP is active until config is written or the server is confirmed connected.\n- Do not claim the package is release-ready until release verification succeeds.\n\n## Platform Notes\n\n- Windows: the npm package and CLI can work even when the local in-process wallet SDK path is unavailable. Do not assume \"installed\" means \"full local wallet runtime is ready\".\n- Linux/macOS/WSL: standard CLI bootstrap path is expected to work directly.\n\n## Published-Package Flow\n\n### 1. Install or update\n\n```bash\n# Windows\nnpm.cmd install -g stablepay-agentpay-dev\n\n# Linux/macOS/WSL\nnpm install -g stablepay-agentpay-dev\n```\n\nIf global install is unnecessary, skip this and use `npx` directly.\n\n### 2. Verify CLI\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev doctor\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev doctor\n```\n\nIf this fails because the entrypoint is missing or broken, report it as a packaging failure.\n\n### 3. Run onboarding\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev onboard --interactive\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev onboard --interactive\n```\n\nExpected question types:\n\n- create a new wallet or bind an existing one\n- wallet identity details\n- payment limits\n- X verification\n- reward status follow-up\n\nImportant:\n\n- If X verification is still pending, treat it as a pause point, not a successful completion.\n- If the CLI gives a resume session ID or resume command, preserve it and tell the user exactly how to continue.\n\n### 4. Validate post-onboarding behavior\n\nRun at least one:\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev status\nnpx.cmd stablepay-agentpay-dev balance\nnpx.cmd stablepay-agentpay-dev merchant list\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev status\nnpx stablepay-agentpay-dev balance\nnpx stablepay-agentpay-dev merchant list\n```\n\nBalance semantics:\n\n- `balance` is the StablePay gateway balance for the active DID.\n- It is not the wallet app's total asset value.\n- It is not the native SOL balance.\n\n### 5. Optionally configure MCP\n\nOnly after CLI bootstrap works:\n\n```json\n{\n  \"mcpServers\": {\n    \"stablepay\": {\n      \"command\": \"npx\",\n      \"args\": [\"stablepay-agentpay-dev\", \"mcp\"]\n    }\n  }\n}\n```\n\n## Local-Repo Flow\n\nUse this only when the user wants to validate the working tree before publish.\n\n### 1. Build\n\n```bash\nnpm.cmd run check\nnpm.cmd run build\n```\n\n### 2. Validate CLI\n\n```bash\nnode ./dist/cli.cjs doctor\nnode ./dist/cli.cjs onboard --interactive\nnode ./dist/cli.cjs status\n```\n\n### 3. Release verification\n\n```bash\nnpm.cmd run release:verify\n```\n\n## Publish Flow\n\n```bash\nnpm.cmd version patch\nnpm.cmd run release:verify\nnpm.cmd publish --access public\n```\n\nPost-publish smoke test:\n\n```bash\nnpx stablepay-agentpay-dev doctor\nnpx stablepay-agentpay-dev onboard --interactive\nnpx stablepay-agentpay-dev status\n```\n\n## Failure Classification\n\n### Packaging failure\n\nExamples:\n\n- `npx` cannot find the command\n- `bin` entry is missing\n- `dist/cli.cjs` is missing from the package\n\nReport:\n\n- failed command\n- concrete packaging symptom\n- whether the local repo path still works\n\n### Runtime failure\n\nExamples:\n\n- wallet runtime unavailable\n- onboarding cannot continue because no usable wallet path exists\n\nReport:\n\n- CLI is installed or not\n- which layer is blocked\n- OS context\n\n### Backend or network failure\n\nExamples:\n\n- doctor reaches local runtime but remote APIs fail\n- balance, reward, registration, or merchant calls fail\n\nReport:\n\n- local CLI state\n- failing remote-facing step\n- exact command that failed\n\n### External-verification pause\n\nExamples:\n\n- X verification must be completed in the browser before onboarding can continue\n\nReport:\n\n- onboarding reached a real pause point\n- what the user must do next\n- exact resume command\n\n## Completion Format\n\nReport in compact operator style:\n\n1. OS detected\n2. flow used: published package or local repo\n3. whether onboarding completed or paused\n4. which validation command succeeded\n5. whether MCP was configured\n6. remaining step, if any\n\nExample:\n\n> OS: Linux / WSL2  \n> Flow: published package  \n> Onboarding: paused at X verification  \n> Validation: `status` works  \n> MCP: not configured  \n> Next step: complete X verification, then resume onboarding with the saved session\n\nFile v1.3.0:_meta.json\n\n{\n  \"ownerId\": \"kn7264hkpbx4newe3f23dfmpk582m3mq\",\n  \"slug\": \"stablepay-agent-bootstrap\",\n  \"version\": \"1.3.0\",\n  \"publishedAt\": 1783612008699\n}\n\nFile v1.3.0:skill-card.md\n\n## Description: <br>\nInstall, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[bubblevan](https://clawhub.ai/user/bubblevan) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to install and validate the StablePay CLI, complete or pause onboarding with a clear resume path, and optionally configure StablePay MCP after CLI bootstrap succeeds. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill includes a public npm publish workflow that could expose code or secrets if run unintentionally. <br>\nMitigation: Require explicit manual confirmation before any publish command, inspect the package contents and version, and confirm the npm account and registry target. <br>\nRisk: The skill installs and runs an external npm package for StablePay onboarding. <br>\nMitigation: Install only when StablePay onboarding is intended and the external package source and version are trusted. <br>\nRisk: Onboarding can pause on external X verification or runtime, backend, or network failures. <br>\nMitigation: Treat external verification as a pause point, preserve any resume command, and report the exact failing command and layer. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON configuration snippets] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Reports OS, selected flow, onboarding status, validation command result, MCP configuration status, and any remaining resume step.] <br>\n\n## Skill Version(s): <br>\n1.3.0 (source: frontmatter and server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.2.0: 3 files, 4814 bytes\n\nFiles: skill-card.md (2284b), SKILL.md (7651b), _meta.json (144b)\n\nFile v1.2.0:SKILL.md\n\n---\nname: stablepay-agent-bootstrap\nversion: 1.2.0\nauthor: Bubblevan\ndescription: One-click end-to-end StablePay setup for Codex, Claude Code & Cursor. Covers CLI onboarding, validation, and optional MCP configuration. Cross-platform (Windows/Linux/macOS).\ntags:\n  - stablepay\n  - payment\n  - web3\n  - onboarding\n  - mcp\ncategory: Developer Tools\n---\n\n# StablePay Setup Skill\n\nThis document is the only required entrypoint.\n\nWhen the user says:\n\n- \"Read only this file and install/configure StablePay for me\"\n- \"Set up StablePay for me\"\n- \"Initialize StablePay on this machine\"\n\nyou should follow this document directly and do not require the user to point you to additional project files before starting.\n\n## Goal\n\nLeave the machine in a state where:\n\n1. StablePay is installed or built.\n2. `doctor` runs successfully.\n3. onboarding is completed or clearly blocked by a real external dependency.\n4. at least one post-onboarding command is verified.\n5. MCP is optionally configured after CLI bootstrap succeeds.\n\n## Product Positioning\n\nTreat StablePay as two surfaces:\n\n- `CLI` is the bootstrap and repair surface.\n- `MCP` is the ongoing in-agent runtime surface.\n\nDo not force the user to choose only one.\nFor first-time setup, always prefer CLI first.\nAfter CLI succeeds, MCP may be added as an optional second step.\n\n## OS Detection (Must Do First)\n\nBefore running any command, determine the operating system:\n\n- **Windows**: if `$env:OS` contains \"Windows\" or `uname` returns \"MINGW\"/\"CYGWIN\".\n- **Linux/macOS**: if `uname` returns \"Linux\" or \"Darwin\".\n\nSet a variable `$OS` to either `windows` or `unix` and use it in all following steps.\n\n## Hard Rules\n\n- Use this file as the canonical setup script.\n- **Always use OS-native shell commands**: \n  - On Windows (PowerShell): prefer `npm.cmd` and `npx.cmd` if `npm`/`npx` fail due to execution policy; otherwise `npm`/`npx` work too.\n  - On Linux/macOS (bash/zsh): use `npm` and `npx` directly.\n- Use forward slashes in all paths (e.g., `./dist/cli.cjs`), they work on all platforms.\n- For path A (published package), prefer `npx stablepay-agentpay-dev ...` (or `npx.cmd` on Windows if needed).\n- For path B (local repo), prefer `node ./dist/cli.cjs ...`.\n- Prefer `stablepay onboard --interactive` or `node ./dist/cli.cjs onboard --interactive` for first-time setup.\n- If onboarding asks follow-up questions, keep answering them until it completes or hits a real blocker.\n- Do not describe StablePay to the user using internal jargon like `ows-sdk`, `ows-cli`, `wsl-ows`, `ows-rest`, `MASTER_KEY`, or backend implementation details unless debugging requires it.\n- Do not claim MCP is active unless you actually verified the config was written or the MCP server was successfully connected.\n\n## Platform-Specific Notes\n\n### Windows Reality (known limitation)\n- The npm package can be installed and CLI can run, but the in-process OWS SDK path may be unavailable on native Windows in some environments.\n- Do not promise \"npm install means local OWS SDK is ready\" on Windows.\n- Rely on `doctor` and onboarding to determine what wallet path is actually available.\n- If the local SDK path is unavailable, continue with the supported fallback path instead of treating setup as a total failure.\n\n### Linux/macOS Reality\n- The OWS SDK works natively, and the CLI should have full functionality.\n- No extra fallback handling is required beyond standard npm installation.\n\n## Steps\n\n### Step 1: Install or update\n\nRun:\n\n```bash\n# On Windows (PowerShell):\nnpm.cmd install -g stablepay-agentpay-dev\n\n# On Linux/macOS:\nnpm install -g stablepay-agentpay-dev\n```\n\n(If global install is not desired, use `npx` directly in step 2.)\n\n### Step 2: Verify CLI entrypoint\n\nRun:\n\n```bash\n# On Windows:\nnpx.cmd stablepay-agentpay-dev doctor\n\n# On Linux/macOS:\nnpx stablepay-agentpay-dev doctor\n```\n\nIf this fails because the package entrypoint is broken, stop and report the packaging issue clearly.\n\n### Step 3: Run onboarding\n\nRun:\n\n```bash\n# Windows:\nnpx.cmd stablepay-agentpay-dev onboard --interactive\n\n# Linux/macOS:\nnpx stablepay-agentpay-dev onboard --interactive\n```\n\nOnboarding should be treated as a loop, not a single fire-and-exit action.\n\nExpected categories of questions may include:\n\n- whether to bind an existing wallet or create one\n- wallet identity details\n- payment limit values\n- whether X verification has already been completed\n- whether reward status should be checked\n\nIf the CLI asks a question, answer it and continue until the command finishes.\n\n### Step 4: Validate post-onboarding behavior\n\nRun at least one:\n\n```bash\n# Windows:\nnpx.cmd stablepay-agentpay-dev status\nnpx.cmd stablepay-agentpay-dev balance\nnpx.cmd stablepay-agentpay-dev merchant list\n\n# Linux/macOS:\nnpx stablepay-agentpay-dev status\nnpx stablepay-agentpay-dev balance\nnpx stablepay-agentpay-dev merchant list\n```\n\n### Step 5: Optionally configure MCP\n\nOnly do this after CLI bootstrap is already working.\n\nRecommended MCP config:\n\n```json\n{\n  \"mcpServers\": {\n    \"stablepay\": {\n      \"command\": \"npx\",\n      \"args\": [\"stablepay-agentpay-dev\", \"mcp\"]\n    }\n  }\n}\n```\n\nIf the current host already has an MCP config file convention, write the config there.\nIf the host uses a UI-managed MCP registry, provide the same command and args in that UI.\n\n---\n\n## How To Behave During Onboarding\n\nIf StablePay asks for setup input, keep the interaction focused on user-meaningful choices.\n\nPrefer questions in this shape:\n\n- \"Do you want to bind an existing wallet or create a new one?\"\n- \"What should the single purchase limit be?\"\n- \"What should the auto-charge threshold be?\"\n- \"Have you already completed X verification?\"\n\nAvoid exposing raw implementation knobs unless the product truly cannot continue without them.\n\nIf onboarding exits immediately after one turn and did not complete, explain that the CLI behavior is incorrect for the intended guided setup and continue debugging instead of pretending setup is done.\n\n## Failure Handling\n\nIf setup fails, classify the failure before responding.\n\n### Packaging failure\n\nExamples:\n\n- `npx` cannot find the command\n- `bin` entry is missing\n- `dist/cli.cjs` is missing from the tarball\n\nResponse pattern:\n\n- say the npm package is not correctly published\n- include the failed command\n- include the concrete packaging symptom\n\n### Runtime availability failure\n\nExamples:\n\n- doctor reports wallet runtime unavailable\n- onboarding cannot continue because no usable wallet path exists\n\nResponse pattern:\n\n- say StablePay CLI is present\n- say wallet runtime is the blocked layer\n- say whether the blocker is local SDK, CLI runtime, WSL path, or remote signing path if known (and mention the OS if relevant)\n\n### Backend or network failure\n\nExamples:\n\n- API health checks fail\n- registration or reward checks fail\n- merchant queries fail\n\nResponse pattern:\n\n- say local install succeeded\n- say remote service connectivity is blocked\n- include the failing command or failing API-facing step\n\n## Completion Standard\n\nIf setup succeeds, report success in compact operator language.\n\nPreferred completion shape:\n\n1. say whether you used the local-repo path or published-package path\n2. say which OS you detected and which commands were used\n3. say whether onboarding completed\n4. say which post-onboarding command succeeded\n5. say whether MCP was also configured\n6. if not everything succeeded, say exactly what remains\n\nExample:\n\n> StablePay was set up through the published-package flow on Linux.  \n> Onboarding completed successfully.  \n> `status` now works.  \n> MCP has not been configured yet.  \n> Remaining step: add the `stablepay` MCP server if you want native in-agent tool use.\n\nFile v1.2.0:_meta.json\n\n{\n  \"ownerId\": \"kn7264hkpbx4newe3f23dfmpk582m3mq\",\n  \"slug\": \"stablepay-agent-bootstrap\",\n  \"version\": \"1.2.0\",\n  \"publishedAt\": 1783605935931\n}\n\nFile v1.2.0:skill-card.md\n\n## Description: <br>\nInstall, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[bubblevan](https://clawhub.ai/user/bubblevan) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and agent operators use this skill to install or update StablePay, run CLI health checks, complete wallet and payment onboarding, verify post-onboarding commands, and optionally configure StablePay MCP for Codex, Claude Code, or Cursor. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Installing or running the StablePay npm package can execute package code and modify the local environment. <br>\nMitigation: Review the npm package source before running it, use npx when avoiding a global install is preferred, and install only when StablePay setup is intended on the machine. <br>\nRisk: Wallet onboarding and payment-limit choices can affect future payment behavior. <br>\nMitigation: Choose wallet binding, wallet creation, single-purchase limits, and auto-charge thresholds deliberately during onboarding. <br>\nRisk: Adding the StablePay MCP configuration can give future agent sessions access to StablePay. <br>\nMitigation: Add MCP configuration only after CLI bootstrap succeeds and only when future in-agent StablePay access is desired. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON configuration snippets] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces OS-specific setup guidance and verification steps for Windows, Linux, and macOS.] <br>\n\n## Skill Version(s): <br>\n1.2.0 (source: server release evidence and frontmatter) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.1.0: 3 files, 5337 bytes\n\nFiles: skill-card.md (2097b), SKILL.md (10015b), _meta.json (144b)\n\nFile v1.1.0:SKILL.md\n\n---\nname: stablepay-agent-bootstrap\nversion: 1.1.0\nauthor: Bubblevan\ndescription: One-click end-to-end StablePay setup for Codex, Claude Code & Cursor. Covers CLI onboarding, validation, and optional MCP configuration. Cross-platform (Windows/Linux/macOS).\ntags:\n  - stablepay\n  - payment\n  - web3\n  - onboarding\n  - mcp\ncategory: Developer Tools\n---\n\n# StablePay Setup Skill\n\nThis document is the only required entrypoint.\n\nWhen the user says:\n\n- \"Read only this file and install/configure StablePay for me\"\n- \"Set up StablePay for me\"\n- \"Initialize StablePay on this machine\"\n\nyou should follow this document directly and do not require the user to point you to additional project files before starting.\n\n## Goal\n\nLeave the machine in a state where:\n\n1. StablePay is installed or built.\n2. `doctor` runs successfully.\n3. onboarding is completed or clearly blocked by a real external dependency.\n4. at least one post-onboarding command is verified.\n5. MCP is optionally configured after CLI bootstrap succeeds.\n\n## Product Positioning\n\nTreat StablePay as two surfaces:\n\n- `CLI` is the bootstrap and repair surface.\n- `MCP` is the ongoing in-agent runtime surface.\n\nDo not force the user to choose only one.\nFor first-time setup, always prefer CLI first.\nAfter CLI succeeds, MCP may be added as an optional second step.\n\n## OS Detection (Must Do First)\n\nBefore running any command, determine the operating system:\n\n- **Windows**: if `$env:OS` contains \"Windows\" or `uname` returns \"MINGW\"/\"CYGWIN\".\n- **Linux/macOS**: if `uname` returns \"Linux\" or \"Darwin\".\n\nSet a variable `$OS` to either `windows` or `unix` and use it in all following steps.\n\n## Hard Rules\n\n- Use this file as the canonical setup script.\n- **Always use OS-native shell commands**: \n  - On Windows (PowerShell): prefer `npm.cmd` and `npx.cmd` if `npm`/`npx` fail due to execution policy; otherwise `npm`/`npx` work too.\n  - On Linux/macOS (bash/zsh): use `npm` and `npx` directly.\n- Use forward slashes in all paths (e.g., `./dist/cli.cjs`), they work on all platforms.\n- For path A (published package), prefer `npx stablepay-agentpay-dev ...` (or `npx.cmd` on Windows if needed).\n- For path B (local repo), prefer `node ./dist/cli.cjs ...`.\n- Prefer `stablepay onboard --interactive` or `node ./dist/cli.cjs onboard --interactive` for first-time setup.\n- If onboarding asks follow-up questions, keep answering them until it completes or hits a real blocker.\n- Do not describe StablePay to the user using internal jargon like `ows-sdk`, `ows-cli`, `wsl-ows`, `ows-rest`, `MASTER_KEY`, or backend implementation details unless debugging requires it.\n- Do not claim MCP is active unless you actually verified the config was written or the MCP server was successfully connected.\n- Do not claim the npm package is publish-ready unless release verification succeeded.\n\n## Platform-Specific Notes\n\n### Windows Reality (known limitation)\n- The npm package can be installed and CLI can run, but the in-process OWS SDK path may be unavailable on native Windows in some environments.\n- Do not promise \"npm install means local OWS SDK is ready\" on Windows.\n- Rely on `doctor` and onboarding to determine what wallet path is actually available.\n- If the local SDK path is unavailable, continue with the supported fallback path instead of treating setup as a total failure.\n\n### Linux/macOS Reality\n- The OWS SDK works natively, and the CLI should have full functionality.\n- No extra fallback handling is required beyond standard npm installation.\n\n## Choose One Execution Path\n\nStart by deciding whether the user wants:\n\n### Path A: Published package validation\n\nUse this when the user is simulating a fresh public install, validating npm publish output, or testing from a clean machine.\n\n### Path B: Local repository validation\n\nUse this when the user is inside the repository and wants to validate the current source before or after publish.\n\nIf both are possible and the user did not specify, prefer:\n\n1. local repository validation first\n2. published package validation second\n\n---\n\n## Path A: Published Package Flow\n\n### Step 1: Install or update\n\nRun:\n\n```bash\n# On Windows (PowerShell):\nnpm.cmd install -g stablepay-agentpay-dev\n\n# On Linux/macOS:\nnpm install -g stablepay-agentpay-dev\n```\n\n(If global install is not desired, use `npx` directly in step 2.)\n\n### Step 2: Verify CLI entrypoint\n\nRun:\n\n```bash\n# On Windows:\nnpx.cmd stablepay-agentpay-dev doctor\n\n# On Linux/macOS:\nnpx stablepay-agentpay-dev doctor\n```\n\nIf this fails because the package entrypoint is broken, stop and report the packaging issue clearly.\n\n### Step 3: Run onboarding\n\nRun:\n\n```bash\n# Windows:\nnpx.cmd stablepay-agentpay-dev onboard --interactive\n\n# Linux/macOS:\nnpx stablepay-agentpay-dev onboard --interactive\n```\n\nOnboarding should be treated as a loop, not a single fire-and-exit action.\n\nExpected categories of questions may include:\n\n- whether to bind an existing wallet or create one\n- wallet identity details\n- payment limit values\n- whether X verification has already been completed\n- whether reward status should be checked\n\nIf the CLI asks a question, answer it and continue until the command finishes.\n\n### Step 4: Validate post-onboarding behavior\n\nRun at least one:\n\n```bash\n# Windows:\nnpx.cmd stablepay-agentpay-dev status\nnpx.cmd stablepay-agentpay-dev balance\nnpx.cmd stablepay-agentpay-dev merchant list\n\n# Linux/macOS:\nnpx stablepay-agentpay-dev status\nnpx stablepay-agentpay-dev balance\nnpx stablepay-agentpay-dev merchant list\n```\n\n### Step 5: Optionally configure MCP\n\nOnly do this after CLI bootstrap is already working.\n\nRecommended MCP config:\n\n```json\n{\n  \"mcpServers\": {\n    \"stablepay\": {\n      \"command\": \"npx\",\n      \"args\": [\"stablepay-agentpay-dev\", \"mcp\"]\n    }\n  }\n}\n```\n\nIf the current host already has an MCP config file convention, write the config there.\nIf the host uses a UI-managed MCP registry, provide the same command and args in that UI.\n\n---\n\n## Path B: Local Repository Flow\n\nAssume the repository root is open and the package has not necessarily been published yet.\n\n### Step 1: Build and typecheck\n\nRun:\n\n```bash\n# Windows/Linux/macOS all use:\nnpm run check\nnpm run build\n```\n\n### Step 2: Verify local CLI\n\nRun:\n\n```bash\n# Windows:\nnode ./dist/cli.cjs doctor\n\n# Linux/macOS:\nnode ./dist/cli.cjs doctor\n```\n\n### Step 3: Run onboarding\n\nRun:\n\n```bash\n# Windows:\nnode ./dist/cli.cjs onboard --interactive\n\n# Linux/macOS:\nnode ./dist/cli.cjs onboard --interactive\n```\n\nTreat onboarding as a continuing setup loop until completion or a real external blocker.\n\n### Step 4: Validate post-onboarding behavior\n\nRun at least one:\n\n```bash\n# Windows:\nnode ./dist/cli.cjs status\nnode ./dist/cli.cjs balance\nnode ./dist/cli.cjs merchant list\n\n# Linux/macOS:\nnode ./dist/cli.cjs status\nnode ./dist/cli.cjs balance\nnode ./dist/cli.cjs merchant list\n```\n\n### Step 5: Verify release readiness\n\nRun:\n\n```bash\nnpm run release:verify\n```\n\nOnly describe the package as publish-ready if this succeeds.\n\n---\n\n## Publish Flow\n\nWhen the user asks for release or npm publishing commands, use this sequence.\n\n### Version bump\n\nChoose one:\n\n```bash\nnpm version patch\nnpm version minor\nnpm version major\n```\n\n### Pre-publish verification\n\nRun:\n\n```bash\nnpm run release:verify\n```\n\n### Publish\n\nRun:\n\n```bash\nnpm publish --access public\n```\n\n### Post-publish smoke test\n\nFrom a clean shell, run:\n\n```bash\n# Windows:\nnpx.cmd stablepay-agentpay-dev doctor\nnpx.cmd stablepay-agentpay-dev onboard --interactive\nnpx.cmd stablepay-agentpay-dev status\n\n# Linux/macOS:\nnpx stablepay-agentpay-dev doctor\nnpx stablepay-agentpay-dev onboard --interactive\nnpx stablepay-agentpay-dev status\n```\n\n## How To Behave During Onboarding\n\nIf StablePay asks for setup input, keep the interaction focused on user-meaningful choices.\n\nPrefer questions in this shape:\n\n- \"Do you want to bind an existing wallet or create a new one?\"\n- \"What should the single purchase limit be?\"\n- \"What should the auto-charge threshold be?\"\n- \"Have you already completed X verification?\"\n\nAvoid exposing raw implementation knobs unless the product truly cannot continue without them.\n\nIf onboarding exits immediately after one turn and did not complete, explain that the CLI behavior is incorrect for the intended guided setup and continue debugging instead of pretending setup is done.\n\n## Failure Handling\n\nIf setup fails, classify the failure before responding.\n\n### Packaging failure\n\nExamples:\n\n- `npx` cannot find the command\n- `bin` entry is missing\n- `dist/cli.cjs` is missing from the tarball\n\nResponse pattern:\n\n- say the npm package is not correctly published\n- include the failed command\n- include the concrete packaging symptom\n\n### Runtime availability failure\n\nExamples:\n\n- doctor reports wallet runtime unavailable\n- onboarding cannot continue because no usable wallet path exists\n\nResponse pattern:\n\n- say StablePay CLI is present\n- say wallet runtime is the blocked layer\n- say whether the blocker is local SDK, CLI runtime, WSL path, or remote signing path if known (and mention the OS if relevant)\n\n### Backend or network failure\n\nExamples:\n\n- API health checks fail\n- registration or reward checks fail\n- merchant queries fail\n\nResponse pattern:\n\n- say local install succeeded\n- say remote service connectivity is blocked\n- include the failing command or failing API-facing step\n\n## Completion Standard\n\nIf setup succeeds, report success in compact operator language.\n\nPreferred completion shape:\n\n1. say whether you used the local-repo path or published-package path\n2. say which OS you detected and which commands were used\n3. say whether onboarding completed\n4. say which post-onboarding command succeeded\n5. say whether MCP was also configured\n6. if not everything succeeded, say exactly what remains\n\nExample:\n\n> StablePay was set up through the published-package flow on Linux.  \n> Onboarding completed successfully.  \n> `status` now works.  \n> MCP has not been configured yet.  \n> Remaining step: add the `stablepay` MCP server if you want native in-agent tool use.\n\nFile v1.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn7264hkpbx4newe3f23dfmpk582m3mq\",\n  \"slug\": \"stablepay-agent-bootstrap\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1783605512670\n}\n\nFile v1.1.0:skill-card.md\n\n## Description: <br>\nOne-click end-to-end StablePay setup for Codex, Claude Code & Cursor. Covers CLI onboarding, validation, and optional MCP configuration. Cross-platform (Windows/Linux/macOS). <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[bubblevan](https://clawhub.ai/user/bubblevan) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and engineers use this skill to install or validate StablePay, complete CLI onboarding, verify post-onboarding commands, and optionally configure the StablePay MCP server for Codex, Claude Code, or Cursor. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can install or run the StablePay npm package and may change local CLI or MCP setup. <br>\nMitigation: Ask the agent to summarize each command before execution and confirm any MCP configuration file it plans to modify. <br>\nRisk: StablePay onboarding may involve wallet identity and payment limit choices. <br>\nMitigation: Review wallet and payment settings before confirming onboarding prompts, especially purchase limits and auto-charge thresholds. <br>\n\n\n## Reference(s): <br>\n- [StablePay Agent Bootstrap on ClawHub](https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap) <br>\n- [Bubblevan publisher profile](https://clawhub.ai/user/bubblevan) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Shell commands, Configuration, Guidance, Markdown] <br>\n**Output Format:** [Markdown with inline shell commands and JSON configuration snippets] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Includes OS-specific command variants and concise setup status reporting.] <br>\n\n## Skill Version(s): <br>\n1.1.0 (source: frontmatter and server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 3 files, 5043 bytes\n\nFiles: skill-card.md (2318b), SKILL.md (9110b), _meta.json (144b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: stablepay-agent-bootstrap\nversion: 1.0.0\nauthor: Bubblevan\ndescription: One-click end-to-end StablePay setup for Codex, Claude Code & Cursor. Covers CLI onboarding, validation, and optional MCP configuration.\ntags:\n  - stablepay\n  - payment\n  - web3\n  - onboarding\n  - mcp\ncategory: Developer Tools\n---\n\n# StablePay Setup Skill\n\nThis document is the only required entrypoint.\n\nWhen the user says:\n\n- \"Read only this file and install/configure StablePay for me\"\n- \"Set up StablePay for me\"\n- \"Initialize StablePay on this machine\"\n\nyou should follow this document directly and do not require the user to point you to additional project files before starting.\n\n## Goal\n\nLeave the machine in a state where:\n\n1. StablePay is installed or built.\n2. `doctor` runs successfully.\n3. onboarding is completed or clearly blocked by a real external dependency.\n4. at least one post-onboarding command is verified.\n5. MCP is optionally configured after CLI bootstrap succeeds.\n\n## Product Positioning\n\nTreat StablePay as two surfaces:\n\n- `CLI` is the bootstrap and repair surface.\n- `MCP` is the ongoing in-agent runtime surface.\n\nDo not force the user to choose only one.\nFor first-time setup, always prefer CLI first.\nAfter CLI succeeds, MCP may be added as an optional second step.\n\n## Hard Rules\n\n- Use this file as the canonical setup script.\n- Prefer Windows PowerShell commands when the machine is Windows.\n- On Windows PowerShell, prefer `npm.cmd` over `npm` if command resolution or execution policy is unstable.\n- Prefer `npx stablepay-agentpay-dev ...` for the published-package path.\n- Prefer `node .\\dist\\cli.cjs ...` only when working from the local repository before publish.\n- Prefer `stablepay onboard --interactive` or `node .\\dist\\cli.cjs onboard --interactive` for first-time setup.\n- If onboarding asks follow-up questions, keep answering them until it completes or hits a real blocker.\n- Do not describe StablePay to the user using internal jargon like `ows-sdk`, `ows-cli`, `wsl-ows`, `ows-rest`, `MASTER_KEY`, or backend implementation details unless debugging requires it.\n- Do not claim MCP is active unless you actually verified the config was written or the MCP server was successfully connected.\n- Do not claim the npm package is publish-ready unless release verification succeeded.\n\n## Important Windows Reality\n\nDo not assume Windows can use the local OWS SDK path just because npm install succeeds.\n\nCurrent product reality:\n\n- the npm package can be installed on Windows\n- StablePay CLI can run on Windows\n- but the in-process OWS SDK path may still be unavailable on native Windows in some environments\n\nSo on Windows:\n\n- do not promise \"npm install means local OWS SDK is ready\"\n- rely on `doctor` and onboarding to determine what wallet path is actually available\n- if the local SDK path is unavailable, continue with the supported fallback path instead of treating setup as a total failure\n\n## Choose One Execution Path\n\nStart by deciding whether the user wants:\n\n### Path A: Published package validation\n\nUse this when the user is simulating a fresh public install, validating npm publish output, or testing from a clean machine.\n\n### Path B: Local repository validation\n\nUse this when the user is inside the repository and wants to validate the current source before or after publish.\n\nIf both are possible and the user did not specify, prefer:\n\n1. local repository validation first\n2. published package validation second\n\n## Path A: Published Package Flow\n\n### Step 1: Install or update\n\nRun:\n\n```powershell\nnpm.cmd install -g stablepay-agentpay-dev\n```\n\nIf global install is not desired, use:\n\n```powershell\nnpx stablepay-agentpay-dev doctor\n```\n\n### Step 2: Verify CLI entrypoint\n\nRun:\n\n```powershell\nnpx stablepay-agentpay-dev doctor\n```\n\nIf this fails because the package entrypoint is broken, stop and report the packaging issue clearly.\n\n### Step 3: Run onboarding\n\nRun:\n\n```powershell\nnpx stablepay-agentpay-dev onboard --interactive\n```\n\nOnboarding should be treated as a loop, not a single fire-and-exit action.\n\nExpected categories of questions may include:\n\n- whether to bind an existing wallet or create one\n- wallet identity details\n- payment limit values\n- whether X verification has already been completed\n- whether reward status should be checked\n\nIf the CLI asks a question, answer it and continue until the command finishes.\n\n### Step 4: Validate post-onboarding behavior\n\nRun at least one:\n\n```powershell\nnpx stablepay-agentpay-dev status\n```\n\n```powershell\nnpx stablepay-agentpay-dev balance\n```\n\n```powershell\nnpx stablepay-agentpay-dev merchant list\n```\n\n### Step 5: Optionally configure MCP\n\nOnly do this after CLI bootstrap is already working.\n\nRecommended MCP config:\n\n```json\n{\n  \"mcpServers\": {\n    \"stablepay\": {\n      \"command\": \"npx\",\n      \"args\": [\"stablepay-agentpay-dev\", \"mcp\"]\n    }\n  }\n}\n```\n\nIf the current host already has an MCP config file convention, write the config there.\nIf the host uses a UI-managed MCP registry, provide the same command and args in that UI.\n\n## Path B: Local Repository Flow\n\nAssume the repository root is open and the package has not necessarily been published yet.\n\n### Step 1: Build and typecheck\n\nRun:\n\n```powershell\nnpm.cmd run check\nnpm.cmd run build\n```\n\n### Step 2: Verify local CLI\n\nRun:\n\n```powershell\nnode .\\dist\\cli.cjs doctor\n```\n\n### Step 3: Run onboarding\n\nRun:\n\n```powershell\nnode .\\dist\\cli.cjs onboard --interactive\n```\n\nTreat onboarding as a continuing setup loop until completion or a real external blocker.\n\n### Step 4: Validate post-onboarding behavior\n\nRun at least one:\n\n```powershell\nnode .\\dist\\cli.cjs status\n```\n\n```powershell\nnode .\\dist\\cli.cjs balance\n```\n\n```powershell\nnode .\\dist\\cli.cjs merchant list\n```\n\n### Step 5: Verify release readiness\n\nRun:\n\n```powershell\nnpm.cmd run release:verify\n```\n\nOnly describe the package as publish-ready if this succeeds.\n\n## Publish Flow\n\nWhen the user asks for release or npm publishing commands, use this sequence.\n\n### Version bump\n\nChoose one:\n\n```powershell\nnpm.cmd version patch\n```\n\n```powershell\nnpm.cmd version minor\n```\n\n```powershell\nnpm.cmd version major\n```\n\n### Pre-publish verification\n\nRun:\n\n```powershell\nnpm.cmd run release:verify\n```\n\n### Publish\n\nRun:\n\n```powershell\nnpm.cmd publish --access public\n```\n\n### Post-publish smoke test\n\nFrom a clean shell, run:\n\n```powershell\nnpx stablepay-agentpay-dev doctor\nnpx stablepay-agentpay-dev onboard --interactive\nnpx stablepay-agentpay-dev status\n```\n\n## How To Behave During Onboarding\n\nIf StablePay asks for setup input, keep the interaction focused on user-meaningful choices.\n\nPrefer questions in this shape:\n\n- \"Do you want to bind an existing wallet or create a new one?\"\n- \"What should the single purchase limit be?\"\n- \"What should the auto-charge threshold be?\"\n- \"Have you already completed X verification?\"\n\nAvoid exposing raw implementation knobs unless the product truly cannot continue without them.\n\nIf onboarding exits immediately after one turn and did not complete, explain that the CLI behavior is incorrect for the intended guided setup and continue debugging instead of pretending setup is done.\n\n## Failure Handling\n\nIf setup fails, classify the failure before responding.\n\n### Packaging failure\n\nExamples:\n\n- `npx` cannot find the command\n- `bin` entry is missing\n- `dist/cli.cjs` is missing from the tarball\n\nResponse pattern:\n\n- say the npm package is not correctly published\n- include the failed command\n- include the concrete packaging symptom\n\n### Runtime availability failure\n\nExamples:\n\n- doctor reports wallet runtime unavailable\n- onboarding cannot continue because no usable wallet path exists\n\nResponse pattern:\n\n- say StablePay CLI is present\n- say wallet runtime is the blocked layer\n- say whether the blocker is local SDK, CLI runtime, WSL path, or remote signing path if known\n\n### Backend or network failure\n\nExamples:\n\n- API health checks fail\n- registration or reward checks fail\n- merchant queries fail\n\nResponse pattern:\n\n- say local install succeeded\n- say remote service connectivity is blocked\n- include the failing command or failing API-facing step\n\n## Completion Standard\n\nIf setup succeeds, report success in compact operator language.\n\nPreferred completion shape:\n\n1. say whether you used the local-repo path or published-package path\n2. say whether onboarding completed\n3. say which post-onboarding command succeeded\n4. say whether MCP was also configured\n5. if not everything succeeded, say exactly what remains\n\nExample:\n\n> StablePay was set up through the local repository flow.  \n> Onboarding completed successfully.  \n> `status` now works.  \n> MCP has not been configured yet.  \n> Remaining step: add the `stablepay` MCP server if you want native in-agent tool use.\n\n## Official Prompt To Give Another Agent\n\nIf the user wants a one-line prompt for another agent window, use:\n\n> Read only this file, then install, initialize, and validate StablePay. When you finish, tell me whether you used the local-repository path or the npm-published path, whether onboarding completed, and which verification command succeeded.\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn7264hkpbx4newe3f23dfmpk582m3mq\",\n  \"slug\": \"stablepay-agent-bootstrap\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1783599537677\n}\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nOne-click end-to-end StablePay setup for Codex, Claude Code & Cursor. Covers CLI onboarding, validation, and optional MCP configuration. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[bubblevan](https://clawhub.ai/user/bubblevan) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to install or validate StablePay CLI, complete onboarding, verify post-onboarding commands, and optionally add StablePay MCP integration for Codex, Claude Code, or Cursor. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The setup flow can install or run the StablePay npm package on the local machine. <br>\nMitigation: Install this skill only when StablePay setup is intended, and review the npm package source or resolved package before running install or npx commands. <br>\nRisk: Onboarding may involve wallet identity and payment-limit choices. <br>\nMitigation: Make wallet, spending limit, and auto-charge threshold decisions deliberately, then verify the result with doctor and a post-onboarding command. <br>\nRisk: Optional MCP setup may write a persistent MCP server entry for the agent host. <br>\nMitigation: Approve the exact MCP configuration target and command before writing a persistent entry, and verify the server connection before claiming MCP is active. <br>\n\n\n## Reference(s): <br>\n- [StablePay Agent Bootstrap on ClawHub](https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON configuration snippets] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May propose npm, npx, Node.js, and MCP configuration changes that should be reviewed before execution.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: artifact frontmatter and server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: StablePay Agent Bootstrap Owner: bubblevan Summary: Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. Tags: latest:1.4.0, mcp:1.4.0, payment:1.4.0, stablepay:1.4.0, web3:1.4.0 Version history: v1.4.0 | 2026-07-09T16:19:08.178Z | user Initial release v1.3.0 | 2026-07-09T15:46:48.699Z | user Initial release v1.2.0 | 2026-07-09T14:05:35.931Z | user Initial releas","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"# Windows\nnpm.cmd install -g stablepay-agentpay-dev\n\n# Linux/macOS/WSL\nnpm install -g stablepay-agentpay-dev"},{"language":"bash","snippet":"# Windows\nnpx.cmd stablepay-agentpay-dev doctor\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev doctor"},{"language":"bash","snippet":"# Windows\nnpx.cmd stablepay-agentpay-dev onboard --interactive\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev onboard --interactive"},{"language":"bash","snippet":"# Windows\nnpx.cmd stablepay-agentpay-dev status\nnpx.cmd stablepay-agentpay-dev balance\nnpx.cmd stablepay-agentpay-dev merchant list\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev status\nnpx stablepay-agentpay-dev balance\nnpx stablepay-agentpay-dev merchant list"},{"language":"json","snippet":"{\n  \"mcpServers\": {\n    \"stablepay\": {\n      \"command\": \"npx\",\n      \"args\": [\"stablepay-agentpay-dev\", \"mcp\"]\n    }\n  }\n}"},{"language":"bash","snippet":"npm.cmd run check\nnpm.cmd run build"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: stablepay-agent-bootstrap\nversion: 1.4.0\nauthor: Bubblevan\ndescription: Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor.\ntags:\n  - stablepay\n  - onboarding\n  - cli\n  - mcp\ncategory: Developer Tools\n---\n\n# StablePay Setup Skill\n\nUse this file as the only required entrypoint. Do not ask for extra docs before starting.\n\n## Success Condition\n\nLeave the environment in one of these states:\n\n1. StablePay is installed and `doctor` works.\n2. onboarding is complete and at least one follow-up command works.\n3. onboarding is paused on a real external step, and the exact resume command is provided.\n\n## Surface Model\n\n- `CLI` is the bootstrap, repair, and release-validation surface.\n- `MCP` is the ongoing in-agent runtime surface.\n- First-time setup: use `CLI` first.\n- After CLI succeeds: optionally add `MCP`.\n\n## First Step: Detect OS\n\nDetect the shell environment before choosing commands.\n\n- Windows PowerShell: prefer `npm.cmd` and `npx.cmd` when `npm` or `npx` are blocked by execution policy.\n- Linux/macOS/WSL: use `npm` and `npx`.\n\n## Rules\n\n- Use OS-native commands.\n- Prefer published-package flow unless the user explicitly wants local-repo validation.\n- For published-package flow, prefer `npx stablepay-agentpay-dev ...`.\n- For local-repo flow, prefer `node ./dist/cli.cjs ...`.\n- Treat `onboard --interactive` as a loop. Do not stop after the first prompt.\n- When onboarding reaches browser-based X verification, stop and wait for the user. This is a human-in-the-loop step.\n- Do not try to bypass X verification by searching local source, replaying hidden endpoints, or using mock verification paths.\n- Keep user-facing wording focused on meaningful choices, not internal runtime jargon.\n- Do not claim MCP is active until config is written or the server is confirmed connected.\n- Do not claim the package is release-ready until release verification succeeds.\n\n## Platform Notes\n\n- Windows: the npm package and CLI can work even when the local in-process wallet SDK path is unavailable. Do not assume \"installed\" means \"full local wallet runtime is ready\".\n- Linux/macOS/WSL: standard CLI bootstrap path is expected to work directly.\n\n## Published-Package Flow\n\n### 1. Install or update\n\n```bash\n# Windows\nnpm.cmd install -g stablepay-agentpay-dev\n\n# Linux/macOS/WSL\nnpm install -g stablepay-agentpay-dev\n```\n\nIf global install is unnecessary, skip this and use `npx` directly.\n\n### 2. Verify CLI\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev doctor\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev doctor\n```\n\nIf this fails because the entrypoint is missing or broken, report it as a packaging failure.\n\n### 3. Run onboarding\n\n```bash\n# Windows\nnpx.cmd stablepay-agentpay-dev onboard --interactive\n\n# Linux/macOS/WSL\nnpx stablepay-agentpay-dev onboard --interactive\n```\n\nExpected question types:\n\n- create a new wallet or bind an existing one\n- wallet identity details\n- payment limits\n- X verification\n- reward status foll"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7264hkpbx4newe3f23dfmpk582m3mq\",\n  \"slug\": \"stablepay-agent-bootstrap\",\n  \"version\": \"1.4.0\",\n  \"publishedAt\": 1783613948178\n}"},{"path":"skill-card.md","content":"## Description:\n\nInstall, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[bubblevan](https://clawhub.ai/user/bubblevan)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to install and validate StablePay CLI onboarding, handle wallet and payment setup pauses, and optionally configure the StablePay MCP runtime for Codex, Claude Code, or Cursor.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The setup flow asks users to run and optionally persist an unpinned npm package during wallet and payment onboarding.\n\nMitigation: Use a pinned, verified version of stablepay-agentpay-dev, avoid global install unless necessary, and review the exact package before configuring MCP.\n\nRisk: Wallet identity, payment limits, and merchant-facing commands can affect payment behavior if configured incorrectly.\n\nMitigation: Verify wallet identity details, payment limits, and command targets before completing onboarding or running payment-related follow-up commands.\n\nRisk: Onboarding may pause at browser-based X verification, which requires a real external user action.\n\nMitigation: Stop autonomous execution at the verification step, preserve the exact resume command, and continue only after the user completes the browser step.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/bubblevan/skills/stablepay-agent-bootstrap)\n- [ClawHub publisher profile](https://clawhub.ai/user/bubblevan)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown operator guidance with inline shell commands and JSON configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include OS-specific command variants, validation results, and human-in-the-loop resume steps.]\n\n## Skill Version(s):\n\n1.4.0 (source: server release metadata and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. Skill: StablePay Agent Bootstrap Owner: bubblevan Summary: Install, bootstrap, validate, and optionally connect StablePay MCP on Codex, Claude Code, or Cursor. Tags: latest:1.4.0, mcp:1.4.0, payment:1.4.0, stablepay:1.4.0, web3:1.4.0 Version history: v1.4.0 | 2026-07-09T16:19:08.178Z | user Initial release v1.3.0 | 2026-07-09T15:46:48.699Z | user Initial release v1.2.0 | 2026-07-09T14:05:35.931Z | user Initial releas","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1073,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:14:41.456Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:14:41.456Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:38:56.530Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}