rai-session-close

Generate a structured YAML state file for the CLI.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-session-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-session-close
Source: https://github.com/fcastrillo/carbtrack-ai/tree/main/.claude/skills/rai-session-close
Command: npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-session-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close and summarize a session by producing a durable, structured state for the CLI, reducing manual handoffs and ensuring atomic writes.

Core Features & Use Cases

  • Reflect on session outcomes and generate a YAML state file for the CLI
  • Output includes summary, current work, pending decisions, and next actions to maintain continuity
  • Works with the CLI to atomically record session data across memory, patterns, and coaching

Quick Start

Close the active session by generating a YAML state and handing it to the CLI for atomic write.

Frequently Asked Questions about rai-session-close

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

FAQPage Schema
How do I generate a YAML state file when closing a CLI session?

To generate a YAML state file when closing a CLI session, you reflect on session outcomes to produce a structured YAML state file. This file summarizes current work, pending decisions, and next actions for the CLI to atomically record.

What is the best way to automate session handoffs for feature and research tasks?

Automating session handoffs for feature and research tasks requires generating a structured YAML state with concise coaching notes. This deterministic format is consumed by the CLI to ensure continuous memory and atomic writes across task lifecycles.

How does structured reflection at the end of a development session improve continuity?

Structured reflection at the end of a development session improves continuity by capturing outcomes, pending decisions, and next actions in a YAML state file. This explicit format is consumed by the CLI to maintain memory and coaching patterns.

Can I use a YAML state file to record maintenance and infrastructure session data atomically?

Yes, you can use a YAML state file to record maintenance and infrastructure session data atomically. The generated YAML state is handed to the CLI, which atomically writes session data across memory, patterns, and coaching notes.

Do I need any specific dependencies to perform a CLI session close with YAML output?

No specific dependencies are required to perform a CLI session close with YAML output. The process operates independently by reflecting on session outcomes and delivering an explicit YAML state directly to the CLI for atomic writes.

Why does my CLI session handoff lose context between ideation tasks?

Your CLI session handoff loses context between ideation tasks because it lacks a structured YAML state. Generating a durable YAML file with summaries and next actions ensures the CLI atomically records session data for future continuity.