nav-marker_skill

Overview

This skill creates context save points (markers) that preserve conversation state so you can pause work and resume later without re-explaining. It captures conversation summary, technical decisions, current focus, and a Theory-of-Mind section to restore mental context and reduce onboarding friction when resuming.

How this skill works

When invoked, the skill ensures a local marker directory exists, determines or prompts for a marker name and optional note, then synthesizes a structured markdown marker capturing the last part of the conversation. It actively extracts user intent, corrections, belief state, files touched, loaded documentation, next steps, and verification metadata, then writes and verifies the marker file and logs creation details.

When to use it

• When a user says: "save my progress", "create checkpoint", or "mark this point"
• Before taking a break (lunch, end of day) or stepping away
• Before a risky refactor or experimental change
• Before compacting or clearing conversation context
• When reaching a milestone and you want a clear restore point

Best practices

• Use descriptive names (e.g., before-api-refactor, lunch-break) to make restores intuitive
• Include a short note to capture context that may not be obvious later
• Avoid creating markers for very fresh contexts (< 5 messages)
• Capture ToM fields (Primary goal, preferences, corrections) — do not leave them blank
• Verify file creation and checksum to ensure marker integrity

Example use cases

• User: "Save my progress, taking lunch" → creates lunch-break marker to resume later
• User: "Mark this before I refactor routing" → snapshot state to roll back if needed
• End-of-day checkpoint: capture what’s done, blockers, and next steps for tomorrow
• Automatic marker before context compaction so knowledge is preserved across clears
• Create a marker before trying an experimental approach to protect a known-good state