Session State Tracker

• Verdict: Pass
• Confidence: High
• Analyzed: Feb 18, 2026, 5:04 PM
• Findings: 0
• Version: 2.0.0

Overview

The skill is internally consistent with its description: it only reads/writes a single workspace file (SESSION_STATE.md), uses OpenClaw lifecycle hooks and the memory_search tool as documented, and does not request credentials or call external endpoints.

This skill appears to do what it claims, but review before enabling: - Verify you trust the author/repository before enabling hooks that run automatically; hooks will inject system messages and may write to SESSION_STATE.md without interactive confirmation. - The code only accesses SESSION_STATE.md and optionally memory_search (indexed session transcripts). If you use discovery, ensure session indexing is configured and acceptable for your privacy needs. - The module respects OPENCLAW_WORKSPACE (or cwd). Confirm the workspace path is the directory you expect to avoid accidental writes elsewhere. - Back up any existing SESSION_STATE.md before enabling the skill — writes are atomic but strict schema validation can cause writes to fail or discovery may overwrite fields when validating is disabled. - If you want to limit automatic behavior, enable the skill but disable specific hooks in your openclaw.json or test it in an isolated workspace first. - If you need higher assurance, inspect the included scripts (scripts/state.js, hooks/*.js) yourself — they are the only code that runs and are the right place to audit for any unwanted behavior.