[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MB3FBACD705JMPBHNZ45N":3,"skill-same:01M75MB3FBACD705JMPBHNZ45N":54},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M75MB3FBACD705JMPBHNZ45N","brek-ai-skill",null,"Integrate with Brek Partner Core Chat API for hotel-search and booking assistant flows. Use when an agent needs to create or continue Brek chat sessions, send user events safely, enforce anti-abuse call controls, and run payment setup or payment confirmation without collecting raw card data.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fleo9\u002Fbrek-ai\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: brek-ai-skill\ndescription: Integrate with Brek Partner Core Chat API for hotel-search and booking assistant flows. Use when an agent needs to create or continue Brek chat sessions, send user events safely, enforce anti-abuse call controls, and run payment setup or payment confirmation without collecting raw card data.\nmetadata:\n  required_env_vars: BREK_BASE_URL,BREK_PARTNER_API_KEY\n  primary_credential: BREK_PARTNER_API_KEY\n  required_runtime_inputs: actorId,workspaceId,partnerId,clientActionId\n  storage_requirements: durable idempotency dedupe store,budget counter store,usage metering log\n  autonomous_invocation: \"false\"\n  always_on_presence: \"false\"\n  config_paths: none\n---\n\n# Brek AI Partner Core Chat\n\nExecute Brek through `\u002Fapi\u002Fpartner\u002Fv1\u002Fcore-chat`.\n\nUse this execution order:\n1. Create one session per end user (`POST \u002Fsessions`) with a stable `actor.actorId`.\n2. Reuse that session for all follow-up messages (`POST \u002Fevents`).\n3. Read the latest state when needed (`GET \u002Fsessions\u002F{sessionId}`).\n\nDo not share one session across different users.\n\n## Required runtime inputs\n\nRequire these inputs before calling Brek:\n- `BREK_BASE_URL`\n- `BREK_PARTNER_API_KEY`\n- `actorId` (stable partner-side end-user ID)\n- `workspaceId` or tenant context if your product uses workspaces\n- `partnerId` (stable partner tenant ID for idempotency and billing grouping)\n- `clientActionId` for each write-like event kind\n\nIf one required input is missing, stop and request it.\n\nIf `BREK_PARTNER_API_KEY` is missing:\n- stop outbound calls\n- ask the user to get the key from their internal owner or approved support channel\n- never request secrets through unapproved channels\n\n## Call safety guardrails\n\nApply these guardrails before every upstream call:\n1. Enforce local budget limits from `references\u002Fcall-control.md`.\n2. Attach a deterministic `idempotencyKey` for all write-like event kinds.\n3. Respect `429` with `retry-after` and exponential backoff.\n4. Open a circuit breaker after repeated 5xx or timeout failures.\n5. Log `x-request-id`, `x-partner-id`, `x-ratelimit-limit`, and `x-ratelimit-remaining`.\n\nNever retry booking or payment-confirm actions without the same `idempotencyKey`.\n\n## Event-kind rules\n\nWhen `kind` is one of:\n- `command_book_by_option_id`\n- `action_book_option`\n- `action_confirm_price_change`\n- `action_confirm_payment_card`\n- `action_cancel_booking`\n\nAlways include `idempotencyKey`.\n\nGenerate `idempotencyKey` as:\n- `\u003CpartnerId>:\u003CsessionId>:\u003Ckind>:\u003CclientActionId>`\n\nIf `partnerId` is unavailable in your runtime, use stable tenant context (for example `workspaceId`) and keep the key format deterministic.\n\n## Payment handling\n\nHandle payment in two layers:\n1. End-user card setup and confirmation in secure portal flow.\n2. Agent-to-agent usage billing and settlement.\n\nFollow `references\u002Fpayment-and-billing.md` for both layers.\n\nHard rules:\n- Never request or store raw card number, CVV, or full PAN in chat.\n- Accept only tokenized `paymentMethodId` from provider-hosted fields.\n- Require explicit user confirmation before `action_confirm_payment_card` and booking actions.\n\n## Response mapping\n\nMap Brek response as:\n- `data.result.status` -> state machine key for UI and orchestration\n- `data.result.message.text` -> user-visible assistant text\n- `data.result.artifacts` -> structured payload (shortlist, payment setup URL, booking metadata)\n\n## Error handling\n\n- `400`: request validation failed. Fix payload.\n- `401\u002F403`: API key issue. Stop calls. Tell user to rotate or provision key through their internal owner or approved support channel.\n- `404`: session not found or wrong tenant.\n- `409`: actor\u002Fsession mismatch. Recreate correct session.\n- `429`: throttle locally and retry by `retry-after`.\n- `5xx`: retry with backoff, then open breaker.\n\n## References\n\nRead only what you need:\n- API payload templates: `references\u002Fapi-templates.md`\n- Call-control and anti-abuse policy: `references\u002Fcall-control.md`\n- Payment and billing orchestration: `references\u002Fpayment-and-billing.md`\n","# Brek AI Partner Core Chat\n\nExecute Brek through `\u002Fapi\u002Fpartner\u002Fv1\u002Fcore-chat`.\n\nUse this execution order:\n1. Create one session per end user (`POST \u002Fsessions`) with a stable `actor.actorId`.\n2. Reuse that session for all follow-up messages (`POST \u002Fevents`).\n3. Read the latest state when needed (`GET \u002Fsessions\u002F{sessionId}`).\n\nDo not share one session across different users.\n\n## Required runtime inputs\n\nRequire these inputs before calling Brek:\n- `BREK_BASE_URL`\n- `BREK_PARTNER_API_KEY`\n- `actorId` (stable partner-side end-user ID)\n- `workspaceId` or tenant context if your product uses workspaces\n- `partnerId` (stable partner tenant ID for idempotency and billing grouping)\n- `clientActionId` for each write-like event kind\n\nIf one required input is missing, stop and request it.\n\nIf `BREK_PARTNER_API_KEY` is missing:\n- stop outbound calls\n- ask the user to get the key from their internal owner or approved support channel\n- never request secrets through unapproved channels\n\n## Call safety guardrails\n\nApply these guardrails before every upstream call:\n1. Enforce local budget limits from `references\u002Fcall-control.md`.\n2. Attach a deterministic `idempotencyKey` for all write-like event kinds.\n3. Respect `429` with `retry-after` and exponential backoff.\n4. Open a circuit breaker after repeated 5xx or timeout failures.\n5. Log `x-request-id`, `x-partner-id`, `x-ratelimit-limit`, and `x-ratelimit-remaining`.\n\nNever retry booking or payment-confirm actions without the same `idempotencyKey`.\n\n## Event-kind rules\n\nWhen `kind` is one of:\n- `command_book_by_option_id`\n- `action_book_option`\n- `action_confirm_price_change`\n- `action_confirm_payment_card`\n- `action_cancel_booking`\n\nAlways include `idempotencyKey`.\n\nGenerate `idempotencyKey` as:\n- `\u003CpartnerId>:\u003CsessionId>:\u003Ckind>:\u003CclientActionId>`\n\nIf `partnerId` is unavailable in your runtime, use stable tenant context (for example `workspaceId`) and keep the key format deterministic.\n\n## Payment handling\n\nHandle payment in two layers:\n1. End-user card setup and confirmation in secure portal flow.\n2. Agent-to-agent usage billing and settlement.\n\nFollow `references\u002Fpayment-and-billing.md` for both layers.\n\nHard rules:\n- Never request or store raw card number, CVV, or full PAN in chat.\n- Accept only tokenized `paymentMethodId` from provider-hosted fields.\n- Require explicit user confirmation before `action_confirm_payment_card` and booking actions.\n\n## Response mapping\n\nMap Brek response as:\n- `data.result.status` -> state machine key for UI and orchestration\n- `data.result.message.text` -> user-visible assistant text\n- `data.result.artifacts` -> structured payload (shortlist, payment setup URL, booking metadata)\n\n## Error handling\n\n- `400`: request validation failed. Fix payload.\n- `401\u002F403`: API key issue. Stop calls. Tell user to rotate or provision key through their internal owner or approved support channel.\n- `404`: session not found or wrong tenant.\n- `409`: actor\u002Fsession mismatch. Recreate correct session.\n- `429`: throttle locally and retry by `retry-after`.\n- `5xx`: retry with backoff, then open breaker.\n\n## References\n\nRead only what you need:\n- API payload templates: `references\u002Fapi-templates.md`\n- Call-control and anti-abuse policy: `references\u002Fcall-control.md`\n- Payment and billing orchestration: `references\u002Fpayment-and-billing.md`\n",{"name":5,"metadata":24,"description":7},{"config_paths":25,"required_env_vars":26,"always_on_presence":27,"primary_credential":28,"storage_requirements":29,"autonomous_invocation":27,"required_runtime_inputs":30},"none","BREK_BASE_URL,BREK_PARTNER_API_KEY","false","BREK_PARTNER_API_KEY","durable idempotency dedupe store,budget counter store,usage metering log","actorId,workspaceId,partnerId,clientActionId","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fleo9\u002Fbrek-ai",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill brek-ai-skill",{"tool":46,"command":47},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill brek-ai-skill",{"tool":49,"command":50},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill brek-ai-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fleo9\u002Fbrek-ai\u002FSKILL.md",true,[],[55,63,70,77,84,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":62},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":62},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":62},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":62},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":62},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]