claw-history
// 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.
$ git log --oneline --stat
stars:1,933
forks:367
updated:March 4, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
nameclaw-history
descriptionProvide 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)
- Earliest and recent
memory/YYYY-MM-DD*.mdfiles (find first/last dates). MEMORY.mdfor long-term milestones.- Available session inventory/history (main + sub-agent sessions when accessible).
- Current conversation/tool logs.
If any source is unavailable, explicitly state that gap.
Workflow
- Determine earliest known timestamp (“birth marker”) from records.
- Collect confirmed actions across all available periods.
- De-duplicate overlapping entries from memory/session logs.
- Sort strictly oldest → newest.
- Mark each entry as:
- Confirmed (direct evidence), or
- Inferred (indirect/partial evidence).
- 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.