Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
temporal-cortex-scheduling
List events, find free slots, and book meetings across Google Calendar, Outlook, and CalDAV. Multi-calendar availability merging, recurring event expansion,...
skill openclawclawhub Free
List events, find free slots, and book meetings across Google Calendar, Outlook, and CalDAV. Multi-calendar availability merging, recurring event expansion,...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/BOOKING-SAFETY.md, references/CALENDAR-TOOLS.md, references/MULTI-CALENDAR.md, references/OPEN-SCHEDULING.md, references/RRULE-GUIDE.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.9.1
Provenance
- Publisher
- billylui
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Calendar Scheduling & Booking
14 tools (Layers 0, 2โ4) for contact resolution, calendar discovery, event querying, free slot finding, availability checking, RRULE expansion, atomic booking, Open Scheduling, and proposal composition. 12 read-only tools + 2 write tools (book_slot, request_booking).
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
Runtime
These tools run inside 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) Calendar tools make authenticated API calls to your configured providers (Google Calendar API, Microsoft Graph API, CalDAV endpoints) 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: Calendar tools connect only to your configured 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
Layer 0 โ Discovery
ToolWhen to Useresolve_identityDNS for Human Time: resolve an email, phone, or agent ID to a Temporal Cortex slug. Call before query_public_availability. Platform Mode only.search_contactsSearch the user's address book by name (Google People API, Microsoft Graph). Returns matching contacts with emails, phones, organization, and job title. Opt-in โ requires contacts permission.resolve_contactGiven a confirmed contact's email, determine the best scheduling path: Open Scheduling (instant booking), email, or phone. Chains with resolve_identity when Platform API is available.
Layer 2 โ Calendar Operations
ToolWhen to Uselist_calendarsFirst call when calendars are unknown. Returns all connected calendars with provider-prefixed IDs, names, labels, primary status, and access roles.list_eventsList events in a time range. TOON format by default (~40% fewer tokens than JSON). Use provider-prefixed IDs for multi-calendar: "google/primary", "outlook/work".find_free_slotsFind available gaps in a calendar. Set min_duration_minutes for minimum slot length.expand_rruleExpand recurrence rules (RFC 5545) into concrete instances. Handles DST, BYSETPOS, EXDATE, leap years. Use dtstart as local datetime (no timezone suffix).check_availabilityCheck if a specific time slot is free. Checks both events and active booking locks.
Layer 3 โ Availability
ToolWhen to Useget_availabilityMerged free/busy view across multiple calendars. Pass calendar_ids array. Privacy: "opaque" (default, hides sources) or "full".query_public_availabilityCheck another user's public availability by Temporal Link slug. Pass the slug and date to find their open time slots. Platform Mode only.
Layer 4 โ Booking
ToolWhen to Usebook_slotBook a time slot atomically. Lock โ verify โ write โ release. Always check_availability first.request_bookingBook on another user's public calendar by Temporal Link slug. Requires Platform Mode.compose_proposalCompose a scheduling proposal message for email, Slack, or SMS. Formats proposed times in the recipient's timezone with an optional Temporal Link self-serve booking URL. Does NOT send โ returns formatted text for the agent to send via its channel MCP.
Critical Rules
Discover calendars first โ call list_calendars when you don't know which calendars are connected. Use the returned provider-prefixed IDs for all subsequent calls. Use provider-prefixed IDs for multi-calendar setups: "google/primary", "outlook/work", "caldav/personal". Bare IDs (e.g., "primary") route to the default provider. TOON is the default format โ output uses TOON (~40% fewer tokens than JSON). Pass format: "json" only if you need structured parsing. Check before booking โ always call check_availability before book_slot. Never skip the conflict check. Content safety โ event summaries and descriptions pass through a sanitization firewall before reaching the calendar API. Timezone awareness โ all tools accept RFC 3339 with timezone offsets. Never use bare dates. Confirm before booking โ when running autonomously, always present booking details (time, calendar, summary) to the user and wait for confirmation before calling book_slot or request_booking. Confirm contact selection โ when search_contacts returns multiple matches, present candidates to the user and confirm which contact is correct. Never auto-select. Confirm before sending proposals โ when using compose_proposal, present the composed message to the user before sending. Never auto-send outreach. Contact search is optional โ if contacts permission is not configured, ask the user for the email directly. The workflow works without contact search.
Full Booking Workflow
0. Resolve Contact โ search_contacts("Jane") โ resolve_contact(jane@example.com) (skip if user provides email directly) 1. Discover โ list_calendars 2. Orient โ get_temporal_context (temporal-cortex-datetime) 3. Resolve Time โ resolve_datetime("next Tuesday at 2pm") (temporal-cortex-datetime) 4. Route โ If open_scheduling slug: fast path (query_public_availability โ request_booking) If email only: backward-compat path (find_free_slots โ compose_proposal) 5. Check โ check_availability(calendar_id, start, end) 6. Act โ Fast: book_slot / request_booking Backward-compat: compose_proposal โ agent sends via channel MCP If the slot is busy at step 5, use find_free_slots to suggest alternatives.
Open Scheduling Workflow (Platform Mode)
1. Identify โ resolve_identity("jane@example.com") โ slug: "jane-doe" 2. Orient โ get_temporal_context (temporal-cortex-datetime) 3. Discover โ query_public_availability(slug, date) โ available slots 4. Present โ Show top 3 options to user 5. Book โ request_booking(slug, start, end, title, attendee_email)
Two-Phase Commit Protocol
Agent calls book_slot(calendar_id, start, end, summary) โ โโ 1. LOCK โ Acquire exclusive lock on the time slot โ (in-memory local; Redis Redlock in Platform Mode) โ โโ 2. VERIFY โ Check for overlapping events and active locks โ โโ 3. WRITE โ Create event in calendar provider (Google/Outlook/CalDAV) โ Record event in shadow calendar โ โโ 4. RELEASE โ Release the exclusive lock If any step fails, the lock is released and the booking is aborted. No partial writes.
Schedule with a Contact (End-to-End)
1. search_contacts(query: "Jane") โ present candidates to user 2. User confirms: "Jane Doe (jane@example.com)" 3. resolve_contact(email: "jane@example.com") โ scheduling_paths 4. If open_scheduling: query_public_availability(slug, date) โ request_booking 5. If email only: a. find_free_slots(calendar_id, start, end) โ available times b. compose_proposal(contact_name, email, slots, timezone, format: "email") c. Present composed message to user โ user confirms โ send via channel MCP
List Events This Week
1. list_calendars โ discover connected calendars 2. get_temporal_context โ current time (use temporal-cortex-datetime) 3. resolve_datetime("start of this week") โ week start 4. resolve_datetime("end of this week") โ week end 5. list_events(calendar_id: "google/primary", start, end)
Find Free Time Across Calendars
1. list_calendars โ discover all connected calendars 2. get_availability( start, end, calendar_ids: ["google/primary", "outlook/work"], privacy: "full" ) โ merged free/busy blocks with source_count
Check and Book a Slot
1. check_availability(calendar_id: "google/primary", start, end) โ true/false 2. If free: book_slot(calendar_id: "google/primary", start, end, summary: "Team standup") 3. If busy: find_free_slots(calendar_id, start, end, min_duration_minutes: 30)
Expand Recurring Events
expand_rrule( rrule: "FREQ=MONTHLY;BYDAY=FR;BYSETPOS=-1", dtstart: "2026-01-01T10:00:00", โ local datetime, no timezone suffix timezone: "America/New_York", count: 12 ) โ last Friday of every month for 2026
Provider-Prefixed Calendar IDs
All calendar IDs use provider-prefixed format: FormatExampleRoutes togoogle/<id>"google/primary"Google Calendaroutlook/<id>"outlook/work"Microsoft Outlookcaldav/<id>"caldav/personal"CalDAV (iCloud, Fastmail)<id> (bare)"primary"Default provider
Privacy Modes
Modesource_countUse case"opaque" (default)Always 0Sharing availability externally"full"Actual countInternal use โ shows which calendars are busy
Tool Annotations (book_slot)
PropertyValueMeaningreadOnlyHintfalseCreates calendar eventsdestructiveHintfalseNever deletes or overwrites existing eventsidempotentHintfalseCalling twice creates two eventsopenWorldHinttrueMakes external API calls
Tool Annotations (request_booking)
PropertyValueMeaningreadOnlyHintfalseCreates calendar events on another user's calendardestructiveHintfalseNever deletes or overwrites existing eventsidempotentHintfalseCalling twice creates two bookingsopenWorldHinttrueCalls the Platform API
Tool Annotations (compose_proposal)
PropertyValueMeaningreadOnlyHinttruePure formatting โ no state modificationdestructiveHintfalseNever deletes dataidempotentHinttrueSame input always gives same outputopenWorldHintfalseNo external calls โ pure computation
Tool Annotations (search_contacts)
PropertyValueMeaningreadOnlyHinttrueReads contacts only โ no modificationsdestructiveHintfalseNever deletes contactsidempotentHinttrueSame query always gives same resultsopenWorldHinttrueCalls external contact API (Google People / Microsoft Graph)
Error Handling
ErrorAction"No credentials found"Run: npx @temporal-cortex/cortex-mcp auth google (or outlook / caldav)."Timezone not configured"Prompt for IANA timezone. Or run the auth command which configures timezone.Slot is busy / conflict detectedUse find_free_slots to suggest alternatives. Present options to user.Lock acquisition failedAnother agent is booking the same slot. Wait briefly and retry, or suggest alternative times.Content rejected by sanitizationRephrase the event summary/description. The firewall blocks prompt injection attempts.
Open Scheduling & Temporal Links
When a user has Open Scheduling enabled, their Temporal Link (book.temporal-cortex.com/{slug}) allows anyone to: Query availability โ GET /public/{slug}/availability?date=YYYY-MM-DD Book a meeting โ POST /public/{slug}/book with {start, end, title, attendee_email} Discover via Agent Card โ GET /public/{slug}/.well-known/agent-card.json
Workflow: Book via Temporal Link
User shares their Temporal Link Agent calls availability endpoint to find free slots Agent calls booking endpoint with selected slot Meeting is created on the user's default calendar See Temporal Links Reference for detailed API documentation.
Additional References
Calendar Tools Reference โ Complete input/output schemas for all 14 tools Multi-Calendar Guide โ Provider routing, labels, privacy modes, cross-provider operations RRULE Guide โ Recurrence rule patterns, DST edge cases, 5 LLM failure modes Booking Safety โ 2PC details, concurrent booking, lock TTL, content sanitization Temporal Links โ Open Scheduling endpoints, Agent Card integration, calendar routing Open Scheduling Guide โ Identity resolution, public availability, external booking via MCP tools
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- references/BOOKING-SAFETY.md
- references/CALENDAR-TOOLS.md
- references/MULTI-CALENDAR.md
- references/OPEN-SCHEDULING.md
- references/RRULE-GUIDE.md