Nm Conserve Clear Context

Automatic context management with graceful handoff to a continuation subagent at 80% usage

This skill is coherent with its stated goal, but review before use: 1) The SKILL.md references environment variables (CONSERVE_* and CLAUDE_*) although the registry lists none — set and audit those intentionally. 2) The skill writes .claude/session-state.md (or a custom path); ensure your workflows do not cause secrets or credentials to be written to that file or a world-readable location. 3) Beware of 'dangerous' / 'unattended' modes: if CLAUDE_DANGEROUS_MODE or CLAUDE_UNATTENDED is set, continuation agents may proceed without user confirmation — test on non-sensitive projects and prefer interactive mode. 4) Confirm how your platform's Task/TaskUpdate/TaskCreate tools work and what permissions continuation agents receive. 5) If you accept the skill, consider restricting the session state path to a safe location (e.g., project-local, not /tmp or home) and audit generated files after handoffs. If you want greater assurance, ask the maintainer to update registry metadata to declare the env vars the skill actually reads and to add explicit guidance to avoid persisting secrets.

Type: OpenClaw Skill Name: nm-conserve-clear-context Version: 1.0.0 The skill implements a context-management mechanism that saves session state to `.claude/session-state.md` and delegates tasks to subagents. It contains explicit instructions in `SKILL.md` and `modules/session-state.md` directing the agent to bypass user confirmation ("DO NOT pause for user confirmation") and propagate "dangerous" or "unattended" execution modes across agent boundaries. While these features are aligned with the stated goal of maintaining workflow continuity, the programmatic suppression of human-in-the-loop controls and the use of environment variables like `CLAUDE_DANGEROUS_MODE` to trigger automated execution constitute high-risk behavior.