Session Watchdog
v1.0.0Monitors session context usage and saves checkpoints when approaching limits to prevent data loss before compaction or long tasks.
⭐ 2· 1.2k·8 current·8 all-time
byBill Watson@xbillwatsonx
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (monitor session context and save checkpoints) match the instructions: check session_status contextTokens and write checkpoint files under memory/YYYY-MM-DD.md. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
Instructions explicitly read/write memory/YYYY-MM-DD.md and call session_status to get contextTokens — these are appropriate for a checkpointing watchdog. However the doc is somewhat vague about the exact memory directory root and where 'Files modified and their paths' should be sourced from, which could lead an agent to attempt broader filesystem reads if not constrained. It also assumes a session_status command with a contextTokens field exists.
Install Mechanism
No install spec and no code files — lowest risk. Nothing will be downloaded or installed by this skill.
Credentials
No environment variables, credentials, or external service tokens are requested; the skill's data access is limited to its declared memory file usage.
Persistence & Privilege
Skill writes persistent checkpoint files to memory/YYYY-MM-DD.md which is coherent for a checkpointing tool. 'always' is false and autonomous invocation is allowed by default. Consider whether persistent memory writes are acceptable for your privacy/retention policies.
Assessment
This skill appears to do what it says: monitor context levels and save checkpoints to memory files. Before installing: (1) confirm what 'memory/' directory the agent will use and that the skill is restricted to that path (avoid giving it open filesystem read access); (2) ensure session_status exists and returns contextTokens as expected; (3) review what kinds of information will be saved (decisions, pending tasks, file paths) and avoid storing secrets or credentials in checkpoints; (4) consider access controls or encryption for the memory folder if checkpoint files could contain sensitive data; (5) if you want stricter behavior, ask for the skill to explicitly limit reads to its memory file and not enumerate or read arbitrary system files.Like a lobster shell, security has layers — review code before you run it.
latestvk97fjv7a6hy2k7q7851nn1b2en81je36
License
MIT-0
Free to use, modify, and redistribute. No attribution required.