Session Log

Lightweight session logging for OpenClaw agents. Automatically creates a timestamped session file on every session start (including /new resets) and appends...

Security Scan

The skill does what it says — lightweight local session logging using a small helper script and shell append instructions; nothing in the files or instructions requests unrelated credentials, network access, or unusual system privileges.

Purpose & Capability

Name/description match the provided artifacts: an instruction-only skill plus a small Python helper to create timestamped session files. Required resources are local filesystem paths which are appropriate for a logging utility.

Instruction Scope

SKILL.md only instructs creating files in user-specified sessions directories, appending one-line summaries, and globs for daily reports. It does not instruct reading unrelated files, accessing environment variables, or sending data to external endpoints.

Install Mechanism

No install spec; the skill is instruction-only with a tiny script. No downloads, package installs, or archive extraction are present.

Credentials

The skill requests no environment variables, credentials, or config paths. The helper script only needs a user-supplied --dir path and uses local time; this is proportional to its purpose.

Persistence & Privilege

The skill is not force-included (always:false) and does not attempt to modify other skills or global agent config. It writes files only to the directory the user supplies.

Assessment

This skill is straightforward and appears safe: review the small script (it is included) and run it with a directory you control (e.g., a workspace/sessions folder). Note the script uses CST (UTC+8) for timestamps — change if you need local time. Do not point --dir at sensitive system directories. Because it writes files where you tell it to, ensure appropriate filesystem permissions and avoid exposing the sessions folder to external services if those logs contain sensitive conversation content.

Lightweight session logging that survives /new resets.

How It Works

• On every session start → create sessions/YYYY-MM-DD_HH-MM_{agent}.md
• During conversation → append a one-line summary after each meaningful topic
• Daily report / cron → glob sessions/YYYY-MM-DD_*.md to reconstruct the full day

Session Startup (add to AGENTS.md)

5. Create `sessions/YYYY-MM-DD_HH-MM_{agent}.md` (local time) for this session

Get current time and create the file:

python3 /path/to/skills/session-log/scripts/new_session.py --agent main --dir /path/to/workspace/sessions

Or manually:

# Session 2026-03-04 09:30 | main

## Log

During Conversation

After each meaningful topic wraps up, append one line:

echo "- [topic] one-line summary" >> sessions/YYYY-MM-DD_HH-MM_{agent}.md

Keep it short — one line per topic, a dozen words max. This is a log, not a journal.

Multi-Agent Setup

Each agent writes to its own workspace sessions/ folder. The daily report reads all of them:

Agent	Path
main	/path/to/main-workspace/sessions/
writer	/path/to/writer-workspace/sessions/
coding	/path/to/coding-workspace/sessions/

Daily Report Integration

In the report cron's prepare step, glob today's session files from all agents:

ls /path/to/main-workspace/sessions/YYYY-MM-DD_*.md
ls /path/to/writer-workspace/sessions/YYYY-MM-DD_*.md
ls /path/to/coding-workspace/sessions/YYYY-MM-DD_*.md

Read each file and include summaries in the conversation recap section, tagged by agent ([main]/[writer]/[coding]).

File Format

# Session YYYY-MM-DD HH:MM | {agent}

## Log

- [topic-a] one-line summary
- [topic-b] one-line summary

Helper Script

Use scripts/new_session.py to create the session file with correct timestamp:

python3 skills/session-log/scripts/new_session.py --agent main --dir workspace/sessions