---
name: Hive Note-Taking
slug: hive-note-taking
category: AI Engineering
description: "Hive Note-Taking maintains a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need. Use it to record working data and reasoning between agent tool calls."
github: "https://github.com/aden-hive/hive/tree/main/core/framework/skills/_default_skills/note-taking"
language: Python
stars: 10907
forks: 5668
install: "npx degit https://github.com/aden-hive/hive/tree/main/core/framework/skills/_default_skills/note-taking ~/.claude/skills/note-taking"
installs_to: ~/.claude/skills/note-taking
source_path: core/framework/skills/_default_skills/note-taking/SKILL.md
collection_size: 24
category_size: 2451
collection_url: "https://dirskills.com/collections/aden-hive/hive"
added: 2026-08-15T06:50:12.585Z
last_synced: 2026-08-15T06:50:12.585Z
canonical_url: "https://dirskills.com/skills/hive-note-taking"
---

# Hive Note-Taking

Hive Note-Taking maintains a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need. Use it to record working data and reasoning between agent tool calls.

**Install:**

```bash
npx degit https://github.com/aden-hive/hive/tree/main/core/framework/skills/_default_skills/note-taking ~/.claude/skills/note-taking
```

## README

## Operational Protocol: Structured Note-Taking

Maintain free-form working notes in shared buffer key `_working_notes` for data that *you* need to remember but that isn't captured by the colony task queue.

**Do not duplicate the queue in here.** Per-task goal, ordered steps, and SOP gates live in `progress.db` — use `hive.colony-progress-tracker` for those. These notes are for things the DB schema doesn't cover.

Update at these checkpoints:

- After receiving new information that changes how you plan to approach the current step
- Before any tool call that will produce substantial output you'll need to reference later
- When you make a non-obvious decision whose *why* would be lost if the tool call history gets pruned

Structure:

### Key Decisions — decisions made and WHY
### Working Data — intermediate results, extracted values (URLs, IDs, key snippets — not full pages)
### Open Questions — uncertainties you plan to verify
### Blockers — anything preventing progress that isn't already captured in `tasks.last_error`

Update incrementally — do not rewrite from scratch each time.