v0.9.1 · March 2026 · Changelog · Website: temporal-cortex.com

Agent Skills that give AI agents scheduling capabilities — from finding contacts to booking or sending proposals. Built on Temporal Cortex open scheduling infrastructure with 18 tools across 5 layers. Compatible with 26+ agent platforms.

Zero-setup Layer 1: The temporal-cortex-datetime skill works immediately — no OAuth, no API keys, no configuration. All 5 temporal tools (timezone conversion, datetime resolution, duration math) are pure computation. Connect calendar providers only when you need calendar operations (Layers 2-4).

npx skills add temporal-cortex/skills

Or manually:

git clone https://github.com/temporal-cortex/skills.git
cp -r skills/temporal-cortex* ~/.claude/skills/

All skills share one MCP server. The included .mcp.json provides the default configuration:

{
  "mcpServers": {
    "temporal-cortex": {
      "command": "npx",
      "args": ["-y", "@temporal-cortex/cortex-mcp"]
    }
  }
}

Layer 1 tools (temporal context, datetime resolution) work immediately. Calendar tools require a one-time OAuth setup:

npx @temporal-cortex/cortex-mcp auth google     # Google Calendar
npx @temporal-cortex/cortex-mcp auth outlook    # Microsoft Outlook
npx @temporal-cortex/cortex-mcp auth caldav     # CalDAV (iCloud, Fastmail)

skills/
├── temporal-cortex/                  # Router skill
│   └── SKILL.md
├── temporal-cortex-datetime/         # Time & timezone tools (no credentials needed)
│   ├── SKILL.md
│   └── references/DATETIME-TOOLS.md
├── temporal-cortex-scheduling/       # Calendar ops + booking (needs OAuth)
│   ├── SKILL.md
│   └── references/
│       ├── BOOKING-SAFETY.md
│       ├── CALENDAR-TOOLS.md
│       ├── MULTI-CALENDAR.md
│       ├── OPEN-SCHEDULING.md
│       ├── RRULE-GUIDE.md
│       └── TEMPORAL-LINKS.md
└── calendar-scheduling/              # Legacy alias (auto-generated, do not edit)
    ├── SKILL.md
    └── references/
        └── SECURITY-MODEL.md
scripts/                              # Shared automation
├── setup.sh                          # OAuth + calendar connection
├── configure.sh                      # Timezone + week start
└── status.sh                         # Connection health check
assets/presets/                       # Workflow presets
├── meeting-coordinator.json
├── personal-assistant.json
├── recruiter-agent.json
└── team-coordinator.json

The skills follow the Agent Skills specification and work with Claude Code, Claude Desktop, OpenAI Codex CLI, Google Gemini CLI, GitHub Copilot, Cursor, Windsurf, and 20+ other platforms.

Yes. The temporal-cortex-datetime skill works immediately with zero setup — no OAuth or API keys needed. All 5 tools are pure computation with no external API calls.

The original calendar-scheduling skill was renamed to temporal-cortex at v0.5.1 when it was decomposed into a router + 2 focused sub-skills. The calendar-scheduling slug is still published on all directories as a backward-compatible alias — it is auto-generated from the router SKILL.md and installs the same MCP server.

The router skill (temporal-cortex) knows the full 7-step workflow and routes to the appropriate sub-skill based on intent. For a full scheduling workflow (resolve time → check availability → book), the agent progresses through datetime → scheduling sub-skills.

These skills are published on multiple directories:

• ClawHub — All 3 skills + legacy calendar-scheduling alias published individually (auto-published on release via CI)
• anthropics/skills — Official Anthropic skill directory (PR pending)
• awesome-claude-skills — Community curated list (PR pending)

• temporal-cortex/mcp — MCP server
• temporal-cortex/core — Truth Engine + TOON
• Agent Skills Specification — The open standard these skills follow

See CONTRIBUTING.md.

MIT