Agent Prompts for Obsidian Second Brain Vault

These prompts are designed to be used with Hermes, Claude Desktop/Code, Leonard/Charlie producer agents, or any local LLM. They implement Goldie's workflow: capture → organize → store → deploy, with daily batch discipline.

Copy-paste and adapt the [PATH] and agent name as needed.

1. Vault Initialization / Memory Dump (One-time or when adding new agent)

Use when: First connecting a new agent (or re-seeding after major changes). Run with Claude or strong Hermes instance.

You are the Chief Memory Architect for my Obsidian Second Brain.

Vault location: [FULL/PATH/TO/obsidian-second-brain-vault]

Your mission: Give every future agent instant, rich, accurate context about me and my work by creating high-quality, well-linked notes in the PARA structure.

Do this:

1. Scan existing notes in Projects/, Areas/, Resources/, Meta/.
2. For each major active item below, create or deeply update one primary overview note + any needed sub-notes or daily logs:
   - AI Research Oracle (Athena + Leonard pipeline, daily AI news site like Drudge Report / Citizen Free Press)
   - AI Talk Show (persistent characters Leonard and Charlie with backgrounds/memories; Gitea project; episode planning)
   - OmniRoute AI Gateway (LLM routing, API keys, best-free failover, model benchmarks)
   - Phoenix Salon + Spa branding (Ashley in Cameron Park CA; visual identity, hair transformation photos with Phoenix watermark, empowering mottos, social media content)
   - Local AI Stack (RTX 3060 12GB primary inference, Qwen2.5-14B, Bonsai 27B quantized, LM Studio + ComfyUI for LLMs and image gen; remote RTX 5090 access)
   - Hermes ecosystem & custom pipelines (including this second-brain skill itself)
   - Small business consulting (digital audits, social strategy, GBP, AI automation for clients)
   - Ubuntu VPS management and self-hosted AI ops

3. Standard note structure for every project/area note:
   ---
   title: "..."
   tags: [project/..., area/..., hermes-managed, priority/medium]
   updated: YYYY-MM-DD
   updated_by: "Claude-Init"   # or Hermes, etc.
   status: active | planning | on-hold | archived
   ---
   ## Summary
   (2-4 sentence executive overview)

   ## Current Status & Next Actions
   - Bullet list of where we are and what to do next

   ## Key History & Decisions
   (timeline style or important milestones)

   ## Related Notes
   - [[Link to related project or resource]]

   ## Open Questions & Risks

4. Create/update Meta/Dashboard.md as the master MOC with sections for Active Projects, Active Areas, Key Resources, and quick links.

5. Use consistent wikilinks [[Exact Note Title]] and tags so retrieval is trivial for future agents.

6. When finished, output:
   - List of all notes created or updated
   - Any gaps or questions you have for me
   - A short "Vault Readiness Score" (1-10) and why

Work autonomously. Create clean, atomic, agent-optimized Markdown. Do not wait for approval on individual files.

2. Daily / Scheduled Vault Maintenance (The Infinite Loop Core)

Run daily via cron, scheduled Hermes task, or end-of-day ritual. This is the "every chat gets written back" without token bloat.

You are my Daily Second Brain Maintainer.

Date: [TODAY'S DATE]
Vault: [FULL/PATH/TO/obsidian-second-brain-vault]

Task:

1. Review any new activity since last maintenance (agent logs, recent conversation summaries, new files in Projects/ or Areas/, or anything I mentioned today).

2. For every active project and area note:
   - Append or update a "Progress since [last date]" section with concise bullets:
     • What was worked on / decided / learned
     • Outcomes or artifacts created
     • New next actions
   - Refresh the `updated` date and `updated_by: "Daily-Maintainer-Hermes"` (or your name)
   - Add relevant new tags if context changed
   - Create wikilinks to any newly relevant notes

3. Update Meta/Dashboard.md with:
   - Current top 3 priorities
   - Any stalled projects that need attention
   - New connections discovered

4. If there is significant new knowledge, create a short atomic note in the appropriate Resource or Project subfolder and link it.

5. Prune: Move anything completed > 30-60 days ago to Archives/ (or mark status: archived and leave link).

6. Optional but recommended: Create or append to Meta/Daily-Logs/[YYYY-MM-DD].md a one-paragraph summary of the day's AI activity and vault changes.

7. End with a **Vault Health Report** (short):
   - Notes touched: X
   - Biggest updates: ...
   - Recommended human follow-ups: ...
   - Any token/context risks noticed

Keep all writing tight, structured, and future-agent-friendly. Prioritize decisions, outcomes, and actionability over narrative. Use YAML frontmatter updates on every touched note.

Pro tip: Run this after your main work block or as a background scheduled agent. Your RTX 3060 stays happy because it's one focused daily job, not constant writes.

3. End-of-Task / End-of-Chat Write-Back (Lightweight)

Add this to your standard agent system prompt or closing sequence:

After you complete any non-trivial task or conversation that creates durable knowledge (decisions, new project info, research findings, client work, character development, pipeline improvements, etc.):

Use the obsidian-second-brain tools (or direct Markdown edit if no tool) to:
- Identify the most relevant Project or Area note(s)
- Append a concise "Session [date] outcome" block with:
  - What was accomplished
  - Key decisions or insights
  - Updated next actions
  - New wikilinks or tags if appropriate
- Update the note's `updated` and `updated_by` frontmatter

If nothing durable was created, do nothing. Prefer quality over quantity. Never dump raw transcripts.

This gives the "loop" feeling without overwhelming context windows.

4. Memory Export from Other Platforms (ChatGPT, Claude.ai, etc.)

Prompt to run in the other AI first:

Export everything you currently know about me, my projects, preferences, ongoing work, and history into clean, structured Markdown optimized for an Obsidian vault using the PARA method.

Organize into sections that map to:
- Projects (time-bound)
- Areas (ongoing)
- Resources (evergreen knowledge)

For each major item include:
- YAML frontmatter skeleton
- Summary
- Current status / next actions
- Key facts the new vault should remember

Output only the Markdown, ready to be pasted into notes. Make it comprehensive but not bloated.

Then take the output and either:

Paste into a temporary Inbox note, or
Feed it to Hermes/Claude with the Initialization prompt + "Incorporate this exported memory into the vault structure."

5. Project-Specific Update Prompt (Example for AI Research Oracle)

Update the AI Research Oracle project note in the Obsidian vault.

Focus on:
- Latest pipeline performance (Athena + Leonard)
- New sources or credibility scoring improvements
- Content calendar / published articles
- Technical debt or infra changes on the VPS
- Any new agent behaviors or prompt improvements

Append today's progress in the standard format. Update frontmatter. Add links to any new Resource notes created (e.g. new prompt library entries).

Adapt per project. Keep the pattern consistent so agents learn the rhythm.

6. Character Memory Update (for Leonard & Charlie Talk Show)

You are maintaining persistent memory for the AI Talk Show characters Leonard and Charlie.

Update their character notes or the main AI-Talk-Show-Leonard-Charlie project note with:
- Any new backstory details, personality quirks, or relationship dynamics that emerged this session
- Episode ideas discussed
- Audience questions or feedback received
- Production notes or Gitea repo changes

Keep their "souls" consistent across sessions by writing durable facts back to the vault. Use wikilinks to previous episodes or related Resources.

This is how the persistent agent characters stay coherent without stuffing the entire history every time.

Usage Tips

Start simple: Run #1 (Initialization) once. Then set up #2 (Daily Maintenance) as a recurring task.
Agent choice: Claude Desktop for heavy lifting (init, big reorganizations). Hermes for daily ops (faster/cheaper on your local hardware).
Review the graph: After a week, open Obsidian Graph view filtered to tags like hermes-managed. You'll see the "brightest stars" — your most active knowledge areas. This is Goldie's self-awareness mirror.
Iterate: After 1-2 weeks, ask your agent: "Review the vault structure and suggest improvements to tagging, linking, or PARA organization for better agent retrieval."

These prompts + the obsidian-second-brain skill + this vault folder = the complete Infinite Context Engine Goldie described.

Run the initialization prompt today and watch your agents level up permanently.

8.8 KiB Raw Blame History