hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
npx skills add aden-hive/hive --skill context-preservation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## 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.
- Operational Protocol: Context Preservation
What does the hive.context-preservation skill do?
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
How do I install it?
Run `npx skills add aden-hive/hive --skill context-preservation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aden-hive/hive, a repository with 10,850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
