Session Logger

VerifiedSafe

Logs all session activity (actions, commands, decisions, errors, notes) to a timestamped file. Automatically creates a log at session start and appends throughout, with structured entries. Helpful for maintaining a detailed record of the session for later review or debugging.

Sby Skills Guide Bot
ProductivityBeginner
6/2/2026
Claude Code
#session-logging#activity-log#timestamped#auto-trigger

Recommended for

Automated summary

Automatically logs all session activity to a timestamped file.

Strengths

  • Automatically starts logging at session start
  • Structured format with event types (ACTION, COMMAND, DECISION, ERROR, NOTE)
  • ISO 8601 timestamps
  • Session end summary with accomplishments, decisions, unresolved items, and next steps

Limitations

  • Requires manual command to end session
  • Log files can grow large
  • Only works within Claude Code environment
When to use it

When you want a detailed, structured record of all actions and decisions made during a session.

When not to use it

If the session is very short or you have privacy concerns about logging commands.

Security analysis

Safe
Quality score90/100

The skill only appends to a local log file under the user's home directory. It does not execute shell commands, transmit data, or perform any destructive or exfiltrating actions.

No concerns found

How this analysis is made

Examples

Start logging session
Start logging
Log current session explicitly
log this session
Wrap up session
wrap up

name: session-logger description: Log all session activity to a timestamped log file. Use automatically at the start of every session, and when the user says "log this session", "start logging", or "session log".

Session Logger

Instructions

  1. At session start, create a log file at ~/.openclaw/workspace-main/logs/${SESSION_ID}.log
  2. Write a SESSION START block: timestamp, working directory, user's initial goal
  3. Throughout the session append events:
    • [ACTION] — What you're doing
    • [COMMAND] — Shell commands executed
    • [DECISION] — Key choices made
    • [ERROR] — Issues encountered
    • [NOTE] — Important context
  4. At session end (user says "done", "wrap up", "end session"), write SESSION END block: accomplished, decisions, unresolved, next steps

Log Format

================================================================================
SESSION START: ${SESSION_ID}
Timestamp: ${ISO8601}
Working Directory: ${PWD}
Initial Goal: ${USER_GOAL}
================================================================================

[ACTION] Started task analysis
[COMMAND] ls -la ~/.openclaw/
[DECISION] Using deterministic script approach
[NOTE] User prefers concise updates
...

================================================================================
SESSION END: ${SESSION_ID}
Timestamp: ${ISO8601}
Duration: ${MINUTES}m
Accomplished:
- Item 1
- Item 2

Key Decisions:
- Decision 1

Unresolved:
- Item to follow up

Next Steps:
- What to do next
================================================================================

Auto-Trigger

This skill loads automatically at session start. Call log_session_start() implicitly.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/session-logger-mma3jsuy/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/session-logger-mma3jsuy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/session-logger-mma3jsuy/download' --output '.skill-downloads/session-logger-mma3jsuy/SKILL.md.part' && mv '.skill-downloads/session-logger-mma3jsuy/SKILL.md.part' '.skill-downloads/session-logger-mma3jsuy/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/session-logger-mma3jsuy/SKILL.md' && test -s '.skill-downloads/session-logger-mma3jsuy/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/session-logger' && cp -R '.skill-downloads/session-logger-mma3jsuy' '.claude/skills/session-logger'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/session-logger-mma3jsuy'

openskills read 'session-logger-mma3jsuy'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/session-logger-mma3jsuy/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills