[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KG9QXVZPQFTG9MD1BPTTH":3,"skill-same:01M75KG9QXVZPQFTG9MD1BPTTH":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M75KG9QXVZPQFTG9MD1BPTTH","shipp",null,"Shipp is a real-time data connector. Use it to fetch authoritative, changing external data (e.g., sports schedules, live events) via the Shipp API.","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\u002Fkclonts\u002Fshipp\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: shipp\ndescription: >\n  Shipp is a real-time data connector. Use it to fetch authoritative, changing\n  external data (e.g., sports schedules, live events) via the Shipp API.\n\nmetadata:\n  author: Outsharp Inc.\n  version: 0.1.4\n\ncompatibility:\n  requirements:\n    - Internet access\n    - Shipp API Key (Get from https:\u002F\u002Fplatform.shipp.ai)\n  notes:\n    - All endpoints require authorization via API key.\n    - Requests and responses are JSON.\n\nallowed-tools:\n  - Bash(curl:https:\u002F\u002Fdocs.shipp.ai\u002F*)\n  - Bash(curl:https:\u002F\u002Fapi.shipp.ai\u002F*)\n  - Bash(curl:https:\u002F\u002Fplatform.shipp.ai\u002F*)\n  - Bash(jq:*)\n\n---\n\n# Shipp API\n\n[Shipp.ai](https:\u002F\u002Fshipp.ai) is the definitive source on real-time data.\n\n[Create an API Key](https:\u002F\u002Fplatform.shipp.ai)\n\nReference [docs](https:\u002F\u002Fdocs.shipp.ai).\n\nImplement as many tests as possible as soon as possible.\nVerify data and how the app uses data.\nBe flexible in schema — event rows are schema-flexible JSON and fields vary by sport, feed, and event.\n\nBase prefix:\n\n- All routes are under: `https:\u002F\u002Fapi.shipp.ai\u002Fapi\u002Fv1`\n\n---\n\n## Documentation & References\n\nAll detailed examples, request\u002Fresponse schemas, and walkthroughs live in the official docs. Always consult these before building:\n\n| Resource | URL |\n|---|---|\n| Full documentation | \u003Chttps:\u002F\u002Fdocs.shipp.ai> |\n| How-to guides | \u003Chttps:\u002F\u002Fdocs.shipp.ai\u002Fhow-to\u002F> |\n| Setup instructions | \u003Chttps:\u002F\u002Fdocs.shipp.ai\u002Finstructions\u002Fsetup\u002F> |\n| API reference | \u003Chttps:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F> |\n| Dashboard \u002F Signup | \u003Chttps:\u002F\u002Fplatform.shipp.ai\u002Fsignup> |\n| Billing management | \u003Chttps:\u002F\u002Fplatform.shipp.ai\u002Fbilling> |\n\n---\n\n## Authentication\n\nAll endpoints require an API key. The API supports several ways to provide it:\n\n| Method | Example |\n|---|---|\n| Query parameter `api_key` | `?api_key=YOUR_API_KEY` |\n| Query parameter `apikey` | `?apikey=YOUR_API_KEY` |\n| `Authorization` header (Bearer) | `Authorization: Bearer YOUR_API_KEY` |\n| `Authorization` header (Basic) | `Authorization: Basic base64(:YOUR_API_KEY)` |\n| `X-API-Key` header | `X-API-Key: YOUR_API_KEY` |\n| `User-API-Key` header | `User-API-Key: YOUR_API_KEY` |\n| `API-Key` header | `API-Key: YOUR_API_KEY` |\n\nPick whichever method works best for your client.\n\n---\n\n## Endpoints Overview\n\nBelow is a summary of the available endpoints. For full request\u002Fresponse examples, schemas, and field descriptions see the [API reference](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F).\n\n### `POST \u002Fapi\u002Fv1\u002Fconnections\u002Fcreate`\n\nCreate a new **raw-data connection** by providing natural-language `filter_instructions` that describe what games, teams, sports, or events you want to track.\n\nReturns a `connection_id` (ULID) you'll reuse for all subsequent runs.\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n### `POST \u002Fapi\u002Fv1\u002Fconnections\u002F{connectionId}`\n\nRun a connection and receive **raw event data**.\n\nSupports optional body fields for time-based filtering (`since`), cursor-based pagination (`since_event_id`), and result limiting (`limit`).\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n### `GET \u002Fapi\u002Fv1\u002Fconnections`\n\nList all connections in the current org scope.\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n### `GET \u002Fapi\u002Fv1\u002Fsports\u002F{sport}\u002Fschedule`\n\nRetrieve upcoming and recent games for a given sport (past 24 hours through next 7 days).\n\nSupported sport values: `nba`, `nfl`, `mlb`, `ncaafb`, `soccer` (case-insensitive).\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n---\n\n## Data Shape\n\nEvent rows returned in `data[]` are **schema-flexible** JSON objects. Fields vary by sport, feed, and event. Common field categories include:\n\n- **IDs:** `game_id`, `home_id`, `away_id`, `attribution_id`, `posession_id`\n- **Text \u002F enums:** `sport`, `home_name`, `away_name`, `game_clock`, `desc`, `type`, `category`\n- **Numeric:** `home_points`, `away_points`, `game_period`, `down`, `yards_first_down`, `location_yard_line`\n- **Time:** `wall_clock_start`, `wall_clock_end`\n\nNot every row has every field. Agents and clients should be defensive and handle missing keys.\n\nFor the complete field reference see [docs.shipp.ai](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F).\n\n---\n\n## Error Format\n\nErrors are returned as JSON with an `error` message, HTTP `status` code, and a `hint`:\n\n| Status | Meaning |\n|---|---|\n| 400 | Invalid request — check JSON and required fields |\n| 401 | Missing or invalid API key |\n| 402 | Billing changes required — manage at \u003Chttps:\u002F\u002Fplatform.shipp.ai\u002Fbilling> |\n| 403 | API key lacks access to this resource |\n| 404 | Connection not found or doesn't belong to your org |\n| 429 | Rate-limited — retry with backoff |\n| 5xx | Server error — retry later or contact support@shipp.ai |\n\n---\n\n## Response Compression\n\nInclude an `Accept-Encoding` header to receive compressed responses (`zstd`, `gzip`, or `deflate`). Compression is applied automatically when the response body exceeds 1 KB.\n\n---\n\n## Usage Tips\n\n- Keep `filter_instructions` short, explicit, and testable. Mention the sport\u002Fleague and scope.\n- Store and reuse `connection_id` — don't create a new connection per run. Creating connections has time and credit overhead.\n- Use `since_event_id` for efficient polling (cursor-based pagination). Send the lexicographically largest event ID you've received.\n- Use the schedule endpoint to discover `game_id`s and team names before creating connections.\n- Surface error `hint` messages directly to users when limits are hit.\n- Treat every field in `data[]` as optional — use existence checks and graceful fallbacks.\n- Log unknown data shapes in development so you can refine `filter_instructions`.\n- Polling interval: 5–30 seconds depending on domain and cost sensitivity.\n- Deduplicate events by keeping a rolling set of seen event IDs.\n- Consult the [how-to guides](https:\u002F\u002Fdocs.shipp.ai\u002Fhow-to\u002F) for end-to-end integration walkthroughs.\n\n---\n\n## Integration Pattern: \"Real-Time Contract\"\n\nWhen building a feature powered by Shipp, define a contract for each screen or agent loop:\n\n1. **User promise** — what must stay accurate while the user (or agent) is watching?\n2. **Triggering events** — what changes should cause UI updates or agent actions?\n3. **Data shape needed** — what fields do you need to render or decide?\n4. **Freshness window** — how old can the last update be before you warn the user?\n5. **Failure mode** — what do you show\u002Fdo if updates stop arriving?\n\nThen translate the contract into `filter_instructions` when creating the connection.\n\n---\n\n## Example Project: Alph Bot\n\n[**Alph Bot**](https:\u002F\u002Fgitlab.com\u002Foutsharp\u002Fshipp\u002Falph-bot) is an open-source automated trading bot that uses Shipp for real-time sports data and trades on prediction markets. It demonstrates a production-quality integration of the Shipp API.\n\n### How Alph Bot Uses Shipp\n\n1. **Game discovery** — Uses `GET \u002Fapi\u002Fv1\u002Fsports\u002F{sport}\u002Fschedule` to list available games:\n\n2. **Connection creation** — Creates a Shipp connection for a specific game, describing what events to track via `filter_instructions`.\n\n3. **Live polling** — Runs the connection on an interval, using `since_event_id` for cursor-based pagination to receive only new events since the last poll.\n\n4. **AI analysis** — Feeds the schema-flexible `data[]` events directly to Claude AI, which analyzes game state and estimates outcome probabilities.\n\n5. **Trading decisions** — Compares AI-estimated probabilities against Kalshi market prices to find value bets.\n\n### Key Takeaways from Alph Bot\n\n- **Reuse connections** — Alph Bot creates a connection once and polls it repeatedly, avoiding unnecessary creation overhead.\n- **Cursor pagination** — Uses `since_event_id` so each poll only returns new events, keeping responses fast and costs low.\n- **Defensive data handling** — Treats all fields as optional since the data shape varies by sport, game phase, and event type.\n- **Schedule-first workflow** — Discovers game IDs via the schedule endpoint before creating targeted connections.\n\nSee the [Alph Bot README](https:\u002F\u002Fgitlab.com\u002Foutsharp\u002Fshipp\u002Falph-bot) for full setup instructions.\n\n---\n\n## Versioning\n\nThis API is versioned under `\u002Fapi\u002Fv1\u002F`. New versions will be introduced under a new prefix when breaking changes are required.\n","# Shipp API\n\n[Shipp.ai](https:\u002F\u002Fshipp.ai) is the definitive source on real-time data.\n\n[Create an API Key](https:\u002F\u002Fplatform.shipp.ai)\n\nReference [docs](https:\u002F\u002Fdocs.shipp.ai).\n\nImplement as many tests as possible as soon as possible.\nVerify data and how the app uses data.\nBe flexible in schema — event rows are schema-flexible JSON and fields vary by sport, feed, and event.\n\nBase prefix:\n\n- All routes are under: `https:\u002F\u002Fapi.shipp.ai\u002Fapi\u002Fv1`\n\n---\n\n## Documentation & References\n\nAll detailed examples, request\u002Fresponse schemas, and walkthroughs live in the official docs. Always consult these before building:\n\n| Resource | URL |\n|---|---|\n| Full documentation | \u003Chttps:\u002F\u002Fdocs.shipp.ai> |\n| How-to guides | \u003Chttps:\u002F\u002Fdocs.shipp.ai\u002Fhow-to\u002F> |\n| Setup instructions | \u003Chttps:\u002F\u002Fdocs.shipp.ai\u002Finstructions\u002Fsetup\u002F> |\n| API reference | \u003Chttps:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F> |\n| Dashboard \u002F Signup | \u003Chttps:\u002F\u002Fplatform.shipp.ai\u002Fsignup> |\n| Billing management | \u003Chttps:\u002F\u002Fplatform.shipp.ai\u002Fbilling> |\n\n---\n\n## Authentication\n\nAll endpoints require an API key. The API supports several ways to provide it:\n\n| Method | Example |\n|---|---|\n| Query parameter `api_key` | `?api_key=YOUR_API_KEY` |\n| Query parameter `apikey` | `?apikey=YOUR_API_KEY` |\n| `Authorization` header (Bearer) | `Authorization: Bearer YOUR_API_KEY` |\n| `Authorization` header (Basic) | `Authorization: Basic base64(:YOUR_API_KEY)` |\n| `X-API-Key` header | `X-API-Key: YOUR_API_KEY` |\n| `User-API-Key` header | `User-API-Key: YOUR_API_KEY` |\n| `API-Key` header | `API-Key: YOUR_API_KEY` |\n\nPick whichever method works best for your client.\n\n---\n\n## Endpoints Overview\n\nBelow is a summary of the available endpoints. For full request\u002Fresponse examples, schemas, and field descriptions see the [API reference](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F).\n\n### `POST \u002Fapi\u002Fv1\u002Fconnections\u002Fcreate`\n\nCreate a new **raw-data connection** by providing natural-language `filter_instructions` that describe what games, teams, sports, or events you want to track.\n\nReturns a `connection_id` (ULID) you'll reuse for all subsequent runs.\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n### `POST \u002Fapi\u002Fv1\u002Fconnections\u002F{connectionId}`\n\nRun a connection and receive **raw event data**.\n\nSupports optional body fields for time-based filtering (`since`), cursor-based pagination (`since_event_id`), and result limiting (`limit`).\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n### `GET \u002Fapi\u002Fv1\u002Fconnections`\n\nList all connections in the current org scope.\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n### `GET \u002Fapi\u002Fv1\u002Fsports\u002F{sport}\u002Fschedule`\n\nRetrieve upcoming and recent games for a given sport (past 24 hours through next 7 days).\n\nSupported sport values: `nba`, `nfl`, `mlb`, `ncaafb`, `soccer` (case-insensitive).\n\n→ [Full docs & examples](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F)\n\n---\n\n## Data Shape\n\nEvent rows returned in `data[]` are **schema-flexible** JSON objects. Fields vary by sport, feed, and event. Common field categories include:\n\n- **IDs:** `game_id`, `home_id`, `away_id`, `attribution_id`, `posession_id`\n- **Text \u002F enums:** `sport`, `home_name`, `away_name`, `game_clock`, `desc`, `type`, `category`\n- **Numeric:** `home_points`, `away_points`, `game_period`, `down`, `yards_first_down`, `location_yard_line`\n- **Time:** `wall_clock_start`, `wall_clock_end`\n\nNot every row has every field. Agents and clients should be defensive and handle missing keys.\n\nFor the complete field reference see [docs.shipp.ai](https:\u002F\u002Fdocs.shipp.ai\u002Fapi-reference\u002F).\n\n---\n\n## Error Format\n\nErrors are returned as JSON with an `error` message, HTTP `status` code, and a `hint`:\n\n| Status | Meaning |\n|---|---|\n| 400 | Invalid request — check JSON and required fields |\n| 401 | Missing or invalid API key |\n| 402 | Billing changes required — manage at \u003Chttps:\u002F\u002Fplatform.shipp.ai\u002Fbilling> |\n| 403 | API key lacks access to this resource |\n| 404 | Connection not found or doesn't belong to your org |\n| 429 | Rate-limited — retry with backoff |\n| 5xx | Server error — retry later or contact support@shipp.ai |\n\n---\n\n## Response Compression\n\nInclude an `Accept-Encoding` header to receive compressed responses (`zstd`, `gzip`, or `deflate`). Compression is applied automatically when the response body exceeds 1 KB.\n\n---\n\n## Usage Tips\n\n- Keep `filter_instructions` short, explicit, and testable. Mention the sport\u002Fleague and scope.\n- Store and reuse `connection_id` — don't create a new connection per run. Creating connections has time and credit overhead.\n- Use `since_event_id` for efficient polling (cursor-based pagination). Send the lexicographically largest event ID you've received.\n- Use the schedule endpoint to discover `game_id`s and team names before creating connections.\n- Surface error `hint` messages directly to users when limits are hit.\n- Treat every field in `data[]` as optional — use existence checks and graceful fallbacks.\n- Log unknown data shapes in development so you can refine `filter_instructions`.\n- Polling interval: 5–30 seconds depending on domain and cost sensitivity.\n- Deduplicate events by keeping a rolling set of seen event IDs.\n- Consult the [how-to guides](https:\u002F\u002Fdocs.shipp.ai\u002Fhow-to\u002F) for end-to-end integration walkthroughs.\n\n---\n\n## Integration Pattern: \"Real-Time Contract\"\n\nWhen building a feature powered by Shipp, define a contract for each screen or agent loop:\n\n1. **User promise** — what must stay accurate while the user (or agent) is watching?\n2. **Triggering events** — what changes should cause UI updates or agent actions?\n3. **Data shape needed** — what fields do you need to render or decide?\n4. **Freshness window** — how old can the last update be before you warn the user?\n5. **Failure mode** — what do you show\u002Fdo if updates stop arriving?\n\nThen translate the contract into `filter_instructions` when creating the connection.\n\n---\n\n## Example Project: Alph Bot\n\n[**Alph Bot**](https:\u002F\u002Fgitlab.com\u002Foutsharp\u002Fshipp\u002Falph-bot) is an open-source automated trading bot that uses Shipp for real-time sports data and trades on prediction markets. It demonstrates a production-quality integration of the Shipp API.\n\n### How Alph Bot Uses Shipp\n\n1. **Game discovery** — Uses `GET \u002Fapi\u002Fv1\u002Fsports\u002F{sport}\u002Fschedule` to list available games:\n\n2. **Connection creation** — Creates a Shipp connection for a specific game, describing what events to track via `filter_instructions`.\n\n3. **Live polling** — Runs the connection on an interval, using `since_event_id` for cursor-based pagination to receive only new events since the last poll.\n\n4. **AI analysis** — Feeds the schema-flexible `data[]` events directly to Claude AI, which analyzes game state and estimates outcome probabilities.\n\n5. **Trading decisions** — Compares AI-estimated probabilities against Kalshi market prices to find value bets.\n\n### Key Takeaways from Alph Bot\n\n- **Reuse connections** — Alph Bot creates a connection once and polls it repeatedly, avoiding unnecessary creation overhead.\n- **Cursor pagination** — Uses `since_event_id` so each poll only returns new events, keeping responses fast and costs low.\n- **Defensive data handling** — Treats all fields as optional since the data shape varies by sport, game phase, and event type.\n- **Schedule-first workflow** — Discovers game IDs via the schedule endpoint before creating targeted connections.\n\nSee the [Alph Bot README](https:\u002F\u002Fgitlab.com\u002Foutsharp\u002Fshipp\u002Falph-bot) for full setup instructions.\n\n---\n\n## Versioning\n\nThis API is versioned under `\u002Fapi\u002Fv1\u002F`. New versions will be introduced under a new prefix when breaking changes are required.\n",{"name":5,"metadata":24,"description":27,"allowed-tools":28,"compatibility":33},{"author":25,"version":26},"Outsharp Inc.","0.1.4","Shipp is a real-time data connector. Use it to fetch authoritative, changing external data (e.g., sports schedules, live events) via the Shipp API.\n",[29,30,31,32],"Bash(curl:https:\u002F\u002Fdocs.shipp.ai\u002F*)","Bash(curl:https:\u002F\u002Fapi.shipp.ai\u002F*)","Bash(curl:https:\u002F\u002Fplatform.shipp.ai\u002F*)","Bash(jq:*)",{"notes":34,"requirements":37},[35,36],"All endpoints require authorization via API key.","Requests and responses are JSON.",[38,39],"Internet access","Shipp API Key (Get from https:\u002F\u002Fplatform.shipp.ai)","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fkclonts\u002Fshipp",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill shipp",{"tool":55,"command":56},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill shipp",{"tool":58,"command":59},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill shipp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fkclonts\u002Fshipp\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":71},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":71},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":71},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":71},"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":71},"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",[],[]]