Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
temporal-cortex-datetime
Convert timezones, resolve natural language times ("next Tuesday at 2pm"), compute durations, and adjust timestamps with DST awareness. No credentials needed...
skill openclawclawhub Free
Convert timezones, resolve natural language times ("next Tuesday at 2pm"), compute durations, and adjust timestamps with DST awareness. No credentials needed...
β¬ 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/DATETIME-TOOLS.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
Temporal Context & Datetime Resolution
5 tools for temporal orientation and datetime computation. All tools execute locally within the compiled MCP server binary β no external API calls, no network access at runtime, no credential files. The binary is installed once via npm (or built from source with Docker) and all subsequent executions are fully offline. No OAuth or credentials required. Timezone and week-start preferences are stored in config.json. Unset fields default to system timezone and Monday week-start.
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
Tools
ToolWhen to Useget_temporal_contextFirst call in any session. Returns current time, timezone, UTC offset, DST status, DST prediction, day of week.resolve_datetimeConvert human expressions to RFC 3339. Supports 60+ patterns: "next Tuesday at 2pm", "tomorrow morning", "+2h", "start of next week", "third Friday of March".convert_timezoneConvert RFC 3339 datetime between IANA timezones.compute_durationDuration between two timestamps (days, hours, minutes).adjust_timestampDST-aware timestamp adjustment. "+1d" across spring-forward = same wall-clock time.
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) All 5 datetime tools execute locally β zero network access, zero filesystem writes, no credentials Network access: Only during the initial npm download. Once cached, subsequent launches are fully offline. The 5 datetime tools make zero network requests β all computation is local. File access: The binary reads ~/.config/temporal-cortex/config.json for timezone and week-start preferences. Unset or missing fields default to system values. No filesystem writes. No credential files accessed. No credentials required. Unlike the scheduling skill, this skill needs no OAuth tokens or API keys. 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 (recommended for maximum isolation β zero Node.js dependency, zero host filesystem access, zero network after build): { "mcpServers": { "temporal-cortex": { "command": "docker", "args": ["run", "--rm", "-i", "--network=none", "cortex-mcp"] } } } Build: docker build -t cortex-mcp https://github.com/temporal-cortex/mcp.git β No volume mount needed since the datetime skill requires no OAuth tokens or credential files. The --network=none flag enforces the zero-network guarantee at the OS level.
Critical Rules
Always call get_temporal_context before time-dependent work β never assume the time or timezone. Resolve before querying β convert "next Tuesday at 2pm" to RFC 3339 with resolve_datetime before passing to calendar tools. Timezone awareness β all datetime tools produce RFC 3339 with timezone offsets.
resolve_datetime Expression Patterns
The expression parser supports 60+ patterns across 10 categories: CategoryExamplesRelative"now", "today", "tomorrow", "yesterday"Named days"next Monday", "this Friday", "last Wednesday"Time of day"morning" (09:00), "noon", "evening" (18:00), "eob" (17:00)Clock time"2pm", "14:00", "3:30pm"Offsets"+2h", "-30m", "in 2 hours", "3 days ago"Compound"next Tuesday at 2pm", "tomorrow morning", "this Friday at noon"Period boundaries"start of week", "end of month", "start of next week", "end of last month"Ordinal weekday"first Monday of March", "third Friday of next month"RFC 3339 passthrough"2026-03-15T14:00:00-04:00" (returned as-is)Week start awareUses configured WEEK_START (Monday default, Sunday option)
Get Current Time Context
get_temporal_context() β utc, local, timezone, utc_offset, dst_active, dst_next_transition, day_of_week, iso_week, is_weekday, day_of_year, week_start
Resolve a Meeting Time
resolve_datetime("next Tuesday at 2pm") β resolved_utc, resolved_local, timezone, interpretation
Convert Across Timezones
1. get_temporal_context β user's timezone 2. convert_timezone(datetime: "2026-03-15T14:00:00-04:00", target_timezone: "Asia/Tokyo") β same moment in Tokyo time with DST and offset info
Calculate Duration
compute_duration(start: "2026-03-15T09:00:00-04:00", end: "2026-03-15T17:30:00-04:00") β total_seconds: 30600, hours: 8, minutes: 30, human_readable: "8 hours 30 minutes"
DST-Aware Adjustment
adjust_timestamp( datetime: "2026-03-07T23:00:00-05:00", adjustment: "+1d", timezone: "America/New_York" ) β same wall-clock time (23:00) on March 8, even though DST spring-forward occurs
Additional References
Datetime Tools Reference β Complete input/output schemas for all 5 tools
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs
- SKILL.md
- references/DATETIME-TOOLS.md