什么是 时间时序推理？

时间技能是专为 AI 智能体设计的精密时序推理支架。通过与 temporal CLI 集成，它允许智能体将工作锚定在当前时刻，并将未来或过去的时间视为空间距离。该技能是 Openclaw Skills 的重要组成部分，提供了处理“自我移动”隐喻所需的逻辑，即智能体在时间中向前推进。这确保了所有截止日期和日程都能相对于当前时间进行准确计算。

使用此技能，智能体可以保持清晰的工作流视图，区分已完成的任务和未来的任务。它将原始日期数据转化为可操作的智能信息，使 Openclaw Skills 在项目管理和长期规划中更加高效。通过维护结构化的 time.md 文件，智能体在管理复杂逻辑序列的同时，能与现实世界的时钟保持同步。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ikana/time

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

时间时序推理 应用场景

• 跟踪项目里程碑和交付截止日期，确保按时完成。
• 安排周期性仪式，如冲刺复盘、站会或客户会议。
• 推理相对时间偏移（如“3天后”或“2周前”），无需手动计算。
• 使用有序序列构建复杂的发布周期和依赖链。

1. 运行 init 命令建立 time.md 文件，以当前时间戳作为参考点。
2. 使用 add 命令，利用相对时长、特定日期或 ISO 格式将事件插入时间线。
3. 执行 refresh 命令，将 NOW 锚点与实际当前时间同步，并相应更新所有事件距离。
4. 分析生成的 Markdown 表格，理解不同项目事件之间的时序关系。
5. 将复杂的工作流组织成序列（Sequences）和跨度（Spans），为规划和执行提供高层级上下文。

时间时序推理 配置指南

要在 Openclaw Skills 生态系统中使用此技能，请确保 temporal 二进制文件已安装在您的路径中：

# 使用提供的脚本进行标准安装
./scripts/install.sh

# 针对 macOS (Apple Silicon) 的手动安装
mkdir -p ~/.local/bin && curl -L https://github.com/Ikana/temporal/releases/latest/download/temporal-darwin-arm64 -o ~/.local/bin/temporal && chmod +x ~/.local/bin/temporal

# 确保二进制文件在您的 shell 配置文件中可访问
export PATH="$HOME/.local/bin:$PATH"

# 初始化时间上下文文件
temporal init

时间时序推理 数据架构与分类体系

该技能在结构化的 time.md 文件中组织信息，分类如下：

name: time
slug: time
description: LLM temporal reasoning scaffold for the temporal CLI.
when_to_use: Use when a task involves dates, deadlines, scheduling, or relative time reasoning.
metadata: {"openclaw":{"requires":{"bins":["temporal"]}}}

time

Use temporal to anchor work at NOW and place events as spatial distances (ahead/behind) for reliable temporal reasoning.

Ego-Moving Metaphor (Required)

Use one frame only: you move forward through time.

• Future is ahead of you.
• Past is behind you.
• Correct: "We are approaching the deadline."
• Incorrect: "The deadline is approaching."

Prerequisites

• temporal must be on your $PATH.
• If temporal is not on $PATH, run scripts/install.sh from the skill directory.
• scripts/install.sh auto-detects OS/arch, verifies SHA-256 checksums from values bundled in the installer (not from the release checksums file), and installs to /usr/local/bin/temporal when writable or ~/.local/bin/temporal otherwise.
• Installer defaults to v0.1.0. You can override version/install dir with TEMPORAL_VERSION and TEMPORAL_INSTALL_DIR.
• For versions without a bundled checksum, set TEMPORAL_SHA256 to an independently obtained digest.
• Ensure ~/.local/bin is on your $PATH (for example, export PATH="$HOME/.local/bin:$PATH" in your shell profile).
• Note: The OS-specific curl examples below install binaries without checksum verification; prefer scripts/install.sh when possible.
• Install (macOS Apple Silicon): mkdir -p ~/.local/bin && curl -L https://github.com/Ikana/temporal/releases/latest/download/temporal-darwin-arm64 -o ~/.local/bin/temporal && chmod +x ~/.local/bin/temporal
• Install (macOS Intel): mkdir -p ~/.local/bin && curl -L https://github.com/Ikana/temporal/releases/latest/download/temporal-darwin-x64 -o ~/.local/bin/temporal && chmod +x ~/.local/bin/temporal
• Install (Linux x64): mkdir -p ~/.local/bin && curl -L https://github.com/Ikana/temporal/releases/latest/download/temporal-linux-x64 -o ~/.local/bin/temporal && chmod +x ~/.local/bin/temporal
• Install (Linux ARM64): mkdir -p ~/.local/bin && curl -L https://github.com/Ikana/temporal/releases/latest/download/temporal-linux-arm64 -o ~/.local/bin/temporal && chmod +x ~/.local/bin/temporal
• Install a custom version with explicit checksum: TEMPORAL_VERSION=v0.1.1 TEMPORAL_SHA256= ./scripts/install.sh
• Install/build instructions: github.com/Ikana/temporal

Quick Start

temporal init
temporal add "Sprint review" --on "2026-02-21" --type ceremony
temporal add "v0.3.0 deadline" --in "13 days" --type milestone --notes "new auth flow"
temporal show

Commands

init [--timezone ] [--force]

Create time.md with NOW as the anchor. Use --force to overwrite an existing file.

now [--timezone ]

Update only the NOW section timestamp metadata. Does not recalculate event distances.

add (--in | --on | --at ) [--type ] [--notes ]

Add one event with exactly one time selector:

• --in: relative duration ("3 days", "in 4 hours", "2 days ago")
• --on: date input ("2026-03-01", "tomorrow", "next Monday")
• --at: ISO datetime ("2026-02-20T14:00:00Z")

show

Print full time.md to stdout.

past

Print NOW + the Behind (Past) timeline section.

ahead

Print NOW + the Ahead (Future) timeline section.

refresh

Move NOW to current time and recalculate all event distances/order.

remove

Remove an event from timeline and sequences.

seq [event3...]

Create/update a named sequence chain.

span --from --to

Create/update a named duration span. --from must be before --to.

Annotated time.md Format

# Time Context

## Now
- **timestamp**: 2026-02-19T09:00:00.000Z   
- **weekday**: Thursday
- **week**: 8 of 52
- **quarter**: Q1 2026
- **timezone**: Europe/Amsterdam

## Timeline

### Behind (Past)
| distance | event | type | notes | iso |
|----------|-------|------|-------|-----|
| 1 day behind | bug #42 reported | issue | auth timeout | 2026-02-18T10:00:00.000Z |

### Ahead (Future)
| distance | event | type | notes | iso |
|----------|-------|------|-------|-----|
| 2 days ahead | sprint review | ceremony | demo v0.2.1 | 2026-02-21T14:00:00.000Z |

## Sequences
### release-cycle
v0.2.0 released → bug #42 reported → [NOW] → sprint review → v0.3.0 deadline

## Durations
| span | from | to | length |
|------|------|----|--------|
| current sprint | 5 days behind | 2 days ahead | 7 days |

Scratch Pad Pattern (/tmp)

Use this for one-shot reasoning so project files stay clean:

cd /tmp
temporal init --force
temporal add "Draft due" --on "2026-02-25"
temporal add "Client review" --in "3 days"
temporal show
# draft your output using the timeline
rm -f time.md

Sequences

Use sequences to express ordered chains for planning:

temporal seq "release-cycle" "RFC drafted" "Implementation starts" "Testing" "Launch"

show places [NOW] at the correct position relative to sequence events.

Spans

Use spans for time windows:

temporal span "Sprint 12" --from "2026-02-17" --to "2026-02-28"

The Durations table shows from/to distances and total length.

Key Rules

• Run temporal refresh before reading time.md when it may be stale.
• Event names must be unique; remove before re-adding the same name.
• Markdown timeline output is written to stdout.
• Errors/warnings are written to stderr.
• temporal is fully non-interactive (no prompts).