mattrguerra/meridian-outreach-vaultmainPrivate on GitHub, published here in full

SETUP.md

Language Markdown1.8 KB19 lines

SETUP.md

  1. ---
  2. type: setup
  3. scope: project-root
  4. tags: [claude, outreach, setup]
  5. created: 2026-06-16
  6. updated: 2026-06-16
  7. ---
  8. # SETUP: Quarterly Outreach
  9. 1. **Open in Obsidian:** Open Obsidian, choose "Open folder as vault", and point it at the vault's root folder.
  10. 2. **Install Dataview (required):** Settings, Community plugins, browse, install and enable **Dataview**, then turn on "Enable JavaScript Queries" in its settings. The tier and outreach notes and [[00-Index]] use Dataview and DataviewJS queries to list their members. Without it those code blocks show as plain text.
  11. 3. **Optional plugins:** `.obsidian/community-plugins.json` also lists the plugins the operators ran for comfort, by plugin id: `nested-properties`, `file-explorer-note-count`, `calendar`, `code-styler`, `obsidian-file-color`, `obsidian-minimal-settings`, `omnisearch`, `pinned-notes`, `start-page`, `text-brush`, `cmdr`, and `nested-vaults`. None of them is needed for the vault to work. **Plugin code is not shipped** (there is no `.obsidian/plugins/` folder in the repo): install any you want from Obsidian's community plugin browser, and Dataview is the only one you must install.
  12. 4. **Point Cowork at this folder** so Claude can read and write the stubs.
  13. 5. **Confirm the source files** are present: the seed roster workbook in `07-Automation/sample/inputs/` (see [[Source-Documents]]). The original outreach design doc the templates came from is not included.
  14. 6. **Browse:** start at [[00-Index]] for navigation or [[CLAUDE]] for how Claude should work here.
  15. 7. **Enrich a client:** open a stub, run research, append findings under `## Research`. See [[CLAUDE-clients]].
  16. 8. **Send outreach:** pick the play ([[Check-In-Outreach]] / [[Executive-Outreach]] / [[Winback-Outreach]]), draft from the linked template using the `matt-guerra-email` skill, and log it in the stub's Outreach Log.