---
name: Voice Notes
slug: voice-notes
version: 1.0.0
description: Transform chaotic voice memos into a searchable knowledge base with automatic organization, linking, and tag-based retrieval.
metadata: {"clawdbot":{"emoji":"🎙️","requires":{"bins":[]},"os":["linux","darwin","win32"]}}
---

## When to Use

User sends voice notes on any topic. Agent transcribes, organizes into structured notes, links related content, and maintains a scalable tag-based system.

## Architecture

Memory lives in `~/voice-notes/`. See `memory-template.md` for setup.

```
~/voice-notes/
├── memory.md           # HOT: tag registry + recent activity
├── index.md            # Note index with tags and links
├── transcripts/        # Raw transcriptions (never deleted)
├── notes/              # Processed notes
└── archive/            # Superseded content (never deleted)
```

## Quick Reference

| Topic | File |
|-------|------|
| Memory setup | `memory-template.md` |
| Note processing | `processing.md` |
| Linking system | `linking.md` |
| Tag management | `tags.md` |

## Data Storage

All data stored in `~/voice-notes/`. Create on first use:
```bash
mkdir -p ~/voice-notes/{transcripts,notes,archive}
```

## Scope

This skill ONLY:
- Transcribes audio using configured STT
- Stores transcripts and notes in `~/voice-notes/`
- Links related notes based on content
- Manages user-defined tags

This skill NEVER:
- Deletes content without explicit user confirmation
- Accesses files outside `~/voice-notes/`
- Sends data externally
- Infers organization preferences from silence

## Self-Modification

This skill NEVER modifies its own SKILL.md.
All data stored in `~/voice-notes/` files.

## Core Rules

### 1. Never Lose Information
| Event | Action |
|-------|--------|
| New audio | Save transcript immediately to `transcripts/` |
| Edit note | Preserve original in transcript reference |
| Strategy change | Archive old version, link to new |
| User deletes | Confirm first, then move to `archive/` |

### 2. Tag System Over Folders
- Tags defined in `~/voice-notes/memory.md` under `## Tag Registry`
- User defines granularity (broad vs specific)
- Reuse existing tags before creating new
- Each note can have multiple tags

### 3. Detect Related Content
Before creating new note:
1. Search existing notes for topic overlap
2. If related → append or link (not duplicate)
3. If continuation → extend existing note
4. If contradicts → link as evolution, preserve both

### 4. Document Scaling
When note exceeds ~100 lines:
1. Identify natural sections
2. Split into linked child notes
3. Parent becomes overview with links
4. Like Notion: notes contain notes

### 5. Progressive Disclosure
| Tier | When Loaded |
|------|-------------|
| `~/voice-notes/memory.md` | Always (tags, recent) |
| `~/voice-notes/index.md` | When searching |
| Individual notes | On demand |
| Transcripts | For verification only |

### 6. Reorganize Chaotic Input
User may speak stream-of-consciousness:
- Extract clear meaning
- Structure logically
- Preserve nuance (not over-condense)
- Group related points

### 7. First Session Setup
Ask user on first use:
- "Broad categories or detailed tags?"
- "Any existing topics to seed?"

## Common Traps

- Creating new note when should append → always search first
- Losing tag consistency → check registry before creating tags
- Over-condensing → preserve user's intent and nuance
- Deleting "outdated" content → archive, never delete