session-close

Name: session-close
Availability: InStock
Author: thiagoooo34252

Save project context at session checkpoints to prevent data loss.

1|Updated Apr 12, 2026

Search Tags:#session management #project continuity #context persistence #context recovery #context compaction

Ready to run

npx skills add https://github.com/thiagoooo34252/atlas-engineer --skill session-close-thiagoooo34252

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/thiagoooo34252/atlas-engineer/tree/main/skills/session-close
Command: npx skills add https://github.com/thiagoooo34252/atlas-engineer --skill session-close-thiagoooo34252

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mem_save, mem_session_summary, hot.md, wiki pages, memory index, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill ensures the persistent storage of project context during and after a session, preventing valuable information from being lost during context compaction.

Core Features & Use Cases

Context Checkpoints: Automate the saving of context during sessions to prevent data loss.
Full Session Closure: Systematic closure of a session with a comprehensive checklist.
Emergency Context Closure: Immediate actions during high-risk compaction scenarios.
High Context Detection: Automated detection of high context usage for proactive checkpointing.

Quick Start

To close the current session, use the command /session-close.

Frequently Asked Questions about session-close

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

FAQPage Schema

How do I prevent context loss during session compaction in collaborative engineering environments?▼

To prevent context loss during session compaction, you can automate session persistence to save context at key points. This ensures valuable project information is systematically stored and facilitates recovery from unexpected compaction scenarios.

What is the best way to automate context checkpoints for project continuity?▼

The best way to automate context checkpoints for project continuity is by triggering automated saves during high context usage detection. This proactively captures session state, preventing data loss before unexpected compaction occurs.

How do I perform a full session closure to ensure context recovery?▼

You can perform a full session closure by executing a systematic closure command followed by a comprehensive checklist. This process ensures all persistent context is saved and indexed for future recovery.

Do I need Obsidian integration to manage context persistence with this approach?▼

Yes, you need Obsidian integration and project-specific configuration files like memory indexes and wiki pages for optimal functionality. These dependencies are required to properly store and manage your persistent context.

Can I trigger an emergency context closure during high-risk compaction scenarios?▼

Yes, you can trigger an emergency context closure to take immediate actions during high-risk compaction scenarios. This feature rapidly saves your active session context to prevent critical data loss.