end

End MARVIN sessions by preserving context, saving logs, and updating state.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Wattysaid/MARVIN --skill end-wattysaid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end
Source: https://github.com/Wattysaid/MARVIN/tree/main/skills/end
Command: npx skills add https://github.com/Wattysaid/MARVIN --skill end-wattysaid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End MARVIN session with full context preservation, including session logs, state updates, and optional content capture for future continuity.

Core Features & Use Cases

  • Graceful session termination that preserves context.
  • Automatic generation and update of content and session logs.
  • State update and open-thread maintenance for follow-ups.

Quick Start

Use the end skill to terminate the current session by typing /end or /quit, which saves the conversation, updates state, and creates session logs.

Frequently Asked Questions about end

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

FAQPage Schema
How do I preserve session context and state when ending a MARVIN workflow?

To preserve session context, the end skill saves conversation logs, updates the current state file, and maintains open threads for follow-ups when you type /end or /quit.

What is the best way to automatically log session content for future continuity?

Automatically logging session content is handled by updating content/log.md and sessions/{TODAY}.md, which captures a full summary of the current session for future continuity.

Can I automatically create a git commit when I close a session?

Yes, you can create a git commit when closing a session, as the end skill performs optional git commits alongside state updates and content logging to preserve your workflow changes.

What files do I need to configure before terminating a session with context preservation?

You need access to state/current.md, content/log.md, and sessions/{TODAY}.md, as these files are required to summarize the session, update logs, and modify state during termination.

Does the session termination process update the current state for follow-up tasks?

Yes, the session termination process updates the current state and maintains open threads, ensuring that your workflow state is accurately modified for any necessary follow-up tasks.

Why should I use a dedicated skill to end a session instead of manually saving files?

Using a dedicated skill ensures full context preservation by automatically generating session summaries, updating logs consistently, and handling optional git commits, avoiding manual file errors.