internal-vault-routing

Route local vault context to Obsidian notes for CRM-backed workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JinLee794/L.C.G --skill internal-vault-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: internal-vault-routing
Source: https://github.com/JinLee794/L.C.G/tree/main/.github/skills/internal-vault-routing
Command: npx skills add https://github.com/JinLee794/L.C.G --skill internal-vault-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The vault is the local context layer. CRM is system-of-record for live state, while Obsidian notes provide durable memory and cross-medium context. This skill coordinates vault-prefetch, customer roster, and connect hooks to route and enrich local knowledge.

Core Features & Use Cases

  • Vault tools and scope: get_vault_context, get_customer_context, oil_get_opportunity_context, oil_get_milestone_context, prepare_crm_prefetch, search_vault, query_notes
  • Correlate and promote: resolve_people_to_customers, correlate_with_vault, promote_findings, capture_connect_hook
  • Entity sync writes (gated): oil_create_opportunity, oil_update_opportunity, oil_create_milestone, oil_update_milestone, manage_pending_writes
  • Vault standards: Entity Icon & Link Standards, MSX record links, and frontmatter requirements
  • Vault lifecycle: VAULT-PREFETCH, VAULT-CORRELATE, VAULT-PROMOTE, VAULT-SYNC, and fallback behavior
  • References to vault-sync templates for structured notes (customer, opportunity, milestone, people, project)

Quick Start

Run the vault routing workflow to prefetch customer context and align local vault notes with CRM data.

Frequently Asked Questions about internal-vault-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Obsidian vault notes with CRM data for customer context?

Obsidian vault routing automates syncing local vault notes with CRM data by prefetching customer context, correlating records, and promoting findings to durable memory using structured templates and gated writes.

What is vault prefetch and how does it work for Obsidian workflows?

Vault prefetch is a lifecycle stage that retrieves CRM-backed customer context and aligns it with local Obsidian notes before executing correlate, promote, or sync operations. It ensures structured templates are populated with live state data.

Can I use Obsidian to manage customer rosters and CRM milestones?

Yes, this routing workflow supports managing customer rosters and CRM milestones in Obsidian by resolving people to customers, fetching milestone context, and applying gated entity sync writes to update opportunities and milestones safely.

How do I promote findings from Obsidian vault notes back to CRM records?

You can promote findings by running the VAULT-PROMOTE lifecycle stage, which captures connect hooks and routes enriched local context from Obsidian notes back to CRM system-of-record using gated write operations.

What happens when CRM data is unavailable during vault routing?

When CRM data is unavailable, the vault routing workflow applies safe fallback behavior defined in the VAULT-SYNC lifecycle stage, ensuring local Obsidian context remains accessible without corrupting CRM system-of-record state.

Does vault routing require specific frontmatter or link standards for Obsidian notes?

Yes, vault routing enforces Entity Icon and Link Standards, MSX record links, and frontmatter requirements to ensure Obsidian notes maintain structured formats compatible with CRM-backed workflows and cross-medium context assembly.