add-compact

Guide users to the native Codex `/compact` command for managing chat history.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mbaker95/nanodex --skill add-compact-mbaker95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-compact
Source: https://github.com/mbaker95/nanodex/tree/main/.agents/skills/add-compact
Command: npx skills add https://github.com/mbaker95/nanodex --skill add-compact-mbaker95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill clarifies how to manage conversation history within NanoDex, preventing users from implementing custom solutions when a native one exists.

Core Features & Use Cases

  • Native Command Guidance: Directs users to the existing /compact command within Codex.
  • Policy Customization Advice: Advises implementing custom compaction logic in code rather than creating redundant slash commands.
  • Use Case: A user asks how to make their chat history shorter. This skill explains that NanoDex already has a built-in way to do this using a specific command.

Quick Start

Explain how to compact conversations using the built-in Codex command.

Frequently Asked Questions about add-compact

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

FAQPage Schema
How do I compact conversation history in Codex?

To compact conversation history in Codex, use the built-in `/compact` command. This native feature automatically manages and shortens your active chat history without requiring any custom slash commands.

Does Codex have a built-in command for managing chat history length?

Yes, Codex features a built-in command for managing chat history length. You can utilize the native `/compact` command directly in your conversation to reduce context window size automatically.

Do I need to create a custom skill to compress chat history?

No, you do not need to create a custom skill to compress chat history. You should use the existing `/compact` command instead of building redundant slash commands for conversation management.

What is the best way to implement custom conversation compaction logic?

The best way to implement custom conversation compaction logic is through code-based policy implementation. rather than creating custom compaction skills, you should define your specific history management rules directly in your code.

Why should I avoid building custom compaction slash commands?

You should avoid building custom compaction slash commands because Codex already includes a native `/compact` command. Creating redundant skills for conversation management is unnecessary when built-in policy customization can handle it.