- name
- Voice Notes
- slug
- voice-notes
- version
- 1.0.2
- description
- Organize voice message transcripts into a structured, searchable knowledge base with tags, links, and progressive note-taking.
- metadata
- {"clawdbot":{"requires":{"bins":[]},"os":["linux","darwin","win32"]}}
When to Use
User sends voice messages. The agent platform handles transcription (via its configured STT). This skill organizes the resulting transcripts into structured notes, links related content, and maintains a scalable tag-based system.
Important: Transcription is Platform-Handled
This skill does NOT perform transcription. It expects the agent platform to:
- Receive audio from the user
- Transcribe it using the platform's configured STT (local or cloud)
- Pass the transcript text to this skill for organization
The skill only organizes and stores text transcripts locally in ~/voice-notes/. Audio files are never accessed or stored by this skill.
Architecture
All data stored 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 (text only)
+-- notes/ # Processed notes
+-- archive/ # Superseded contentQuick 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:
mkdir -p ~/voice-notes/{transcripts,notes,archive}Scope
This skill ONLY:
- Receives transcript text from the agent platform
- Stores transcripts and notes in
~/voice-notes/ - Links related notes based on content
- Manages user-defined tags
This skill NEVER:
- Performs audio transcription (platform responsibility)
- Accesses audio files
- Deletes content without explicit user confirmation
- Accesses files outside
~/voice-notes/ - Sends data externally
- Requires API keys or credentials
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 transcript | Save 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.mdunder## 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:
- Search existing notes for topic overlap
- If related -> append or link (not duplicate)
- If continuation -> extend existing note
- If contradicts -> link as evolution, preserve both
4. Document Scaling
When note exceeds ~100 lines:
- Identify natural sections
- Split into linked child notes
- Parent becomes overview with links
- 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