context-graph-compressor

Compress conversations into a portable JSON context graph for handoff.

34|9|Updated May 30, 2026
One-click install
npx skills add https://github.com/Adityapal67/context-graph-compressor --skill context-graph-compressor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-graph-compressor
Source: https://github.com/Adityapal67/context-graph-compressor/tree/main
Command: npx skills add https://github.com/Adityapal67/context-graph-compressor --skill context-graph-compressor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compress conversations into a portable JSON context graph to preserve critical decisions and context when handing off to a new chat or different LLM.

Core Features & Use Cases

  • Converts chat history into a compact, machine-readable graph with node types and relationships.
  • Supports both compact handoff (token-efficient) and readable mode for archiving.
  • Enables cross-session continuity across LLMs and platforms.

Quick Start

Instruct the assistant to "compress this chat" to generate a context graph.

Frequently Asked Questions about context-graph-compressor

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

FAQPage Schema
How do I compress chat history into a JSON context graph for cross-session handoff?

To compress chat history into a JSON context graph, instruct the assistant to "compress this chat," which converts conversations into a portable graph preserving decisions and context for cross-session continuity across different LLMs.

What is a context graph and how does it preserve conversation state for different LLMs?

A context graph is a portable JSON structure that maps conversations using typed nodes (F, D, P, G, C, A, X), importance levels, and relationships to preserve decision history and context when handing off to a new chat or different LLM.

Can I save tokens when transferring chat context to a new session?

You can save tokens during chat context transfer by using the compact handoff mode, which encodes conversations into a token-efficient JSON context graph while retaining critical decision history for the new session.

Does the context graph handoff work across different AI platforms and chat sessions?

Yes, the context graph handoff supports cross-session continuity across different LLMs and platforms by outputting a downloadable, portable JSON file that any compatible AI system can ingest.

What's the best way to archive AI chat history in a human-readable format?

The best way to archive AI chat history is using the readable mode of the context graph compressor, which structures conversation decisions and context into a human-readable JSON format suitable for long-term archiving.

What schema structure does a compressed JSON context graph use to map relationships?

The compressed JSON context graph enforces a strict schema utilizing specific node types (F, D, P, G, C, A, X), importance levels, statuses, and relationships to accurately map the conversation history.