session-watchdog

Monitor session context token levels and save checkpoints before compaction.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/velamints2/clawbot-lab --skill session-watchdog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-watchdog
Source: https://github.com/velamints2/clawbot-lab/tree/main/skills/session-watchdog
Command: npx skills add https://github.com/velamints2/clawbot-lab --skill session-watchdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain continuity in long conversations by tracking context token usage and proactively saving checkpoints before memory compaction.

Core Features & Use Cases

  • Context monitoring and thresholds: tracks tokens and triggers at specified levels.
  • Checkpoint saving: writes a memory file containing decisions, pending tasks, and important context details to survive compaction.
  • User alerts and decision prompts: informs the user when approaching limits and offers options to continue, summarize, or pause.
  • Real-world use case: in extended design discussions, preserves decisions and tasks across context resets.

Quick Start

Start a new session with the watchdog enabled to automatically monitor context and save checkpoints as your conversation grows.

Frequently Asked Questions about session-watchdog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save context and prevent data loss during session compaction?

To prevent data loss during session compaction, you can use an automated checkpoint protocol that monitors token usage and proactively saves memory files containing decisions and pending tasks before the context limit is reached.

When should I create checkpoints to maintain memory in long conversations?

You should create checkpoints during session starts, after every 30k tokens of conversation, before large tasks, and when users inquire about remaining context to maintain memory in long conversations.

What is the best way to monitor context token usage in extended design discussions?

The best way to monitor context token usage in extended design discussions is by applying a memory-based checkpoint protocol that tracks token levels and triggers user-facing alerts with threshold-based actions when approaching limits.

Does the checkpoint protocol work automatically, or do I need to manually trigger it?

The checkpoint protocol works automatically by tracking tokens and triggering at specified levels, though it also responds to user inquiries about remaining context by offering options to continue, summarize, or pause.

What information is preserved in a memory file when context is compacted?

When context is compacted, the memory file format preserves decisions, pending tasks, and important context details to ensure continuity and survive the context reset.

Can I use session context monitoring for conversations that exceed standard token limits?

Yes, you can use session context monitoring for conversations that exceed standard token limits, as it tracks token usage and alerts you when approaching limits to offer options to continue, summarize, or pause.