Customer Notes — Obsidian Template

A lightweight Obsidian vault for tracking customer accounts, use cases, meetings and tasks — with daily notes linked to use cases, TaskNotes tasks, customer notes, use case notes, and embedded bases that tie them together. Flat folder layout, no methodology to learn. Built with Databricks field work in mind, but generic enough for any account-based note-taking. Companion Claude Code skills: the obsidian-customer-notes plugin.

What's included

Folder structure

Use Cases.base   ← (vault root) browsable overview of all use cases
Customers/       ← one folder per customer
  Meeting History.base   ← embed-only base
  <Customer>/
    <Customer>.md        ← the customer note
    Use Cases/           ← the customer's use case notes
Daily/           ← daily notes (YYYY-MM-DD.md), one heading per meeting
TaskNotes/       ← TaskNotes plugin layout
  Views/         ← the plugin's view bases (tasks/kanban/calendar/agenda/...)
  Tasks/         ← TaskNotes task files
Templates/       ← note templates (Use Case, Customer, Daily Note)

Custom bases

• Use Cases.base (vault root) — views: Pending, All, Embedd; the browsable overview of all use cases, with the Embedd view embedded in each customer note
• Customers/Meeting History.base — embed-only; cross-references daily notes with a use case (embedded in each use case)

TaskNotes views (in TaskNotes/Views/, managed by the plugin)

The plugin's default view bases (tasks, kanban, calendar, agenda, mini-calendar, relationships). The Embedd view in tasks-default.base lists a use case's open tasks and is embedded in each use case.

Templates

• Use Case.md — frontmatter + sections for a use case
• Customer.md — customer/account note
• Daily Note.md — seeds the one-heading-per-meeting convention

Example content

A sample customer (Acme) with one use case, a daily note that links to it, and a task — so the bases render out of the box.

Setup

1. Create the vault

Use this folder as an Obsidian vault (open the folder in Obsidian). It already ships a configured .obsidian/.

2. Install the Obsidian plugins

In Obsidian → Settings → Community plugins → Browse:

Plugin	Required	Use
TaskNotes	Yes	Task management
Terminal	No	Integrated terminal in Obsidian

TaskNotes is pre-configured to its standard layout: task notes in TaskNotes/Tasks/ and view bases in TaskNotes/Views/ (the six default views ship with the template; auto-generation of default views is disabled so they aren't recreated).

Note (Terminal on Windows/Linux): the shipped Terminal config has its default profile set to macOS (darwinIntegratedDefault, /bin/zsh). If you're on Windows or Linux, open Settings → Terminal → Profiles and set the default profile to your platform's integrated profile (the profiles for all platforms already exist in the config). This only affects the optional Terminal plugin.

3. Install the Claude Code skills

claude plugin install kepano/obsidian-skills
claude plugin install <owner>/obsidian-customer-notes

kepano/obsidian-skills is a prerequisite — it provides the Obsidian CLI and syntax references used by the skills.

4. Make it yours

• Replace the Acme example with your own customers
• Edit CLAUDE.md with any extra context
• Adjust the theme/products values in Templates/Use Case.md

Skills (Claude Code)

Skill	Description
/obsidian-customer-notes:uco-creation	Create use case notes from the template
/obsidian-customer-notes:meeting-sync	Sync meeting notes from daily notes into each use case's timeline
/obsidian-customer-notes:tasknotes-manager	Create and manage TaskNotes tasks