smolkik_adm/My-Brain-Is-Full-Crew
1
0
Fork 0
mirror of https://github.com/gnekt/My-Brain-Is-Full-Crew.git synced 2026-09-20 07:46:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

REVAMPED

Browse Source
This commit is contained in:
gnekt
2026-03-22 17:17:30 +01:00
commit 299df8b1c9
48 changed files with 12762 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/agents/architect.md
+109
View File
@@ -0,0 +1,109 @@
# Architect
> Your vault's foundation, blueprint, and building code, all in one agent.
## What it does
The Architect is the first agent you meet and the one that shapes everything else. When you start fresh, the Architect runs you through a friendly onboarding conversation. Not a boring form, but a real back-and-forth where it learns who you are, what you do, and what you need from your vault. Based on your answers, it builds a personalized folder structure, creates templates, sets up naming conventions, and establishes a tag system that every other agent follows.
Beyond onboarding, the Architect is your vault's structural authority. Whenever a new project needs a home, a new area of your life emerges, or your existing structure starts feeling cramped, the Architect steps in. It creates folders, designs templates, updates the rules, and makes sure every agent in the crew knows about the changes.
Think of it as the urban planner of your knowledge city. It decides where things go, how streets are named, and what the building codes are, so everyone else can do their job without chaos.
## Capabilities
- **Full vault onboarding**: a guided, conversational setup that creates your entire vault from scratch based on your answers
- **User profile creation**: saves your preferences, language, goals, and context so every agent can serve you better
- **Folder management**: creates, restructures, and archives folders as your life evolves
- **Template management**: builds and maintains Templater-compatible templates for meetings, ideas, tasks, projects, people, daily notes, and more
- **Tag taxonomy**: maintains the official tag list, enforces naming rules, and prevents tag sprawl
- **Naming conventions**: defines and documents how files, folders, and tags are named
- **MOC (Map of Content) creation**: creates index notes that tie related topics together
- **Vault evolution**: detects when your structure needs to grow, split, or simplify, and proposes changes
- **Profile updates**: updates your preferences anytime (new job, new language, activating a new agent)
- **Plugin recommendations**: suggests essential and optional Obsidian plugins with clear reasons for each
- **Multilingual support**: responds in whatever language you write in
## How to use it
Start a conversation with any of these phrases (in any language):
- "Initialize my vault" / "Set up the vault" / "Onboarding"
- "Create a new project folder for [name]"
- "I need a new area for [topic]"
- "Add a template for [type]"
- "Update the tag taxonomy"
- "Restructure my vault"
- "I changed jobs, update my profile"
- "Create a MOC for [topic]"
In Italian: "Inizializza il vault", "Nuovo progetto", "Configura il vault"
In French: "Initialiser le vault", "Nouveau projet"
In Spanish: "Inicializar el vault", "Nuevo proyecto"
In German: "Vault initialisieren", "Neues Projekt"
## Example conversations
### First-time setup
**You:** Initialize my vault
**Architect:** Welcome! I am the Architect. I will help you build your personal knowledge vault from the ground up. Before I create any folders or files, I want to understand who you are and how you work. This will take about 5 minutes, and everything you tell me will be saved so every agent in the crew can serve you better.
Let's start with the basics. What should I call you?
**You:** Call me Alex
**Architect:** Nice to meet you, Alex. You are writing in English, so I will keep all our interactions in English. Do you speak any other languages you might use in your vault? Notes, meetings, or sources in other languages?
**You:** I sometimes take notes in Italian
**Architect:** Got it, English primary, Italian secondary. Now, what do you do? Are you a student, researcher, professional, creative...?
*(The conversation continues through 5 phases, covering your role, motivation, which agents you want, health preferences if applicable, and integrations. At the end, the Architect creates your full vault structure.)*
---
### Adding a new project
**You:** Create a new project folder for Project Alpha
**Architect:** I will create a folder for Project Alpha at `01-Projects/Alpha/`. Here is what I will set up:
- `01-Projects/Alpha/` (main project folder)
- A project index note using the Project template
- An entry in the Projects MOC
I will also update `Meta/vault-structure.md` and notify the Sorter that a new filing destination exists.
Shall I proceed?
---
### Evolving the vault
**You:** Update the tag taxonomy. I keep seeing tags that don't make sense
**Architect:** Let me audit the current tag taxonomy. I found 3 issues:
1. Both `#ml` and `#machine-learning` are in use. I recommend keeping `#machine-learning` and replacing all instances of `#ml`
2. `#misc` is used on 12 notes, which is too vague. I suggest reviewing those notes and assigning more specific tags
3. `#meeting-notes` exists alongside `#meeting`. I recommend consolidating to `#meeting`
Want me to apply these changes?
## Works with
- **Every agent** reads the rules the Architect creates (naming conventions, tag taxonomy, vault structure)
- **Scribe** uses the templates the Architect maintains
- **Sorter** follows the folder structure for filing decisions
- **Librarian** references all Meta files when auditing vault health
- **Connector** uses the MOC structure for link suggestions
- **Postman** checks your profile for integration settings (Gmail, Calendar)
## Tips
- **Run onboarding first.** The Architect is designed to be the very first thing you use. Other agents depend on the structure and profile it creates.
- **Ask for restructuring when things feel messy.** If you notice notes piling up in the wrong places or tags multiplying, ask the Architect to audit and evolve the structure.
- **Update your profile when your life changes.** New job? New language? New goal? Tell the Architect so every agent stays in sync.
- **Start small.** You do not need all 10 agents on day one. Start with the core (Architect, Scribe, Sorter, Seeker) and add more as your vault grows.
docs/agents/connector.md
+122
View File
@@ -0,0 +1,122 @@
# Connector
> The agent that turns isolated notes into a living knowledge web.
## What it does
The Connector is obsessed with relationships between your notes. It reads your vault, analyzes the link structure, and finds connections you did not know existed. That meeting note from January? It relates to the idea you jotted down last week. That book quote? It supports the argument in your project brief. The Connector sees these threads and weaves them together.
Your vault's value grows exponentially with the quality of its connections. A note with zero links is an island, useful on its own but invisible to everything around it. The Connector ensures no note stays isolated for long. It discovers missing links, suggests new connections ranked by confidence, identifies clusters of related notes that need a Map of Content, and can even surprise you with unexpected relationships between seemingly unrelated topics.
It is also your graph health monitor. It tracks metrics like orphan rate, link density, and cluster count, and tells you when parts of your vault are drifting into isolation.
## Capabilities
- **Full graph audit**: maps all wikilinks, identifies orphan notes (no incoming links), dead-end notes (no outgoing links), and disconnected clusters
- **Targeted connection discovery**: given a specific note, finds all potentially related notes ranked by strength (strong, medium, weak)
- **Serendipity mode**: discovers unexpected connections between notes that share no obvious keywords but relate conceptually
- **Semantic bridging**: finds notes about the same concept using different terminology
- **Bridge notes**: creates new notes that explicitly connect two otherwise separate clusters
- **MOC enhancement**: audits Maps of Content for completeness and suggests missing entries
- **Constellation view**: shows how a topic connects across different areas of your vault (work, personal, learning)
- **People network**: maps how people in your vault are connected through meetings, projects, and references
- **Graph health metrics**: tracks connectivity ratio, orphan rate, average path length, cluster count, and MOC coverage
- **Batch processing**: after the Sorter files a batch of notes, analyzes all of them for connections at once
## How to use it
Trigger the Connector when you want to strengthen your vault's knowledge graph:
- "Find connections for my latest note"
- "Analyze my vault graph"
- "What notes are isolated?"
- "What connects [topic A] and [topic B]?"
- "Find missing links"
- "Surprise me, what unexpected connections exist?"
- "Audit the MOCs"
- "How is my graph health?"
- "Show me the people network"
In Italian: "Trova connessioni", "Analizza le relazioni", "Collega le note"
In French: "Trouve des connexions", "Analyse du graphe"
In Spanish: "Encuentra conexiones", "Analiza el grafo"
In German: "Finde Verbindungen", "Netzwerkanalyse"
## Example conversations
### Connection discovery for a specific note
**You:** Find connections for my latest note on tiered pricing
**Connector:** I analyzed "Tiered Pricing Model" and found these potential connections:
**Strong (add these):**
- [[Client Feedback on Pricing]] contains the client's response to the tiered model idea
- [[Sprint Planning Q2]] is the meeting where Marco first proposed the tiers
**Medium (probably useful):**
- [[Competitor Analysis Q1]] includes competitor pricing models for comparison
- [[Revenue Projections 2026]] would be impacted by a pricing change
**Weak (worth considering):**
- [[Reading Notes, SaaS Pricing Strategies]] has book notes with relevant frameworks
Want me to add the strong connections now?
---
### Graph health check
**You:** How is my graph health?
**Connector:** Vault Graph Analysis
Stats:
- Total notes: 147
- Total links: 312
- Average density: 2.1 links per note
- Orphan notes: 18 (12%), target is under 10%
- Dead-end notes: 9
Islands (disconnected clusters):
1. "Personal Finance": 5 interconnected notes, 0 external links
2. "Old Project Beta": 8 notes, only 1 link to the rest of the vault
Top 5 most connected notes:
1. [[MOC/Index]], 23 links out
2. [[Sprint Planning Q2]], 8 links in, 6 links out
3. [[Project Alpha Roadmap]], 5 links in, 9 links out
Recommendations:
- The Personal Finance cluster should be linked to your Areas and daily notes
- 18 orphan notes need attention. Want me to suggest connections for each?
---
### Serendipity mode
**You:** Surprise me, what unexpected connections exist?
**Connector:** Here are some connections you probably did not expect:
1. Your reading notes on "Atomic Habits" and your project retrospective for Beta share the same core insight about feedback loops, one in personal habits, one in software development. Linking them could create a powerful cross-domain concept note.
2. Three different people in your vault (Marco, Sarah, and the podcast guest from last week) all independently mentioned the same concern about "sustainable growth." This might be an emerging theme worth a dedicated note.
Want me to create any of these connections?
## Works with
- **Sorter**: after a batch filing, the Connector receives a notification to analyze newly filed notes
- **Architect**: when the Connector discovers a cluster needing a new MOC, it flags the Architect to create one
- **Seeker**: the Connector can ask the Seeker to verify content-level relationships before suggesting links
- **Librarian**: broken wikilinks found during analysis are reported to the Librarian
## Tips
- **Run it after big filing sessions.** The best time to use the Connector is right after the Sorter processes a batch of notes. The new notes have the most linking potential.
- **Start with "strong" connections.** When the Connector suggests links at three confidence levels, always approve the strong ones. They are almost always correct.
- **Use serendipity mode for creative work.** The unexpected connections it finds can spark genuinely new ideas by linking concepts from different domains.
- **Watch the orphan rate.** If it climbs above 15-20%, your vault is accumulating unlinked knowledge that is effectively invisible. Run a graph audit.
- **Do not over-link.** The Connector follows a quality-over-quantity principle. A few meaningful links are worth more than dozens of superficial ones. Trust its judgment.
- **Check the people network.** It is a surprisingly useful way to see who appears most often in your vault and how they are connected to your projects.
docs/agents/librarian.md
+132
View File
@@ -0,0 +1,132 @@
# Librarian
> The quality inspector that keeps your vault healthy, consistent, and trustworthy.
## What it does
The Librarian is your vault's maintenance crew. While other agents create and organize notes, the Librarian checks that everything stays clean, consistent, and structurally sound over time. Think of it as a weekly health checkup for your entire knowledge base.
Run it once a week (or whenever things feel off), and it performs a thorough 6-phase audit: scanning folder structure, hunting duplicates, verifying every wikilink, auditing frontmatter consistency, reviewing Maps of Content, and generating a detailed health report. It finds the problems you would never notice on your own. That broken link from two months ago, the two nearly identical notes in different folders, the 15 notes still tagged `status: inbox` even though they were filed weeks ago.
The Librarian is conservative by design. It never deletes anything, only archives. It never auto-merges duplicates. Instead, it shows you both versions and asks. Every change is logged and transparent.
## Capabilities
- **6-phase full audit**: structural scan, duplicate detection, link integrity, frontmatter audit, MOC review, and health report generation
- **Quick health check**: a lighter version focusing on the most common issues (broken links, inbox stragglers, recent duplicates)
- **Deep clean**: aggressive audit that catches everything, including near-duplicate content with 70%+ overlap
- **Duplicate detection**: finds exact filename matches, "(copy)" variants, sync conflicts, and content-similar notes
- **Broken link repair**: identifies wikilinks pointing to non-existent notes and fixes or flags them
- **Orphan note rescue**: finds notes with zero incoming links and suggests where they should be connected
- **Frontmatter consistency**: checks that every note has required fields (type, date, tags, status) and fixes format issues automatically
- **Tag audit**: validates all tags against the official taxonomy and flags unknown or duplicate-meaning tags
- **Consistency report**: shows exactly what is wrong and what was fixed, with counts and percentages
- **Growth analytics**: tracks your vault's growth over time (notes per week, links per note, health score trends)
- **Stale content detector**: identifies notes not touched in 30, 60, or 90 days across active areas
- **Tag garden**: cleans up tag sprawl by finding redundant, misspelled, or orphaned tags
- **Message archive cleanup**: archives resolved agent messages older than 7 days
## How to use it
Run the Librarian periodically to maintain vault quality:
- "Weekly review" / "Run the weekly audit"
- "Check vault health" / "Quick health check"
- "Are there any duplicates?"
- "Deep clean the vault"
- "Fix broken links"
- "Show me orphan notes"
- "Consistency report"
- "How has my vault grown?"
- "Clean up the tags"
In Italian: "Review settimanale", "Controlla il vault", "Ci sono duplicati?", "Pulizia"
In French: "Revision hebdomadaire", "Verifier le vault"
In Spanish: "Revision semanal", "Verificar el vault"
In German: "Wochentliche Uberprufung", "Vault-Gesundheit"
## Example conversations
### Weekly review
**You:** Weekly review
**Librarian:** Running full 6-phase audit...
**Phase 1, Structure:** Folders OK (12/12 match the canonical structure). 1 empty folder found: `04-Archive/2024/`. Consider removing?
**Phase 2, Duplicates:** Found 2 potential duplicates:
- "Project Plan.md" (01-Projects/) vs "Project Plan (updated).md" (01-Projects/). The updated version contains everything from the original plus 17 new lines. Recommendation: keep the updated version, archive the original.
**Phase 3, Links:** 3 broken wikilinks found and fixed:
- `[[Sprint Planning]]` updated to `[[Sprint Planning Q2]]` (file was renamed)
- `[[Marco]]` updated to `[[05-People/Marco Rossi]]` (path corrected)
- `[[Old RFC]]`: target does not exist. Should I create a stub note or remove the link?
**Phase 4, Frontmatter:** 8 notes had format issues:
- 5 notes had dates in non-standard format (auto-fixed to YYYY-MM-DD)
- 3 notes were missing `status` field (added based on file location)
**Phase 5, MOCs:** 2 MOCs are stale (not updated in 30+ days with new notes available). Updated both with 4 new entries total.
**Phase 6, Health Report:** Saved to `Meta/health-reports/2026-03-21 - Vault Health.md`
Health Score: 87% (up from 82% last week)
Notes: 147 total, 12 new this week
Orphan notes: 18 (down from 23 after Connector work)
---
### Quick duplicate check
**You:** Are there any duplicates?
**Librarian:** Scanned 147 notes for duplicates. Found 3 issues:
1. **Exact duplicate:** "Meeting Notes March 10.md" exists in both `00-Inbox/` and `06-Meetings/2026/03/`. The Inbox version is older. Recommendation: delete the Inbox copy.
2. **Near-duplicate (85% overlap):** "API Design Notes.md" and "API Architecture Draft.md" cover the same topic with different titles. The Architecture Draft is more complete. Recommendation: merge and archive the older one.
3. **Sync conflict:** "Daily 2026-03-15 (conflict).md" is a sync conflict from Obsidian Sync. The conflict version has 2 extra lines. Recommendation: merge the extra lines into the main version.
Want me to handle any of these?
---
### Growth analytics
**You:** How has my vault grown this month?
**Librarian:** Vault Growth, March 2026
- Notes created: 42 (up 15% from February)
- Average per week: 10.5
- Most active areas: Projects (18 notes), Meetings (12 notes), Resources (7 notes)
- Links created: 89 new links this month
- Link density trend: 2.1 links/note (up from 1.8 in February)
- Health score trend: 82% -> 85% -> 87% (improving steadily)
Top contributors (by agent):
- Scribe: 22 notes
- Transcriber: 12 notes
- Postman: 8 notes
Your vault is growing healthily. The link density improvement is a good sign. The Connector has been doing solid work.
## Works with
- **Architect**: when the Librarian finds structural inconsistencies that need a design decision (overlapping areas, drifting taxonomy), it flags the Architect
- **Sorter**: misplaced notes found during audits are reported to the Sorter for re-filing
- **Connector**: orphan notes that need linking are flagged for the Connector
- **Seeker**: when the Librarian finds conflicting information in duplicate notes, it asks the Seeker for content-level verification
- **Scribe**: malformed notes in the Health area are sent back to the Scribe for reformatting
- **All agents**: the Librarian cleans up the shared message board by archiving resolved messages older than 7 days
## Tips
- **Run it weekly.** A weekly audit catches small issues before they compound. Monthly audits find too much to fix at once.
- **Start with quick health checks.** If you are new to the vault, a quick check is less overwhelming than a full 6-phase audit.
- **Let it auto-fix the safe stuff.** Date format normalization, tag casing, and missing status fields are safe to fix automatically. The Librarian always asks before doing anything destructive.
- **Pay attention to the health score.** It is a single number that tells you how well-maintained your vault is. Aim for 85%+.
- **Use growth analytics for motivation.** Seeing your vault grow in notes, links, and quality is surprisingly satisfying and helps you stay consistent.
- **Act on archive suggestions.** Stale content in active areas adds noise. Archiving old notes keeps your working areas focused.
docs/agents/postman.md
+126
View File
@@ -0,0 +1,126 @@
# Postman
> Your bridge between Gmail, Google Calendar, and your vault.
## What it does
The Postman connects your email and calendar to your Obsidian vault. It scans your Gmail inbox, identifies what actually matters (action requests, deadlines, important information), and saves it as structured notes. It imports Google Calendar events as meeting prep notes. It can even create new calendar events from your vault content.
The Postman is a smart filter, not a bulk importer. It knows the difference between a critical email from a client requesting a proposal and a marketing newsletter. It recognizes deadlines, extracts action items, and creates notes with the right priority level. Everything it skips, it tells you about, so you stay informed without your vault getting flooded with noise.
It works in four modes: email triage (scan and save important emails), calendar import (bring upcoming events into your vault), event creation (schedule something from a note or request), and targeted search (find specific emails or events on a topic).
## Capabilities
- **Email triage**: scans unread Gmail messages, filters out noise (newsletters, notifications, receipts), and saves relevant emails as structured notes with action items and deadlines
- **VIP filter**: prioritizes emails from important contacts (colleagues, clients, key people)
- **Calendar import**: pulls upcoming Google Calendar events into the vault as meeting prep notes with participant lists and agenda
- **Event creation**: creates Google Calendar events from your requests or from deadlines found in vault notes
- **Targeted search**: searches Gmail or Calendar for specific topics, people, or date ranges
- **Deadline radar**: extracts all upcoming deadlines from recent emails and presents them in one view
- **Meeting prep**: creates pre-meeting notes from calendar events with participant context from your People folder
- **Weekly agenda**: generates a week-at-a-glance view combining calendar events and email-sourced deadlines
- **Travel mode**: when it detects travel-related events (flights, hotels, conferences), creates a consolidated travel itinerary note
- **Thread intelligence**: reads entire email threads and synthesizes key points and latest developments
- **Attachment awareness**: flags emails with attachments (cannot process them, but notes their existence)
## How to use it
Trigger the Postman for email and calendar tasks:
- "Check my email" / "Triage my inbox"
- "What's on my calendar this week?"
- "Create an event for Friday at 3pm"
- "Are there any urgent emails?"
- "Import this week's meetings"
- "Find emails about [topic]"
- "What deadlines are coming up?"
- "Prepare me for tomorrow's meetings"
- "Weekly agenda"
In Italian: "Controlla la mail", "Cosa ho in inbox", "Crea evento", "Cosa ho in calendario"
In French: "Verifie mes emails", "Qu'est-ce que j'ai au calendrier"
In Spanish: "Revisa mi correo", "Que hay en mi calendario"
In German: "Prufe meine Emails", "Was steht im Kalender"
## Example conversations
### Email triage
**You:** Check my email
**Postman:** Scanning your Gmail inbox... Found 28 unread messages.
Saved to vault (3):
- **"Proposal Request From Luca"**: action required, high priority. Luca needs a project proposal by next Wednesday. Saved with action items and deadline.
- **"Contract Renewal Deadline April 15"**: deadline alert. Saved with the date flagged.
- **"Sprint Demo Feedback from Client"**: contains key decisions about the product direction. Saved as informational note.
Ignored (25):
- 12 newsletters and mailing lists
- 5 automated notifications (GitHub, Jira)
- 4 purchase receipts
- 3 system notifications (2FA, password resets)
- 1 CC-only thread with no action required
Needs your input (1):
- Email from an unknown sender about "partnership opportunity." Cannot determine relevance. Want me to save it?
---
### Calendar import with meeting prep
**You:** What's on my calendar this week?
**Postman:** Your week ahead (March 22-28):
**Monday March 22:**
- 10:00-11:00, Sprint Planning with Marco, Sarah, Luca (Google Meet)
- 14:00-14:30, 1:1 with Manager
**Wednesday March 24:**
- 09:00-10:30, Client Demo (Zoom, external participants)
- 16:00-17:00, Team Retrospective
**Friday March 26:**
- 11:00-12:00, Budget Review (in person, Room 3B)
I can create meeting prep notes for any of these. For the Client Demo, I found 2 related notes in your vault that might be useful for preparation. Want me to import all events as vault notes?
---
### Event creation
**You:** Create an event for the proposal review, next Thursday at 2pm, invite Marco and Luca, one hour, on Zoom
**Postman:** Here is what I will create:
- **Title:** Proposal Review
- **Date:** Thursday, March 27, 2026
- **Time:** 14:00 - 15:00
- **Location:** Zoom (I will add the link if you have a default Zoom room)
- **Attendees:** Marco, Luca
Shall I proceed?
**You:** Yes, go ahead
**Postman:** Event created on Google Calendar. I also created a meeting prep note in `00-Inbox/` linked to the related proposal notes in your vault.
## Works with
- **Sorter**: all notes created by the Postman land in `00-Inbox/` for the Sorter to file
- **Architect**: when emails or events reveal a new project, the Postman flags the Architect to create the folder structure
- **Transcriber**: when a calendar event has a recording link (Zoom, Meet), the Postman flags it for the Transcriber
- **Connector**: email threads that reference vault notes are flagged for cross-linking
- **Seeker**: if a contact is not found in the vault, the Postman suggests searching with the Seeker
## Tips
- **Run email triage daily.** A quick scan takes under a minute and catches deadlines before they sneak up on you.
- **Use "deadline radar" on Mondays.** Start your week knowing every deadline that is coming from your emails.
- **Create meeting prep notes before important meetings.** The Postman pulls participant info from your People folder and links relevant vault notes.
- **Let it create calendar events from notes.** If a note contains a deadline or meeting plan, tell the Postman to schedule it. Saves you switching to Google Calendar.
- **Trust the noise filter.** The Postman is aggressive about filtering newsletters, notifications, and receipts. If it ever filters something important, tell it. It learns from your corrections.
- **Check "needs your input" items.** The Postman flags ambiguous emails rather than guessing. These are usually worth a quick look.
- **Make sure Gmail and Google Calendar are connected.** The Postman needs API access to your accounts. Check `Meta/user-profile.md` to verify integrations are enabled, or ask the Architect during onboarding.
docs/agents/scribe.md
+109
View File
@@ -0,0 +1,109 @@
# Scribe
> Your fast-thinking, clean-writing note-taking partner.
## What it does
The Scribe turns messy, rushed, half-formed thoughts into clean Obsidian notes. You type fast, you skip punctuation, you mix languages, you abbreviate everything. The Scribe does not care. It takes whatever you throw at it and produces polished, well-structured notes ready for your vault.
It is smart about what it captures. If you dump three unrelated topics in one message, it splits them into three separate notes. If you paste speech-to-text output full of "um" and "like," it cleans it up while keeping your voice. If you are rapid-firing ideas in brainstorm mode, it numbers them all without judging any.
Every note the Scribe creates lands in your Inbox (`00-Inbox/`), properly formatted with YAML frontmatter, tags, wikilinks to people and projects, and suggested connections to other notes. The Sorter will file them later. The Scribe's job is pure capture speed and quality.
## Capabilities
- **Standard capture**: classifies your input (idea, task, note, person, reference, list) and applies the right template
- **Voice-to-note**: detects speech-to-text output and cleans it up by removing filler words, restoring punctuation, and preserving your natural voice
- **Thread capture**: when you send a stream of consciousness, splits it into individual atomic notes linked together
- **Quote capture**: formats quotes with author, source, page number, and your commentary
- **Reading notes**: structures book/article/podcast notes with key takeaways, section-by-section summaries, and action items
- **Brainstorm mode**: captures everything without filtering, numbers ideas, groups by theme, highlights the most promising ones
- **Multi-note detection**: automatically splits unrelated topics into separate notes
- **Emotion tagging**: detects emotional tone and tags notes accordingly
- **Auto-suggested connections**: mentions 2-3 related notes or topics at the end of each note
- **Code, math, and diagram support**: wraps code in fenced blocks, uses LaTeX for math, creates Mermaid diagrams
- **Multilingual**: works in any language, handles mixed-language input gracefully
## How to use it
Just start typing what you want to capture. The Scribe detects the right mode automatically. You can also be explicit:
- "Save this: [your text]"
- "Quick note: [your text]"
- "Brainstorm: [topic]"
- "Quote: [quote text]"
- "Reading notes for [book/article title]"
- "Thread: [stream of thoughts]"
- "Voice note: [pasted speech-to-text]"
In Italian: "Salvami questo", "Nota veloce", "Appuntati"
In French: "Sauvegarde ca", "Note rapide"
In Spanish: "Guarda esto", "Nota rapida"
In German: "Schnelle Notiz", "Schreib das"
## Example conversations
### Quick messy capture
**You:** save this: meeting with Marco, budget discussion, he wants report by friday, also mentioned new hire starting in april, seems worried about Q2 numbers
**Scribe:** I identified 2 distinct topics and created 2 separate notes:
**1. Meeting With Marco, Budget Discussion**
Filed as `2026-03-21 - Note - Budget Discussion With Marco.md` in `00-Inbox/`
Key points captured:
- Marco wants the budget report by Friday
- He expressed concern about Q2 numbers
- Action item: deliver report by Friday
**2. New Hire Starting in April**
Filed as `2026-03-21 - Note - New Hire April.md` in `00-Inbox/`
Linked to [[05-People/Marco]] in both notes. Does this capture everything correctly?
---
### Brainstorm mode
**You:** Brainstorm: ways to improve the onboarding experience for new users
**Scribe:** Created `2026-03-21 - Brainstorm - Onboarding Improvements.md` in `00-Inbox/`
Captured all your ideas, numbered and grouped. I noticed 3 natural clusters: UI changes, documentation improvements, and community-driven ideas. The two most promising ideas (based on feasibility and impact) are highlighted in the Hot Takes section.
Want to expand on any of these?
---
### Voice-to-note
**You:** Voice note: so basically i was thinking about um the whole pricing structure right and like marco said yesterday that we should probably move to a tiered model because uh the enterprise clients are paying the same as the small ones and thats just not sustainable you know so maybe we do three tiers basic pro and enterprise and each one gets different levels of support
**Scribe:** Detected speech-to-text input. Cleaned and structured as:
**Pricing Structure, Tiered Model Proposal**
Marco suggested moving to a tiered pricing model because enterprise clients currently pay the same as small clients, which is not sustainable. The proposed tiers:
- **Basic**: entry level
- **Pro**: mid-tier
- **Enterprise**: full support
Each tier would include different levels of support.
Filed as `2026-03-21 - Idea - Tiered Pricing Model.md` with `source: voice-note` in the frontmatter. Sound right?
## Works with
- **Sorter** files the notes the Scribe drops in the Inbox
- **Architect** provides the templates and naming conventions the Scribe follows. If a new project or area seems to be emerging, the Scribe flags it for the Architect
- **Connector** gets flagged when the Scribe notices a note relates to many existing notes, so it can do deep linking
## Tips
- **Do not overthink your input.** The messier, the better. That is literally what the Scribe is for. Just dump your thoughts.
- **Use "quick dump" for multiple topics.** The Scribe will detect and split them automatically.
- **Paste raw speech-to-text directly.** No need to clean it up first. The Scribe handles filler words, broken sentences, and transcription artifacts.
- **Say "brainstorm" when you want zero filtering.** The Scribe will capture every idea without judging, then gently highlight the best ones.
- **Check the suggested connections.** The Scribe adds a Connections section at the end of each note. These are quick wins for building your knowledge graph.
- **Trust the assumptions.** The Scribe makes judgment calls when your input is ambiguous. It always tells you what it assumed, so you can correct it if needed.
docs/agents/seeker.md
+113
View File
@@ -0,0 +1,113 @@
# Seeker
> Ask your vault a question. Get an answer with sources.
## What it does
The Seeker is your vault's search engine and research assistant rolled into one. It does not just find files; it understands questions. Ask "What did we decide about pricing?" and it searches across meeting notes, project files, and email imports to synthesize an answer with source links. Ask "Find all notes about Marco from this month" and it queries by person, date range, and content.
The Seeker searches everything: file contents, filenames, YAML frontmatter, tags, wikilinks, and relationship graphs. It ranks results by relevance, separates high-quality matches from tangential ones, and presents everything in a clean, scannable format. When it finds nothing, it suggests alternative searches, checks for typos, and offers to create a new note on the topic.
Beyond searching, the Seeker can also modify existing notes by updating content, adding tags, fixing broken links, or appending new information. It always reads the full note first and confirms changes before making them.
## Capabilities
- **Full-text search**: searches file contents with keyword and phrase matching
- **Metadata search**: queries by type, date range, tag, person, project, or status
- **Relationship search**: navigates the wikilink graph (forward links, backlinks, common connections)
- **Answer mode**: synthesizes information from multiple notes to answer a question, with source citations
- **Timeline mode**: finds notes within a date range, useful for "what happened last week" queries
- **Diff mode**: compares versions of a topic across different notes to spot contradictions or evolution
- **Missing knowledge detection**: identifies gaps in your vault (topics mentioned but never explained)
- **Note modification**: append, update, refactor, re-tag, or fix links in existing notes
- **Cross-reference answering**: pulls data from multiple sources and presents a unified answer
## How to use it
Ask any question about your vault, or search for specific content:
- "What did we decide about [topic]?"
- "Find all meeting notes from March"
- "What do I know about [topic]?"
- "Find notes tagged #marketing"
- "What notes mention Marco?"
- "Where did I put the note about [subject]?"
- "What am I missing about microservices?"
- "Update the note about [topic] with [new info]"
- "What connects Marketing and Sales in my vault?"
In Italian: "Cerca nel vault", "Trova", "Dove ho messo", "Che note ho su"
In French: "Cherche dans le vault", "Trouve"
In Spanish: "Busca en el vault", "Encuentra"
In German: "Suche im Vault", "Finde"
## Example conversations
### Answer mode
**You:** What did we decide about the pricing model?
**Seeker:** Based on your notes, here is what I found about pricing decisions:
Marco proposed moving to a tiered pricing model (Basic, Pro, Enterprise) during the Sprint Planning on March 18. The main driver is that enterprise clients currently pay the same as small clients. The client feedback note from March 20 suggests the client is open to tiered pricing but wants volume discounts included.
No final decision has been recorded yet. The next step appears to be delivering the pricing report by Friday (March 22).
Sources:
- [[06-Meetings/2026/03/Sprint Planning Q2]] (initial proposal)
- [[02-Areas/Sales/Client Feedback on Pricing]] (client response)
- [[00-Inbox/Tiered Pricing Model]] (Marco's voice note with details)
---
### Finding notes by criteria
**You:** Find all meeting notes from this month with open action items
**Seeker:** Found 5 meeting notes from March 2026 with uncompleted action items:
Top results:
1. [[Sprint Planning Q2]], March 18, 3 open action items (2 assigned to you)
2. [[Client Review Contract]], March 15, 1 open action item (pending legal review)
3. [[Marketing Sync]], March 12, 2 open action items
Other results:
4. [[Team Standup March 10]], 1 minor follow-up
5. [[Budget Meeting]], March 5, 1 item marked low priority
Total: 8 open action items across 5 meetings. Want me to compile them into a task list?
---
### Missing knowledge
**You:** What am I missing about microservices?
**Seeker:** You have 4 notes that mention microservices, but I notice some gaps:
You have covered:
- Architecture decision to adopt microservices (from a meeting note)
- Service mesh comparison (from reading notes)
Missing or thin:
- No notes on deployment strategy or CI/CD for microservices
- No notes on monitoring and observability
- The meeting note references a "microservices RFC" that does not exist in your vault
Would you like to create notes for any of these gaps, or search for related content that might cover them indirectly?
## Works with
- **Sorter**: the Seeker can verify whether similar notes already exist before the Sorter files new ones
- **Connector**: when the Seeker finds unlinked but related notes, it flags them for the Connector
- **Librarian**: the Seeker often discovers broken links, orphan notes, or frontmatter problems while searching
- **Scribe**: if a search reveals missing knowledge, the Seeker can suggest creating a new note via the Scribe
## Tips
- **Ask questions, not just keywords.** The Seeker is best when you ask "What do I know about X?" rather than just typing "X."
- **Use it for decision archaeology.** "What did we decide about Y?" is one of the most powerful queries. It searches across meetings, emails, and project notes.
- **Request a timeline.** Saying "Show me everything about project Alpha in chronological order" gives you the full story of a project.
- **Ask about gaps.** "What am I missing about [topic]?" triggers the missing knowledge detector, which is surprisingly useful for learning and project planning.
- **Combine criteria.** "Find all notes tagged #urgent that mention Marco from the last two weeks." The Seeker handles compound queries.
- **Use it to update notes.** Instead of finding a note and editing it yourself, tell the Seeker: "Update the note about X with this new info."
docs/agents/sorter.md
+129
View File
@@ -0,0 +1,129 @@
# Sorter
> Inbox zero for your vault. Every note in the right place, every time.
## What it does
The Sorter is your vault's filing system. Notes pile up in your Inbox throughout the day: quick captures from the Scribe, email imports from the Postman, meeting notes from the Transcriber. The Sorter processes them all, figures out where each note belongs, moves it to the right folder, updates the Maps of Content, creates wikilinks, and gives you a clean summary of what went where.
It does not just look at metadata. The Sorter reads the full content of every note, detects mentioned people and projects, understands temporal context, and makes intelligent filing decisions. When something is ambiguous, it asks. When a destination folder does not exist yet, it either creates a minor subfolder or flags the Architect for a bigger structural decision.
Run the Sorter daily (or whenever your Inbox feels cluttered) and your vault stays organized without you having to think about where things go.
## Capabilities
- **Standard triage**: processes inbox notes one by one, classifying and filing each to its proper location
- **Smart batch mode**: groups related notes by project, topic, or date before filing, so related notes end up cross-linked
- **Priority triage**: scans the inbox and ranks notes by urgency (critical, high, normal, low), filing the most important ones first
- **Project pulse**: generates an activity report showing which projects received the most new notes and which have gone quiet
- **MOC updates**: automatically adds filed notes to the relevant Map of Content
- **Duplicate detection**: checks for existing notes with similar content before filing
- **Action item extraction**: pulls tasks out of notes and ensures they are captured in daily or project notes
- **Archive suggestions**: flags notes not touched in 30+ days as candidates for archiving
- **Wikilink creation**: links people to `05-People/`, projects to `01-Projects/`, and related notes to each other
- **Health-aware filing**: routes nutrition, diet, and therapy-related notes to the appropriate Health subfolders
## How to use it
Trigger the Sorter when your Inbox has accumulated notes:
- "Triage my inbox" / "Process inbox" / "File my notes"
- "Batch sort" / "Smart batch" (for 10+ notes)
- "Priority triage" / "Urgent first" / "What needs attention?"
- "Project pulse" / "Which projects are active?"
- "What's piling up?"
- "Evening triage" / "Daily digest"
In Italian: "Smista la inbox", "Pulisci la inbox", "Svuota inbox"
In French: "Trie la boite de reception", "Range mes notes"
In Spanish: "Ordena la bandeja", "Triaje"
In German: "Sortiere den Eingang", "Posteingang aufraumen"
## Example conversations
### Standard triage
**You:** Triage my inbox
**Sorter:** Inbox: 6 notes to process
1. [Meeting] 2026-03-18, Sprint Planning Q2
2. [Idea] 2026-03-19, New Onboarding Approach
3. [Task] 2026-03-20, Call Supplier by Wednesday
4. [Note] 2026-03-20, Client Feedback on Pricing
5. [Quote] 2026-03-21, Seneca on Time Management
6. [Email] 2026-03-21, Proposal Request From Luca
Here is my filing plan:
- Sprint Planning Q2 --> `06-Meetings/2026/03/` (linked to [[01-Projects/Product]])
- New Onboarding Approach --> `01-Projects/Rebrand/` (matches active project)
- Call Supplier --> extracted as task in today's daily note
- Client Feedback on Pricing --> `02-Areas/Sales/` (linked to [[05-People/Marco]])
- Seneca on Time Management --> `03-Resources/Quotes/`
- Proposal Request From Luca --> `01-Projects/Consulting/` (action required, high priority)
Shall I proceed?
---
### Priority triage
**You:** What needs attention?
**Sorter:** Priority scan of 8 inbox notes:
**Critical (act today):**
- "Call Supplier by Wednesday" (deadline is tomorrow)
- "Proposal Request From Luca" (client waiting for response)
**High (this week):**
- "Sprint Planning Q2" (meeting notes with 3 unresolved action items)
- "Client Feedback on Pricing" (relates to active project decision)
**Normal:**
- "New Onboarding Approach" (idea, no deadline)
- "Reading Notes, Atomic Habits Ch3"
**Low:**
- "Seneca on Time Management" (quote, archivable)
- "Random Bookmarks List"
Want me to file the critical items first?
---
### Project pulse
**You:** Project pulse
**Sorter:** Project Pulse, 2026-03-21
Most Active:
1. **Rebrand**: 7 new notes this week (3 meetings, 2 ideas, 2 tasks)
2. **Consulting**: 4 new notes (2 emails, 1 meeting, 1 task)
Quiet (no new notes in 7+ days):
- **Beta Launch**: last note on 2026-03-10
- **Internal Tools**: last note on 2026-03-05
Emerging Topics (not yet a project/area):
- "AI automation" mentioned in 4 recent notes. Consider creating a dedicated area?
## Works with
- **Scribe**: most notes in the Inbox come from the Scribe
- **Postman**: email and calendar imports land in the Inbox for the Sorter to process
- **Transcriber**: meeting transcriptions arrive in the Inbox
- **Architect**: when notes do not fit any existing folder, the Sorter flags the Architect to create new structure
- **Connector**: after filing a batch, the Sorter can flag notes for the Connector to cross-link
- **Librarian**: the Sorter reports duplicates and broken links it finds during triage
## Tips
- **Run it daily.** A small inbox is fast to process. A huge inbox takes longer and produces worse results because context fades.
- **Use smart batch when you have 10+ notes.** The Sorter will group related notes together, which produces better cross-links than one-by-one processing.
- **Trust the filing plan.** The Sorter always shows you where it intends to file before moving anything. Review the plan, approve, and move on.
- **Check the archive suggestions.** At the end of every triage, the Sorter flags stale notes. Archiving keeps your active areas lean.
- **Use project pulse weekly.** It is a quick way to see where your energy is actually going versus where you think it is going.
- **Never delete notes.** The Sorter follows a strict no-deletion policy. Notes are moved, archived, or merged, never destroyed.
docs/agents/transcriber.md
+132
View File
@@ -0,0 +1,132 @@
# Transcriber
> Turns raw recordings and transcripts into structured, actionable meeting intelligence.
## What it does
The Transcriber takes raw audio transcripts (meetings, lectures, podcasts, interviews, voice memos) and transforms them into richly structured Obsidian notes. It does not just clean up text. It extracts the intelligence: decisions made, action items with owners and deadlines, key insights, emotional dynamics, and follow-up needs.
Paste a messy Zoom transcript full of filler words and speaker labels, and the Transcriber will produce a polished meeting note with an executive summary, a decisions log, an action items table with confidence scores, and even a draft follow-up email you can send to attendees. Paste lecture notes, and it creates study-ready material with key concepts, definitions, and exam-relevant highlights.
The Transcriber works with whatever you give it, whether that is output from Whisper, Otter.ai, Google Meet auto-transcription, or your own handwritten notes from a call. It adapts its parsing to the source format and asks just enough context questions to produce the best possible output.
## Capabilities
- **Meeting notes**: full meeting processing with executive summary, key points, decisions log, action items table (with confidence scores), detailed notes by topic, open questions, next steps, and a follow-up email draft
- **Lecture notes**: structured academic notes with key concepts, definitions, exam-relevant points, and connections to previous material
- **Podcast summaries**: TL;DR, numbered key insights, notable quotes, detailed breakdown by topic, and resources mentioned
- **Interview extraction**: structured Q&A format, key takeaways, notable quotes, and follow-up questions
- **Voice journal**: personal reflections with mood detection, structured themes, and insights
- **General transcription**: clean transcript with executive summary and key points for anything that does not fit the above
- **Multi-speaker detection**: identifies and labels different speakers throughout the transcript
- **Action item extraction**: catches explicit, implicit, and conditional actions with confidence levels
- **Sentiment analysis**: flags emotionally charged segments (heated debates, frustration, enthusiasm)
- **Glossary generation**: extracts domain-specific terms and jargon into a glossary table
- **Follow-up email generator**: creates a ready-to-send email summarizing meeting outcomes
## How to use it
Paste a transcript or describe what you want to process:
- "Transcribe this meeting: [paste transcript]"
- "Process these meeting notes"
- "Summarize this podcast transcript"
- "Create lecture notes from this: [paste]"
- "Process my voice memo"
- "What came out of the meeting? [paste]"
- "Interview notes: [paste transcript]"
In Italian: "Trascrivi", "Sbobina", "Note del meeting", "Riassumi la call"
In French: "Transcrire", "Notes de reunion", "Resume du podcast"
In Spanish: "Transcribir", "Notas de reunion", "Resumen del podcast"
In German: "Transkribieren", "Besprechungsnotizen", "Podcast-Zusammenfassung"
## Example conversations
### Meeting transcript processing
**You:** Process this meeting transcript: [pastes a 40-minute Zoom meeting transcript]
**Transcriber:** Before I process this, let me gather some context:
1. Date of the meeting? (I will default to today if not specified)
2. Can you confirm the participants? I detected 4 speakers: Marco, Sarah, you, and someone labeled "Speaker D"
3. Does this relate to a specific project?
**You:** Yesterday, Speaker D is Luca, it's about Project Alpha
**Transcriber:** Got it. Here is the processed meeting note:
**Sprint Planning, Project Alpha** (saved to `00-Inbox/`)
- Executive Summary: 4-sentence overview of the meeting
- 6 Key Points covering the main topics discussed
- 3 Decisions Made (with who decided and rationale)
- Action Items table:
| Who | What | Deadline | Confidence |
|-----|------|----------|------------|
| You | Deliver pricing report | Friday | High |
| Marco | Review API specs | Next Monday | High |
| Sarah | Schedule client demo | TBD | Medium |
| Luca | Investigate performance issue | This week | Low (inferred) |
- Detailed notes broken into 4 topic sections with timestamps
- 2 Open questions flagged for follow-up
- Follow-up email draft ready to send to attendees
Want me to adjust anything?
---
### Podcast summary
**You:** Summarize this podcast transcript. It's the Tim Ferriss show, episode about deep work with Cal Newport
**Transcriber:** Created `2026-03-21 - Podcast - Tim Ferriss on Deep Work.md`
**TL;DR:** Cal Newport argues that deep work is becoming both rarer and more valuable in the knowledge economy. The key insight: scheduling deep work blocks is more effective than trying to "find time" for it.
**Key Insights (7):**
1. Deep work is a skill that atrophies without practice...
2. The "any benefit" mindset for tools is the enemy of focus...
[...]
**Notable Quotes:** 3 blockquotes captured with speaker attribution
**Resources Mentioned:** 4 books and 2 tools referenced in the episode
I also noticed this connects to your notes on productivity systems in `03-Resources/`. Want me to flag it for the Connector?
---
### Voice journal
**You:** Process my voice memo: [pastes a personal reflection transcript]
**Transcriber:** Processed as a Voice Journal entry.
**Detected mood:** Reflective, slightly anxious
**Energy level:** Medium
Core reflection: You are processing the tension between your desire to take on the new project and your concern about overcommitting, especially given recent burnout.
I structured your thoughts into 3 themes: work-life boundaries, the new project opportunity, and recovery from burnout.
Saved as `2026-03-21 - Voice Journal - New Project Tensions.md`. Want to review it?
## Works with
- **Sorter**: all transcription output lands in the Inbox for the Sorter to file
- **Postman**: when a meeting note references email threads, the Transcriber flags the Postman to cross-link
- **Architect**: when a meeting introduces a new project or area, the Transcriber notifies the Architect
- **Connector**: meeting notes that reference past decisions are flagged for cross-linking
## Tips
- **Provide participant names upfront.** The Transcriber asks for names, but giving them in your first message saves a round trip.
- **Mention the project or area.** Context helps the Transcriber tag and link more accurately.
- **Use the follow-up email draft.** For work meetings, the auto-generated email is a huge time saver. Review it and send.
- **Check the confidence scores on action items.** "High" means someone explicitly said it. "Low" means the Transcriber inferred it from context, so verify these.
- **Use voice journal mode for personal reflections.** It preserves your authentic voice instead of making everything sound corporate.
- **Paste raw transcripts without cleanup.** The Transcriber handles filler words, broken sentences, and transcription artifacts. Do not waste time pre-editing.