[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DDK4DFXNP3Y1ZAB1BAXAX":3,"skill-same:01M75DDK4DFXNP3Y1ZAB1BAXAX":66},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M75DDK4DFXNP3Y1ZAB1BAXAX","calendar-scheduling",null,"Schedule meetings, check availability, and manage calendars across Google, Outlook, and CalDAV. Routes to focused sub-skills for datetime resolution and calendar scheduling.\nAlso available as temporal-cortex. Both listings install the same MCP server and share the same source code.","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\u002Fbillylui\u002Fcalendar-scheduling\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: calendar-scheduling\ndescription: |-\n  Schedule meetings, check availability, and manage calendars across Google, Outlook, and CalDAV. Routes to focused sub-skills for datetime resolution and calendar scheduling.\n  Also available as temporal-cortex. Both listings install the same MCP server and share the same source code.\nlicense: MIT\ncompatibility: |-\n  Requires npx (Node.js 18+) or Docker to install the MCP server binary. python3 optional (configure\u002Fstatus scripts). Stores OAuth credentials at ~\u002F.config\u002Ftemporal-cortex\u002F. Works with Claude Code, Claude Desktop, Cursor, Windsurf, and any MCP-compatible client.\nmetadata:\n  author: temporal-cortex\n  version: \"0.9.1\"\n  mcp-server: \"@temporal-cortex\u002Fcortex-mcp\"\n  homepage: \"https:\u002F\u002Ftemporal-cortex.com\"\n  repository: \"https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\"\n  openclaw:\n    install:\n      - kind: node\n        package: \"@temporal-cortex\u002Fcortex-mcp@0.9.1\"\n        bins: [cortex-mcp]\n    requires:\n      bins:\n        - npx\n      config:\n        - ~\u002F.config\u002Ftemporal-cortex\u002Fcredentials.json\n        - ~\u002F.config\u002Ftemporal-cortex\u002Fconfig.json\n---\n\n# Temporal Cortex — Calendar Scheduling Router\n\nThis is the router skill for Temporal Cortex calendar operations. It routes your task to the right sub-skill based on intent.\n\n## Who is this for?\n\n**If you're an individual user** (Claude Desktop, Cursor, OpenClaw, Manus) — install this skill and let your AI agent manage your calendar. Connect your Google, Outlook, or CalDAV calendars, and the agent handles availability, scheduling, and booking without double-booking.\n\n**If you're building a product with scheduling** — use the same MCP server as your scheduling backend. 18 tools, atomic booking via Two-Phase Commit, and cross-provider availability merging. See the [REST API reference](https:\u002F\u002Ftemporal-cortex.com\u002Fdocs\u002Frest-api) and [Platform docs](https:\u002F\u002Fapp.temporal-cortex.com) for developer integration.\n\n## Source & Provenance\n\n- **Homepage:** [temporal-cortex.com](https:\u002F\u002Ftemporal-cortex.com)\n- **Source code:** [github.com\u002Ftemporal-cortex\u002Fmcp](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) (open-source Rust)\n- **npm package:** [@temporal-cortex\u002Fcortex-mcp](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@temporal-cortex\u002Fcortex-mcp)\n- **Skills repo:** [github.com\u002Ftemporal-cortex\u002Fskills](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills)\n\n## Sub-Skills\n\n| Sub-Skill | When to Use | Tools |\n|-----------|------------|-------|\n| [temporal-cortex-datetime](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftemporal-cortex-datetime\u002FSKILL.md) | Time resolution, timezone conversion, duration math. No credentials needed — works immediately. | 5 tools (Layer 1) |\n| [temporal-cortex-scheduling](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftemporal-cortex-scheduling\u002FSKILL.md) | List calendars, events, free slots, availability, RRULE expansion, booking, contact search, and proposal composition. Requires OAuth credentials. | 14 tools (Layers 0-4) |\n\n## Routing Table\n\n| User Intent | Route To |\n|------------|----------|\n| \"What time is it?\", \"Convert timezone\", \"How long until...\" | **temporal-cortex-datetime** |\n| \"Show my calendar\", \"Find free time\", \"Check availability\", \"Expand recurring rule\" | **temporal-cortex-scheduling** |\n| \"Book a meeting\", \"Schedule an appointment\" | **temporal-cortex-scheduling** |\n| \"Find someone's booking page\", \"Look up email for scheduling\" | **temporal-cortex-scheduling** |\n| \"Search my contacts for Jane\", \"Find someone's email\" | **temporal-cortex-scheduling** |\n| \"How should I schedule with this person?\" | **temporal-cortex-scheduling** |\n| \"Check someone else's availability\", \"Query public availability\" | **temporal-cortex-scheduling** |\n| \"Book a meeting with someone externally\", \"Request booking via Temporal Link\" | **temporal-cortex-scheduling** |\n| \"Send a scheduling proposal\", \"Compose meeting invite\" | **temporal-cortex-scheduling** |\n| \"Schedule a meeting next Tuesday at 2pm\" (full workflow) | **temporal-cortex-datetime** → **temporal-cortex-scheduling** |\n| \"Schedule with Jane\" (end-to-end) | **temporal-cortex-scheduling** (contact search → resolve → propose\u002Fbook) |\n\n## Core Workflow\n\nEvery calendar interaction follows this 7-step pattern:\n\n```\n0. Resolve Contact  →  search_contacts → resolve_contact   (find the person, determine scheduling path)\n1. Discover         →  list_calendars                       (know which calendars are available)\n2. Orient           →  get_temporal_context                  (know the current time)\n3. Resolve Time     →  resolve_datetime                     (turn human language into timestamps)\n4. Route            →  If open_scheduling: fast path. If email: backward-compat path.\n5. Query            →  list_events \u002F find_free_slots \u002F get_availability \u002F query_public_availability\n6. Act              →  Fast: check_availability → book_slot \u002F request_booking\n                       Backward-compat: compose_proposal → agent sends via channel MCP\n```\n\nStep 0 is optional — skip if the user provides an email directly. **Always start with step 1** when calendars are unknown. Never assume the current time. Never skip the conflict check before booking.\n\n## Safety Rules\n\n1. **Discover calendars first** — call `list_calendars` when you don't know which calendars are connected\n2. **Check before booking** — always call `check_availability` before `book_slot`. Never skip the conflict check.\n3. **Content safety** — all event summaries and descriptions pass through a prompt injection firewall before reaching the calendar API\n4. **Timezone awareness** — never assume the current time. Use `get_temporal_context` first.\n5. **Confirm before booking** — when running autonomously, present booking details to the user for confirmation before calling `book_slot` or `request_booking`.\n6. **Confirm contact selection** — when `search_contacts` returns multiple matches, always present candidates to the user and confirm which contact is correct before proceeding.\n7. **Confirm before sending proposals** — when using `compose_proposal`, always present the composed message to the user before sending via any channel. Never auto-send outreach.\n8. **Contact search is optional** — the full workflow works without it if the user provides an email directly. If contacts permission is not configured, ask the user for the email.\n\n## All 18 Tools (5 Layers)\n\n| Layer | Tools | Sub-Skill |\n|-------|-------|-----------|\n| 0 — Discovery | `resolve_identity`, `search_contacts`, `resolve_contact` | scheduling |\n| 1 — Temporal Context | `get_temporal_context`, `resolve_datetime`, `convert_timezone`, `compute_duration`, `adjust_timestamp` | datetime |\n| 2 — Calendar Ops | `list_calendars`, `list_events`, `find_free_slots`, `expand_rrule`, `check_availability` | scheduling |\n| 3 — Availability | `get_availability`, `query_public_availability` | scheduling |\n| 4 — Booking | `book_slot`, `request_booking`, `compose_proposal` | scheduling |\n\n## MCP Server Connection\n\nAll sub-skills share the [Temporal Cortex MCP server](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) (`@temporal-cortex\u002Fcortex-mcp`), a compiled Rust binary distributed as an npm package.\n\n**Install and startup lifecycle:**\n1. `npx` resolves `@temporal-cortex\u002Fcortex-mcp` from the npm registry (one-time, cached locally after first download)\n2. The postinstall script downloads the platform-specific binary from the [GitHub Release](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Ftag\u002Fmcp-v0.9.1) and verifies its SHA256 checksum against the embedded `checksums.json` — **installation halts on mismatch**\n3. The MCP server starts as a local process communicating over stdio (no listening ports)\n4. Layer 1 tools (datetime) execute as pure local computation — no further network access\n5. Layer 2-4 tools (calendar) make authenticated API calls to your configured providers (Google, Outlook, CalDAV)\n\n**Credential storage:** OAuth tokens are stored locally at `~\u002F.config\u002Ftemporal-cortex\u002Fcredentials.json` and read exclusively by the local MCP server process. No credential data is transmitted to Temporal Cortex servers. The binary's filesystem access is limited to `~\u002F.config\u002Ftemporal-cortex\u002F` — verifiable by inspecting the [open-source Rust code](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) or running under Docker where the mount is the only writable path.\n\n**File access:** The binary reads and writes only `~\u002F.config\u002Ftemporal-cortex\u002F` (credentials and config). No other filesystem writes.\n\n**Network scope:** After the initial npm download, Layer 1 tools make zero network requests. Layer 2–4 tools connect only to your configured calendar providers (`googleapis.com`, `graph.microsoft.com`, or your CalDAV server). In Local Mode (default), no calls to Temporal Cortex servers and no telemetry is collected. In Platform Mode, three tools (`resolve_identity`, `query_public_availability`, `request_booking`) call `api.temporal-cortex.com` for cross-user scheduling — no credential data is included in these calls.\n\n**Pre-run verification** (recommended before first use):\n1. Inspect the npm package without executing: `npm pack @temporal-cortex\u002Fcortex-mcp --dry-run`\n2. Verify checksums independently against the [GitHub Release](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Fdownload\u002Fmcp-v0.9.1\u002FSHA256SUMS.txt) (see verification pipeline below)\n3. For full containment, run in Docker instead of npx (see Docker containment below)\n\n**Verification pipeline:** Checksums are published independently at each [GitHub Release](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Ftag\u002Fmcp-v0.9.1) as `SHA256SUMS.txt` — verify the binary before first use:\n\n```bash\n# 1. Fetch checksums from GitHub (independent of the npm package)\ncurl -sL https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Fdownload\u002Fmcp-v0.9.1\u002FSHA256SUMS.txt\n\n# 2. Compare against the npm-installed binary\nshasum -a 256 \"$(npm root -g)\u002F@temporal-cortex\u002Fcortex-mcp\u002Fbin\u002Fcortex-mcp\"\n```\n\nAs defense-in-depth, the npm package also embeds `checksums.json` and the postinstall script compares SHA256 hashes during install — **installation halts on mismatch** (the binary is deleted, not executed). This automated check supplements, but does not replace, independent verification above.\n\n**Build provenance:** Binaries are cross-compiled from auditable Rust source in [GitHub Actions](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Factions) across 5 platforms (darwin-arm64, darwin-x64, linux-x64, linux-arm64, win32-x64). Source: [github.com\u002Ftemporal-cortex\u002Fmcp](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) (MIT-licensed). The CI workflow, build artifacts, and release checksums are all publicly inspectable.\n\n**Docker containment** (no Node.js on host, credential isolation via volume mount):\n\n```json\n{\n  \"mcpServers\": {\n    \"temporal-cortex\": {\n      \"command\": \"docker\",\n      \"args\": [\"run\", \"--rm\", \"-i\", \"-v\", \"~\u002F.config\u002Ftemporal-cortex:\u002Froot\u002F.config\u002Ftemporal-cortex\", \"cortex-mcp\"]\n    }\n  }\n}\n```\n\nBuild: `docker build -t cortex-mcp https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp.git`\n\n**Default setup** (npx): See [.mcp.json](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002F.mcp.json) for the standard `npx @temporal-cortex\u002Fcortex-mcp` configuration. For managed hosting, see [Platform Mode](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp#local-mode-vs-platform-mode) in the MCP repo.\n\nLayer 1 tools work immediately with zero configuration. Calendar tools require a one-time OAuth setup — run the [setup script](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002Fscripts\u002Fsetup.sh) or `npx @temporal-cortex\u002Fcortex-mcp auth google`.\n\n## Additional References\n\n- [Security Model](references\u002FSECURITY-MODEL.md) — Content sanitization, filesystem containment, network scope, tool annotations\n","# Temporal Cortex — Calendar Scheduling Router\n\nThis is the router skill for Temporal Cortex calendar operations. It routes your task to the right sub-skill based on intent.\n\n## Who is this for?\n\n**If you're an individual user** (Claude Desktop, Cursor, OpenClaw, Manus) — install this skill and let your AI agent manage your calendar. Connect your Google, Outlook, or CalDAV calendars, and the agent handles availability, scheduling, and booking without double-booking.\n\n**If you're building a product with scheduling** — use the same MCP server as your scheduling backend. 18 tools, atomic booking via Two-Phase Commit, and cross-provider availability merging. See the [REST API reference](https:\u002F\u002Ftemporal-cortex.com\u002Fdocs\u002Frest-api) and [Platform docs](https:\u002F\u002Fapp.temporal-cortex.com) for developer integration.\n\n## Source & Provenance\n\n- **Homepage:** [temporal-cortex.com](https:\u002F\u002Ftemporal-cortex.com)\n- **Source code:** [github.com\u002Ftemporal-cortex\u002Fmcp](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) (open-source Rust)\n- **npm package:** [@temporal-cortex\u002Fcortex-mcp](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@temporal-cortex\u002Fcortex-mcp)\n- **Skills repo:** [github.com\u002Ftemporal-cortex\u002Fskills](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills)\n\n## Sub-Skills\n\n| Sub-Skill | When to Use | Tools |\n|-----------|------------|-------|\n| [temporal-cortex-datetime](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftemporal-cortex-datetime\u002FSKILL.md) | Time resolution, timezone conversion, duration math. No credentials needed — works immediately. | 5 tools (Layer 1) |\n| [temporal-cortex-scheduling](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftemporal-cortex-scheduling\u002FSKILL.md) | List calendars, events, free slots, availability, RRULE expansion, booking, contact search, and proposal composition. Requires OAuth credentials. | 14 tools (Layers 0-4) |\n\n## Routing Table\n\n| User Intent | Route To |\n|------------|----------|\n| \"What time is it?\", \"Convert timezone\", \"How long until...\" | **temporal-cortex-datetime** |\n| \"Show my calendar\", \"Find free time\", \"Check availability\", \"Expand recurring rule\" | **temporal-cortex-scheduling** |\n| \"Book a meeting\", \"Schedule an appointment\" | **temporal-cortex-scheduling** |\n| \"Find someone's booking page\", \"Look up email for scheduling\" | **temporal-cortex-scheduling** |\n| \"Search my contacts for Jane\", \"Find someone's email\" | **temporal-cortex-scheduling** |\n| \"How should I schedule with this person?\" | **temporal-cortex-scheduling** |\n| \"Check someone else's availability\", \"Query public availability\" | **temporal-cortex-scheduling** |\n| \"Book a meeting with someone externally\", \"Request booking via Temporal Link\" | **temporal-cortex-scheduling** |\n| \"Send a scheduling proposal\", \"Compose meeting invite\" | **temporal-cortex-scheduling** |\n| \"Schedule a meeting next Tuesday at 2pm\" (full workflow) | **temporal-cortex-datetime** → **temporal-cortex-scheduling** |\n| \"Schedule with Jane\" (end-to-end) | **temporal-cortex-scheduling** (contact search → resolve → propose\u002Fbook) |\n\n## Core Workflow\n\nEvery calendar interaction follows this 7-step pattern:\n\n```\n0. Resolve Contact  →  search_contacts → resolve_contact   (find the person, determine scheduling path)\n1. Discover         →  list_calendars                       (know which calendars are available)\n2. Orient           →  get_temporal_context                  (know the current time)\n3. Resolve Time     →  resolve_datetime                     (turn human language into timestamps)\n4. Route            →  If open_scheduling: fast path. If email: backward-compat path.\n5. Query            →  list_events \u002F find_free_slots \u002F get_availability \u002F query_public_availability\n6. Act              →  Fast: check_availability → book_slot \u002F request_booking\n                       Backward-compat: compose_proposal → agent sends via channel MCP\n```\n\nStep 0 is optional — skip if the user provides an email directly. **Always start with step 1** when calendars are unknown. Never assume the current time. Never skip the conflict check before booking.\n\n## Safety Rules\n\n1. **Discover calendars first** — call `list_calendars` when you don't know which calendars are connected\n2. **Check before booking** — always call `check_availability` before `book_slot`. Never skip the conflict check.\n3. **Content safety** — all event summaries and descriptions pass through a prompt injection firewall before reaching the calendar API\n4. **Timezone awareness** — never assume the current time. Use `get_temporal_context` first.\n5. **Confirm before booking** — when running autonomously, present booking details to the user for confirmation before calling `book_slot` or `request_booking`.\n6. **Confirm contact selection** — when `search_contacts` returns multiple matches, always present candidates to the user and confirm which contact is correct before proceeding.\n7. **Confirm before sending proposals** — when using `compose_proposal`, always present the composed message to the user before sending via any channel. Never auto-send outreach.\n8. **Contact search is optional** — the full workflow works without it if the user provides an email directly. If contacts permission is not configured, ask the user for the email.\n\n## All 18 Tools (5 Layers)\n\n| Layer | Tools | Sub-Skill |\n|-------|-------|-----------|\n| 0 — Discovery | `resolve_identity`, `search_contacts`, `resolve_contact` | scheduling |\n| 1 — Temporal Context | `get_temporal_context`, `resolve_datetime`, `convert_timezone`, `compute_duration`, `adjust_timestamp` | datetime |\n| 2 — Calendar Ops | `list_calendars`, `list_events`, `find_free_slots`, `expand_rrule`, `check_availability` | scheduling |\n| 3 — Availability | `get_availability`, `query_public_availability` | scheduling |\n| 4 — Booking | `book_slot`, `request_booking`, `compose_proposal` | scheduling |\n\n## MCP Server Connection\n\nAll sub-skills share the [Temporal Cortex MCP server](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) (`@temporal-cortex\u002Fcortex-mcp`), a compiled Rust binary distributed as an npm package.\n\n**Install and startup lifecycle:**\n1. `npx` resolves `@temporal-cortex\u002Fcortex-mcp` from the npm registry (one-time, cached locally after first download)\n2. The postinstall script downloads the platform-specific binary from the [GitHub Release](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Ftag\u002Fmcp-v0.9.1) and verifies its SHA256 checksum against the embedded `checksums.json` — **installation halts on mismatch**\n3. The MCP server starts as a local process communicating over stdio (no listening ports)\n4. Layer 1 tools (datetime) execute as pure local computation — no further network access\n5. Layer 2-4 tools (calendar) make authenticated API calls to your configured providers (Google, Outlook, CalDAV)\n\n**Credential storage:** OAuth tokens are stored locally at `~\u002F.config\u002Ftemporal-cortex\u002Fcredentials.json` and read exclusively by the local MCP server process. No credential data is transmitted to Temporal Cortex servers. The binary's filesystem access is limited to `~\u002F.config\u002Ftemporal-cortex\u002F` — verifiable by inspecting the [open-source Rust code](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) or running under Docker where the mount is the only writable path.\n\n**File access:** The binary reads and writes only `~\u002F.config\u002Ftemporal-cortex\u002F` (credentials and config). No other filesystem writes.\n\n**Network scope:** After the initial npm download, Layer 1 tools make zero network requests. Layer 2–4 tools connect only to your configured calendar providers (`googleapis.com`, `graph.microsoft.com`, or your CalDAV server). In Local Mode (default), no calls to Temporal Cortex servers and no telemetry is collected. In Platform Mode, three tools (`resolve_identity`, `query_public_availability`, `request_booking`) call `api.temporal-cortex.com` for cross-user scheduling — no credential data is included in these calls.\n\n**Pre-run verification** (recommended before first use):\n1. Inspect the npm package without executing: `npm pack @temporal-cortex\u002Fcortex-mcp --dry-run`\n2. Verify checksums independently against the [GitHub Release](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Fdownload\u002Fmcp-v0.9.1\u002FSHA256SUMS.txt) (see verification pipeline below)\n3. For full containment, run in Docker instead of npx (see Docker containment below)\n\n**Verification pipeline:** Checksums are published independently at each [GitHub Release](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Ftag\u002Fmcp-v0.9.1) as `SHA256SUMS.txt` — verify the binary before first use:\n\n```bash\n# 1. Fetch checksums from GitHub (independent of the npm package)\ncurl -sL https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Freleases\u002Fdownload\u002Fmcp-v0.9.1\u002FSHA256SUMS.txt\n\n# 2. Compare against the npm-installed binary\nshasum -a 256 \"$(npm root -g)\u002F@temporal-cortex\u002Fcortex-mcp\u002Fbin\u002Fcortex-mcp\"\n```\n\nAs defense-in-depth, the npm package also embeds `checksums.json` and the postinstall script compares SHA256 hashes during install — **installation halts on mismatch** (the binary is deleted, not executed). This automated check supplements, but does not replace, independent verification above.\n\n**Build provenance:** Binaries are cross-compiled from auditable Rust source in [GitHub Actions](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp\u002Factions) across 5 platforms (darwin-arm64, darwin-x64, linux-x64, linux-arm64, win32-x64). Source: [github.com\u002Ftemporal-cortex\u002Fmcp](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp) (MIT-licensed). The CI workflow, build artifacts, and release checksums are all publicly inspectable.\n\n**Docker containment** (no Node.js on host, credential isolation via volume mount):\n\n```json\n{\n  \"mcpServers\": {\n    \"temporal-cortex\": {\n      \"command\": \"docker\",\n      \"args\": [\"run\", \"--rm\", \"-i\", \"-v\", \"~\u002F.config\u002Ftemporal-cortex:\u002Froot\u002F.config\u002Ftemporal-cortex\", \"cortex-mcp\"]\n    }\n  }\n}\n```\n\nBuild: `docker build -t cortex-mcp https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp.git`\n\n**Default setup** (npx): See [.mcp.json](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002F.mcp.json) for the standard `npx @temporal-cortex\u002Fcortex-mcp` configuration. For managed hosting, see [Platform Mode](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fmcp#local-mode-vs-platform-mode) in the MCP repo.\n\nLayer 1 tools work immediately with zero configuration. Calendar tools require a one-time OAuth setup — run the [setup script](https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills\u002Fblob\u002Fmain\u002Fscripts\u002Fsetup.sh) or `npx @temporal-cortex\u002Fcortex-mcp auth google`.\n\n## Additional References\n\n- [Security Model](references\u002FSECURITY-MODEL.md) — Content sanitization, filesystem containment, network scope, tool annotations\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":43},{"author":25,"version":26,"homepage":27,"openclaw":28,"mcp-server":41,"repository":42},"temporal-cortex","0.9.1","https:\u002F\u002Ftemporal-cortex.com",{"install":29,"requires":35},[30],{"bins":31,"kind":33,"package":34},[32],"cortex-mcp","node","@temporal-cortex\u002Fcortex-mcp@0.9.1",{"bins":36,"config":38},[37],"npx",[39,40],"~\u002F.config\u002Ftemporal-cortex\u002Fcredentials.json","~\u002F.config\u002Ftemporal-cortex\u002Fconfig.json","@temporal-cortex\u002Fcortex-mcp","https:\u002F\u002Fgithub.com\u002Ftemporal-cortex\u002Fskills","Requires npx (Node.js 18+) or Docker to install the MCP server binary. python3 optional (configure\u002Fstatus scripts). Stores OAuth credentials at ~\u002F.config\u002Ftemporal-cortex\u002F. Works with Claude Code, Claude Desktop, Cursor, Windsurf, and any MCP-compatible client.","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fbillylui\u002Fcalendar-scheduling",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":54,"prompt":63,"zipAvailable":64},[55,57,60],{"tool":37,"command":56},"npx skills add javimosch\u002Fopen-claw-skills --skill calendar-scheduling",{"tool":58,"command":59},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill calendar-scheduling",{"tool":61,"command":62},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill calendar-scheduling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbillylui\u002Fcalendar-scheduling\u002FSKILL.md",true,[],[67,75,82,89,96,103],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":74},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":74},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":74},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":74},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":74},"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",[],[]]