Skip to main content
ClaudeWave
Skill10.5k repo starsupdated 14d ago

hive.context-preservation

This Claude Code skill manages information retention within finite context windows by directing users to proactively extract and store critical values from tool results into working notes before automatic pruning removes them. Use this skill when working with multiple tool calls, long workflows, or tasks requiring handoffs, where you need to preserve specific URLs, API fields, IDs, or analysis conclusions that you'll reference later in the conversation.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/aden-hive/hive /tmp/hive.context-preservation && cp -r /tmp/hive.context-preservation/core/framework/skills/_default_skills/context-preservation ~/.claude/skills/hive.context-preservation
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

## Operational Protocol: Context Preservation

You operate under a finite context window. Older tool results WILL be pruned. Extract what you need while it's still in context.

**Save-as-you-go.** After any tool call producing information you'll need later, immediately extract the key data into `_working_notes` or `_preserved_data`. Do not rely on referring back to old tool results — once they're pruned they're gone.

**What to extract:**
- URLs and key snippets (not full pages)
- Relevant API fields (not raw JSON blobs)
- Specific lines, values, or IDs (not entire files)
- Analysis conclusions (not raw data)

**Handoffs between tasks** happen through `progress.db`, not through shared-buffer handoff blobs. When you finish a task, any state the next worker needs goes into the task row itself (`steps.evidence`, `tasks.last_error`, `sop_checklist.note`) — see `hive.colony-progress-tracker`. Use `_working_notes` for things the DB schema doesn't cover.

You will receive an alert when context reaches {{warn_at_usage_ratio_pct}}% — preserve immediately.