Skills temporal-cortex

Name: temporal-cortex
Author: openclaw

install

source · Clone the upstream repo

git clone https://github.com/openclaw/skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/billylui/temporal-cortex" ~/.claude/skills/openclaw-skills-temporal-cortex && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/billylui/temporal-cortex" ~/.openclaw/skills/openclaw-skills-temporal-cortex && rm -rf "$T"

manifest: skills/billylui/temporal-cortex/SKILL.md

Temporal Cortex — Calendar Scheduling Router

This is the router skill for Temporal Cortex calendar operations. It routes your task to the right sub-skill based on intent.

Who is this for?

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.

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 and Platform docs for developer integration.

Source & Provenance

Homepage: temporal-cortex.com
Source code: github.com/temporal-cortex/mcp (open-source Rust)
npm package: @temporal-cortex/cortex-mcp
Skills repo: github.com/temporal-cortex/skills

Sub-Skills

Sub-Skill	When to Use	Tools
temporal-cortex-datetime	Time resolution, timezone conversion, duration math. No credentials needed — works immediately.	5 tools (Layer 1)
temporal-cortex-scheduling	List calendars, events, free slots, availability, RRULE expansion, booking, contact search, and proposal composition. Requires OAuth credentials.	14 tools (Layers 0-4)

Routing Table

User Intent	Route To
"What time is it?", "Convert timezone", "How long until..."	temporal-cortex-datetime
"Show my calendar", "Find free time", "Check availability", "Expand recurring rule"	temporal-cortex-scheduling
"Book a meeting", "Schedule an appointment"	temporal-cortex-scheduling
"Find someone's booking page", "Look up email for scheduling"	temporal-cortex-scheduling
"Search my contacts for Jane", "Find someone's email"	temporal-cortex-scheduling
"How should I schedule with this person?"	temporal-cortex-scheduling
"Check someone else's availability", "Query public availability"	temporal-cortex-scheduling
"Book a meeting with someone externally", "Request booking via Temporal Link"	temporal-cortex-scheduling
"Send a scheduling proposal", "Compose meeting invite"	temporal-cortex-scheduling
"Schedule a meeting next Tuesday at 2pm" (full workflow)	temporal-cortex-datetime → temporal-cortex-scheduling
"Schedule with Jane" (end-to-end)	temporal-cortex-scheduling (contact search → resolve → propose/book)

Core Workflow

Every calendar interaction follows this 7-step pattern:

0. Resolve Contact  →  search_contacts → resolve_contact   (find the person, determine scheduling path)
1. Discover         →  list_calendars                       (know which calendars are available)
2. Orient           →  get_temporal_context                  (know the current time)
3. Resolve Time     →  resolve_datetime                     (turn human language into timestamps)
4. Route            →  If open_scheduling: fast path. If email: backward-compat path.
5. Query            →  list_events / find_free_slots / get_availability / query_public_availability
6. Act              →  Fast: check_availability → book_slot / request_booking
                       Backward-compat: compose_proposal → agent sends via channel MCP

Step 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.

Safety Rules

Discover calendars first — call
```
list_calendars
```
when you don't know which calendars are connected
Check before booking — always call
```
check_availability
```
before
```
book_slot
```
. Never skip the conflict check.
Content safety — all event summaries and descriptions pass through a prompt injection firewall before reaching the calendar API
Timezone awareness — never assume the current time. Use
```
get_temporal_context
```
first.
Confirm before booking — when running autonomously, present booking details to the user for confirmation before calling
```
book_slot
```
or
```
request_booking
```
.
Confirm contact selection — when
```
search_contacts
```
returns multiple matches, always present candidates to the user and confirm which contact is correct before proceeding.
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.
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.

All 18 Tools (5 Layers)

Layer	Tools	Sub-Skill
0 — Discovery	`resolve_identity` , `search_contacts` , `resolve_contact`	scheduling
1 — Temporal Context	`get_temporal_context` , `resolve_datetime` , `convert_timezone` , `compute_duration` , `adjust_timestamp`	datetime
2 — Calendar Ops	`list_calendars` , `list_events` , `find_free_slots` , `expand_rrule` , `check_availability`	scheduling
3 — Availability	`get_availability` , `query_public_availability`	scheduling
4 — Booking	`book_slot` , `request_booking` , `compose_proposal`	scheduling

MCP Server Connection

All sub-skills share the Temporal Cortex MCP server (

@temporal-cortex/cortex-mcp

), a compiled Rust binary distributed as an npm package.

Install and startup lifecycle:

```
npx
```
resolves
```
@temporal-cortex/cortex-mcp
```
from the npm registry (one-time, cached locally after first download)
The postinstall script downloads the platform-specific binary from the GitHub Release and verifies its SHA256 checksum against the embedded
```
checksums.json
```
— installation halts on mismatch
The MCP server starts as a local process communicating over stdio (no listening ports)
Layer 1 tools (datetime) execute as pure local computation — no further network access
Layer 2-4 tools (calendar) make authenticated API calls to your configured providers (Google, Outlook, CalDAV)

Credential storage: OAuth tokens are stored locally at

~/.config/temporal-cortex/credentials.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

~/.config/temporal-cortex/

— verifiable by inspecting the open-source Rust code or running under Docker where the mount is the only writable path.

File access: The binary reads and writes only

~/.config/temporal-cortex/

(credentials and config). No other filesystem writes.

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.

Pre-run verification (recommended before first use):

Inspect the npm package without executing:

npm pack @temporal-cortex/cortex-mcp --dry-run

Verify checksums independently against the GitHub Release (see verification pipeline below)
For full containment, run in Docker instead of npx (see Docker containment below)

Verification pipeline: Checksums are published independently at each GitHub Release as

SHA256SUMS.txt

— verify the binary before first use:

# 1. Fetch checksums from GitHub (independent of the npm package)
curl -sL https://github.com/temporal-cortex/mcp/releases/download/mcp-v0.9.1/SHA256SUMS.txt

# 2. Compare against the npm-installed binary
shasum -a 256 "$(npm root -g)/@temporal-cortex/cortex-mcp/bin/cortex-mcp"

As 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.

Build provenance: Binaries are cross-compiled from auditable Rust source in GitHub Actions across 5 platforms (darwin-arm64, darwin-x64, linux-x64, linux-arm64, win32-x64). Source: github.com/temporal-cortex/mcp (MIT-licensed). The CI workflow, build artifacts, and release checksums are all publicly inspectable.

Docker containment (no Node.js on host, credential isolation via volume mount):

{
  "mcpServers": {
    "temporal-cortex": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "-v", "~/.config/temporal-cortex:/root/.config/temporal-cortex", "cortex-mcp"]
    }
  }
}

Build:

docker build -t cortex-mcp https://github.com/temporal-cortex/mcp.git

Default setup (npx): See .mcp.json for the standard

npx @temporal-cortex/cortex-mcp

configuration. For managed hosting, see Platform Mode in the MCP repo.

Layer 1 tools work immediately with zero configuration. Calendar tools require a one-time OAuth setup — run the setup script or

npx @temporal-cortex/cortex-mcp auth google

Additional References

Security Model — Content sanitization, filesystem containment, network scope, tool annotations