{
  "schemaVersion": "1.0",
  "item": {
    "slug": "temporal-cortex-datetime",
    "name": "temporal-cortex-datetime",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/billylui/temporal-cortex-datetime",
    "canonicalUrl": "https://clawhub.ai/billylui/temporal-cortex-datetime",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/temporal-cortex-datetime",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=temporal-cortex-datetime",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "references/DATETIME-TOOLS.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "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."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "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."
        },
        {
          "label": "Upgrade existing",
          "body": "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."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "slug": "temporal-cortex-datetime",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-05-05T05:40:33.796Z",
      "expiresAt": "2026-05-12T05:40:33.796Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=temporal-cortex-datetime",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=temporal-cortex-datetime",
        "contentDisposition": "attachment; filename=\"temporal-cortex-datetime-0.9.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null,
        "slug": "temporal-cortex-datetime"
      },
      "scope": "item",
      "summary": "Item download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this item.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/temporal-cortex-datetime"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/temporal-cortex-datetime",
    "agentPageUrl": "https://openagent3.xyz/skills/temporal-cortex-datetime/agent",
    "manifestUrl": "https://openagent3.xyz/skills/temporal-cortex-datetime/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/temporal-cortex-datetime/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "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."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "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."
      },
      {
        "label": "Upgrade existing",
        "body": "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."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Temporal Context & Datetime Resolution",
        "body": "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."
      },
      {
        "title": "Source & Provenance",
        "body": "Homepage: temporal-cortex.com\nSource code: github.com/temporal-cortex/mcp (open-source Rust)\nnpm package: @temporal-cortex/cortex-mcp\nSkills repo: github.com/temporal-cortex/skills"
      },
      {
        "title": "Tools",
        "body": "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."
      },
      {
        "title": "Runtime",
        "body": "These tools run inside the Temporal Cortex MCP server (@temporal-cortex/cortex-mcp), a compiled Rust binary distributed as an npm package.\n\nInstall and startup lifecycle:\n\nnpx resolves @temporal-cortex/cortex-mcp from the npm registry (one-time, cached locally after first download)\nThe 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\nThe MCP server starts as a local process communicating over stdio (no listening ports)\nAll 5 datetime tools execute locally — zero network access, zero filesystem writes, no credentials\n\nNetwork 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.\n\nFile 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.\n\nNo credentials required. Unlike the scheduling skill, this skill needs no OAuth tokens or API keys.\n\nPre-run verification (recommended before first use):\n\nInspect the npm package without executing: npm pack @temporal-cortex/cortex-mcp --dry-run\nVerify checksums independently against the GitHub Release (see verification pipeline below)\nFor full containment, run in Docker instead of npx (see Docker containment below)\n\nVerification pipeline: Checksums are published independently at each GitHub Release as SHA256SUMS.txt — verify the binary before first use:\n\n# 1. Fetch checksums from GitHub (independent of the npm package)\ncurl -sL https://github.com/temporal-cortex/mcp/releases/download/mcp-v0.9.1/SHA256SUMS.txt\n\n# 2. Compare against the npm-installed binary\nshasum -a 256 \"$(npm root -g)/@temporal-cortex/cortex-mcp/bin/cortex-mcp\"\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\nBuild 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.\n\nDocker containment (recommended for maximum isolation — zero Node.js dependency, zero host filesystem access, zero network after build):\n\n{\n  \"mcpServers\": {\n    \"temporal-cortex\": {\n      \"command\": \"docker\",\n      \"args\": [\"run\", \"--rm\", \"-i\", \"--network=none\", \"cortex-mcp\"]\n    }\n  }\n}\n\nBuild: 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."
      },
      {
        "title": "Critical Rules",
        "body": "Always call get_temporal_context before time-dependent work — never assume the time or timezone.\nResolve before querying — convert \"next Tuesday at 2pm\" to RFC 3339 with resolve_datetime before passing to calendar tools.\nTimezone awareness — all datetime tools produce RFC 3339 with timezone offsets."
      },
      {
        "title": "resolve_datetime Expression Patterns",
        "body": "The expression parser supports 60+ patterns across 10 categories:\n\nCategoryExamplesRelative\"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)"
      },
      {
        "title": "Get Current Time Context",
        "body": "get_temporal_context()\n→ utc, local, timezone, utc_offset, dst_active, dst_next_transition,\n  day_of_week, iso_week, is_weekday, day_of_year, week_start"
      },
      {
        "title": "Resolve a Meeting Time",
        "body": "resolve_datetime(\"next Tuesday at 2pm\")\n→ resolved_utc, resolved_local, timezone, interpretation"
      },
      {
        "title": "Convert Across Timezones",
        "body": "1. get_temporal_context → user's timezone\n2. convert_timezone(datetime: \"2026-03-15T14:00:00-04:00\", target_timezone: \"Asia/Tokyo\")\n   → same moment in Tokyo time with DST and offset info"
      },
      {
        "title": "Calculate Duration",
        "body": "compute_duration(start: \"2026-03-15T09:00:00-04:00\", end: \"2026-03-15T17:30:00-04:00\")\n→ total_seconds: 30600, hours: 8, minutes: 30, human_readable: \"8 hours 30 minutes\""
      },
      {
        "title": "DST-Aware Adjustment",
        "body": "adjust_timestamp(\n  datetime: \"2026-03-07T23:00:00-05:00\",\n  adjustment: \"+1d\",\n  timezone: \"America/New_York\"\n) → same wall-clock time (23:00) on March 8, even though DST spring-forward occurs"
      },
      {
        "title": "Additional References",
        "body": "Datetime Tools Reference — Complete input/output schemas for all 5 tools"
      }
    ],
    "body": "Temporal Context & Datetime Resolution\n\n5 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.\n\nSource & Provenance\nHomepage: temporal-cortex.com\nSource code: github.com/temporal-cortex/mcp (open-source Rust)\nnpm package: @temporal-cortex/cortex-mcp\nSkills repo: github.com/temporal-cortex/skills\nTools\nTool\tWhen to Use\nget_temporal_context\tFirst call in any session. Returns current time, timezone, UTC offset, DST status, DST prediction, day of week.\nresolve_datetime\tConvert human expressions to RFC 3339. Supports 60+ patterns: \"next Tuesday at 2pm\", \"tomorrow morning\", \"+2h\", \"start of next week\", \"third Friday of March\".\nconvert_timezone\tConvert RFC 3339 datetime between IANA timezones.\ncompute_duration\tDuration between two timestamps (days, hours, minutes).\nadjust_timestamp\tDST-aware timestamp adjustment. \"+1d\" across spring-forward = same wall-clock time.\nRuntime\n\nThese tools run inside the Temporal Cortex MCP server (@temporal-cortex/cortex-mcp), a compiled Rust binary distributed as an npm package.\n\nInstall and startup lifecycle:\n\nnpx resolves @temporal-cortex/cortex-mcp from the npm registry (one-time, cached locally after first download)\nThe 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\nThe MCP server starts as a local process communicating over stdio (no listening ports)\nAll 5 datetime tools execute locally — zero network access, zero filesystem writes, no credentials\n\nNetwork 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.\n\nFile 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.\n\nNo credentials required. Unlike the scheduling skill, this skill needs no OAuth tokens or API keys.\n\nPre-run verification (recommended before first use):\n\nInspect the npm package without executing: npm pack @temporal-cortex/cortex-mcp --dry-run\nVerify checksums independently against the GitHub Release (see verification pipeline below)\nFor full containment, run in Docker instead of npx (see Docker containment below)\n\nVerification pipeline: Checksums are published independently at each GitHub Release as SHA256SUMS.txt — verify the binary before first use:\n\n# 1. Fetch checksums from GitHub (independent of the npm package)\ncurl -sL https://github.com/temporal-cortex/mcp/releases/download/mcp-v0.9.1/SHA256SUMS.txt\n\n# 2. Compare against the npm-installed binary\nshasum -a 256 \"$(npm root -g)/@temporal-cortex/cortex-mcp/bin/cortex-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\nBuild 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.\n\nDocker containment (recommended for maximum isolation — zero Node.js dependency, zero host filesystem access, zero network after build):\n\n{\n  \"mcpServers\": {\n    \"temporal-cortex\": {\n      \"command\": \"docker\",\n      \"args\": [\"run\", \"--rm\", \"-i\", \"--network=none\", \"cortex-mcp\"]\n    }\n  }\n}\n\n\nBuild: 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.\n\nCritical Rules\nAlways call get_temporal_context before time-dependent work — never assume the time or timezone.\nResolve before querying — convert \"next Tuesday at 2pm\" to RFC 3339 with resolve_datetime before passing to calendar tools.\nTimezone awareness — all datetime tools produce RFC 3339 with timezone offsets.\nresolve_datetime Expression Patterns\n\nThe expression parser supports 60+ patterns across 10 categories:\n\nCategory\tExamples\nRelative\t\"now\", \"today\", \"tomorrow\", \"yesterday\"\nNamed days\t\"next Monday\", \"this Friday\", \"last Wednesday\"\nTime of day\t\"morning\" (09:00), \"noon\", \"evening\" (18:00), \"eob\" (17:00)\nClock time\t\"2pm\", \"14:00\", \"3:30pm\"\nOffsets\t\"+2h\", \"-30m\", \"in 2 hours\", \"3 days ago\"\nCompound\t\"next Tuesday at 2pm\", \"tomorrow morning\", \"this Friday at noon\"\nPeriod boundaries\t\"start of week\", \"end of month\", \"start of next week\", \"end of last month\"\nOrdinal weekday\t\"first Monday of March\", \"third Friday of next month\"\nRFC 3339 passthrough\t\"2026-03-15T14:00:00-04:00\" (returned as-is)\nWeek start aware\tUses configured WEEK_START (Monday default, Sunday option)\nCommon Patterns\nGet Current Time Context\nget_temporal_context()\n→ utc, local, timezone, utc_offset, dst_active, dst_next_transition,\n  day_of_week, iso_week, is_weekday, day_of_year, week_start\n\nResolve a Meeting Time\nresolve_datetime(\"next Tuesday at 2pm\")\n→ resolved_utc, resolved_local, timezone, interpretation\n\nConvert Across Timezones\n1. get_temporal_context → user's timezone\n2. convert_timezone(datetime: \"2026-03-15T14:00:00-04:00\", target_timezone: \"Asia/Tokyo\")\n   → same moment in Tokyo time with DST and offset info\n\nCalculate Duration\ncompute_duration(start: \"2026-03-15T09:00:00-04:00\", end: \"2026-03-15T17:30:00-04:00\")\n→ total_seconds: 30600, hours: 8, minutes: 30, human_readable: \"8 hours 30 minutes\"\n\nDST-Aware Adjustment\nadjust_timestamp(\n  datetime: \"2026-03-07T23:00:00-05:00\",\n  adjustment: \"+1d\",\n  timezone: \"America/New_York\"\n) → same wall-clock time (23:00) on March 8, even though DST spring-forward occurs\n\nAdditional References\nDatetime Tools Reference — Complete input/output schemas for all 5 tools"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/billylui/temporal-cortex-datetime",
    "publisherUrl": "https://clawhub.ai/billylui/temporal-cortex-datetime",
    "owner": "billylui",
    "version": "0.9.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/temporal-cortex-datetime",
    "downloadUrl": "https://openagent3.xyz/downloads/temporal-cortex-datetime",
    "agentUrl": "https://openagent3.xyz/skills/temporal-cortex-datetime/agent",
    "manifestUrl": "https://openagent3.xyz/skills/temporal-cortex-datetime/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/temporal-cortex-datetime/agent.md"
  }
}