Night Market Skill — ported from claude-night-market/conserve. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents

• Quick Start
• When to Use
• Core Hub Responsibilities
• Module Selection Strategy
• Context Classification
• Integration Points
• Resources

Context Optimization Hub

Quick Start

Basic Usage

# Analyze current context usage
python -m conserve.context_analyzer

When To Use

• Threshold Alert: When context usage approaches 50% of the window.
• Complex Tasks: For operations requiring multi-file analysis or long tool chains.

When NOT To Use

• Simple single-step tasks with low context usage
• Already using mcp-code-execution for tool chains

Core Hub Responsibilities

1. Assess context pressure and MECW compliance.
2. Route to appropriate specialized modules.
3. Coordinate subagent-based workflows.
4. Manage token budget allocation across modules.
5. Synthesize results from modular execution.

Module Selection Strategy

def select_optimal_modules(context_situation, task_complexity):
    if context_situation == "CRITICAL":
        return ['mecw-assessment', 'subagent-coordination']
    elif task_complexity == 'high':
        return ['mecw-principles', 'subagent-coordination']
    else:
        return ['mecw-assessment']

Context Classification

Large Output Handling (Claude Code 2.1.2+)

Behavior Change: Large bash command and tool outputs are saved to disk instead of being truncated; file references are provided for access.

Impact on Context Optimization

Best Practices

• Avoid pre-emptive reads: Large outputs are referenced, not automatically loaded into context.
• Read selectively: Use head, tail, or grep on file references.
• Leverage full data: Quality gates can access complete test results via files.
• Monitor growth: File references are small, but reading the full files adds to context.

Integration Points