Search

PythonReactSEOPDF
OpenClaw

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.

bluebirdback0 source installs☆ 0 Repository stars

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install bluebirdback/claw-history

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

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.

Source information

Source
github
Repository
openclaw/skills
Path
skills/bluebirdback/claw-history
Version
—
Commit
d3abf0e3b536954a28dc774e9aa39aeabde84331
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

README

claw-history

claw-history provides a chronological history of the agent’s actions from earliest available records (“birth marker”) to now.

Beginner quick start

Just tell your OpenClaw to install this skill and run it.

Important: Data quality for full-lifetime history

The skill works without extra hooks, but timeline completeness is much better when these hooks are enabled:

  • session-memory (recommended): saves session context on /new into workspace/memory/...
  • command-logger (strongly recommended): writes command events to ~/.openclaw/logs/commands.log
  • boot-md (optional): startup automation; not required for timeline reconstruction

Enable recommended hooks

openclaw hooks enable session-memory
openclaw hooks enable command-logger

Verify

openclaw hooks info session-memory
openclaw hooks info command-logger

Notes

  • command-logger is not mandatory for claw-history, but is useful for auditable command-level history.
  • If source coverage is incomplete (missing old logs, disabled hooks, inaccessible sessions), claw-history reports gaps explicitly.

Credits

  • Author: C1 (OpenClaw) 🛠️
  • Project direction & validation: B3 (BlueBirdBack)

Build metadata

  • Initial packaging model: gpt-5.3-codex
  • Model note: model/runtime is environment-dependent and may change across releases.

Contact

  • Please use GitHub Issues on this repository for feedback and requests.

Extracted content

SKILL.md
# 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.
README
# claw-history

`claw-history` provides a chronological history of the agent’s actions from earliest available records (“birth marker”) to now.

## Beginner quick start

Just tell your OpenClaw to install this skill and run it.

## Important: Data quality for full-lifetime history

The skill works **without** extra hooks, but timeline completeness is much better when these hooks are enabled:

- **`session-memory`** (recommended): saves session context on `/new` into `workspace/memory/...`
- **`command-logger`** (strongly recommended): writes command events to `~/.openclaw/logs/commands.log`
- **`boot-md`** (optional): startup automation; not required for timeline reconstruction

## Enable recommended hooks

```bash
openclaw hooks enable session-memory
openclaw hooks enable command-logger
```

## Verify

```bash
openclaw hooks info session-memory
openclaw hooks info command-logger
```

## Notes

- `command-logger` is **not mandatory** for `claw-history`, but is useful for auditable command-level history.
- If source coverage is incomplete (missing old logs, disabled hooks, inaccessible sessions), `claw-history` reports gaps explicitly.

## Credits

- **Author:** C1 (OpenClaw) 🛠️
- **Project direction & validation:** B3 (BlueBirdBack)

## Build metadata

- **Initial packaging model:** `gpt-5.3-codex`
- **Model note:** model/runtime is environment-dependent and may change across releases.

## Contact

- Please use GitHub Issues on this repository for feedback and requests.

Related skills

OpenClaw

bambu-studio-ai

heyixuan2

Bambu Lab 3D printer control and automation. Activate when user mentions: printer status, 3D printing, slice, analyze model, generate 3D, AMS filament, print monitor, Bambu Lab, or any 3D printing task. Full pi...

OpenClaw

geo-optimization

capt-marbles

Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discove...

OpenClaw

0protocol

0isone

Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.

OpenClaw

0x0-messenger

eijiac24

Send and receive P2P messages using disposable numbers and PINs. No servers, no accounts. Use for human notifications, approval flows, and agent-to-agent communication.