{"id":22253,"plugin_id":"plugins_6ab02697e5fc819194df99f189e7490d","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:17:12.413Z","digest":"b7b03dcb1f99f126e14c5692c4e6cece32b33847c9854175ae9da48c93574e64","against":null,"payload":{"name":"x402","description":"Use when the user explicitly asks for conceptual guidance, code review, or debugging help for x402 payment integration with Browser Use, without handling secrets or initiating transactions.","included_files":[{"relative_path":"SOURCE-METADATA.yaml","size_in_bytes":166},{"relative_path":"agents/openai.yaml","size_in_bytes":310}],"skill_md_contents":"---\nname: x402\ndescription: Use when the user explicitly asks for conceptual guidance, code review, or debugging help for x402 payment integration with Browser Use, without handling secrets or initiating transactions.\n---\n\n# Browser Use x402 Reference\n\nReference-only guidance for understanding and reviewing x402 integrations around Browser Use.\n\n## Scope\n\nUse this skill to:\n- explain the x402 request/response model at a high level;\n- review user-provided integration code for structure, error handling, and configuration mistakes;\n- explain how HTTP 402 payment-required flows fit into Browser Use architectures;\n- help interpret non-sensitive logs or errors supplied by the user;\n- identify which part of an integration belongs to the application, payment client, Browser Use service, or host environment.\n\n## Safety and execution boundaries\n\nThis skill is reference-only. It does not install packages, download or execute external code, create accounts or wallets, or initiate financial transactions.\n\nNever request or handle wallet secrets, recovery material, authentication secrets, or other sensitive credentials. Do not ask the user to paste them into chat or write them to files.\n\nThis skill does not initiate payments, move funds, purchase assets, top up balances, or perform on-chain actions. If a workflow requires a payment-capable client, assume the user has already configured it outside this skill and limit assistance to conceptual review and non-sensitive debugging.\n\nRespect authentication, access controls, service policies, browser security boundaries, and other usage restrictions.\n\n## Host capability adaptation\n\n1. Prefer approved host-managed capabilities already available in ChatGPT or Codex.\n2. If the user supplies code or logs, analyze only the supplied material and explain the likely integration issue.\n3. If an external runtime would be required to complete an action, state that limitation instead of attempting to bootstrap, install, or invoke it.\n4. Never fabricate a successful request, payment result, balance, transaction, or service response.\n\n## Review checklist\n\nWhen reviewing an x402 integration, check:\n- whether a 402 response is handled as an expected protocol state rather than a generic failure;\n- whether payment-related configuration is separated from application logic;\n- whether retry behavior is bounded and avoids duplicate charge attempts;\n- whether errors are surfaced without exposing sensitive values;\n- whether the application distinguishes transport errors, authorization errors, payment-required responses, and service errors;\n- whether the user has a safe test environment before any real-world payment-enabled deployment.\n\n## Output style\n\nGive concise architecture guidance, code-review findings, or debugging hypotheses. Clearly distinguish what can be inferred from the user's code/logs from what would require an external service or payment-capable runtime to verify.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}