360 Secure SkillHub
360 安全技能中心

Claw History

该 Skill 指示 Agent 不只汇报当前会话,而是按顺序检索最早的 memory 日期文件、MEMORY.md、可访问的会话历史与当前会话工具日志,去重后按时间升序输出含确认/推断标记、覆盖范围、缺口与置信度的完整操作时间线;来源不可用时需明确说明。

bluebirdback
bluebirdback
热度 86.28
最近更新 2026-05-11 17:25:52
分类:知识依赖:读写文件应用场景:笔记整理 / 摘要总结 / 报告撰写

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add claw-history
Metadata
name
claw-history
description
Provide a chronological history of all actions the agent has taken from the beginning (birth) until now. Use when the user asks for full lifetime timeline/accountability, "from birth until now," "everything you've done so far," "full action log," or equivalent chronological-history requests.

Claw History

Return the most complete, auditable lifetime timeline possible.

Core Rule

Do not default to current-session history. Reconstruct from earliest available evidence to now.

Required Data Sources (in this order)

  1. Earliest and recent memory/YYYY-MM-DD*.md files (find first/last dates).
  2. MEMORY.md for long-term milestones.
  3. Available session inventory/history (main + sub-agent sessions when accessible).
  4. Current conversation/tool logs.

If any source is unavailable, explicitly state that gap.

Workflow

  1. Determine earliest known timestamp (“birth marker”) from records.
  2. Collect confirmed actions across all available periods.
  3. De-duplicate overlapping entries from memory/session logs.
  4. Sort strictly oldest → newest.
  5. Mark each entry as:
    • Confirmed (direct evidence), or
    • Inferred (indirect/partial evidence).
  6. Add a final coverage summary with what was and was not visible.

Output Format

  • Birth marker: first known timestamp + source
  • Scope covered: date range + sources checked
  • Chronological history (oldest → newest):
    • YYYY-MM-DD HH:MM (TZ) — [Confirmed|Inferred] Action — Result
  • Gaps / limits: missing windows, inaccessible logs, uncertainty
  • Confidence: high / medium / low

Quality Rules

  • Never invent timestamps or actions.
  • Prefer evidence-backed entries over narrative summaries.
  • If exact time is unknown, use best-known granularity (date/session order) and label it.
  • Include source pointers when possible (file + line or log reference).
  • If user requested “all actions,” include both major milestones and notable operational actions.