Steph Ango (Kepano), CEO of Obsidian, has open-sourced the architecture and custom integration skill set for his personal "Second Brain" vault. Moving away from bloated, proprietary cloud databases, Ango’s blueprint combines flat-file local Markdown with AI-agent integrations (via Claude Code and CLI tools). This piece analyzes how professionals, particularly knowledge workers navigating Singapore’s rapidly digitizing economy, can leverage this open-sourced architecture to build an enduring, AI-accessible personal knowledge base.
A stroll through Singapore’s Financial District during the morning rush presents a striking study in cognitive load. Commuters step off the MRT at Raffles Place, eyes locked to smartphones, triaging an relentless stream of Slack messages, PDF reports, WhatsApp advisories, and financial briefs. We are drowning in information yet starved of structure. For years, the corporate remedy was simple: deposit everything into proprietary, cloud-hosted workspaces. But as organizations scale their reliance on Artificial Intelligence, a glaring vulnerability has emerged: proprietary silos lock up context, turning personal knowledge bases into unsearchable digital graveyards.
Enter Steph Ango (known online as Kepano), the CEO of Obsidian. Ango recently open-sourced his personal Obsidian vault template alongside
obsidian-skills—a set of integrations allowing local AI agents to seamlessly read, write, and organize local notes.Ango’s philosophy rests on a fundamental principle: File over app. By storing knowledge in standard, local Markdown files rather than vendor-locked databases, your data outlives any individual software application or AI model.
1. The Architecture of a Sovereign Vault
Most knowledge management systems collapse under their own weight.
My Vault/
├── 0-raw/ # Ingestion inbox (PDFs, Web Clips, Transcripts)
├── 1-wiki/ # Permanent, curated concept notes & entities
├── 2-digests/ # Periodic reviews, project briefs, and summaries
├── references/ # Media, books, and external sources
├── CLAUDE.md # Vault schema & rules for AI agents
└── identity.md # Personal context, active priorities & style guide
Eliminating Deep Folder Structures
Instead of nestling notes three levels deep inside sub-folders, Ango places notes primarily in the root directory or within a few broad reference folders.
categories: or tags:) and extensive internal linking.references/ directory.Bounded Metadata Rules
To avoid metadata entropy, Ango applies a strict set of personal conventions:
- Pluralized Tags: Always use plural nouns for categories and tags (e.g.,
#frameworksinstead of#framework) to eliminate hesitation when tagging. - ISO 8601 Dates: Standardized date formats (
YYYY-MM-DD) ensure chronological notes sort naturally across any operating system or CLI tool. - Bi-directional Links: Heavy use of
[[WikiLinks]]creates a natural graph of connected ideas rather than a rigid top-down tree.
2. The AI Inversion: Designing Vaults for Machine Readability
The true shift in Ango’s open-sourced setup is how human notes interact with Large Language Model (LLM) agents.
The CLAUDE.md Schema File
At the root of the open-sourced vault sits a single control file:
CLAUDE.md. - Directory Constraints: Where new incoming notes should be saved.
- Formatting Rules: Required frontmatter fields, metadata schemas, and linking standards.
- Retrieval Protocol: How the agent should search the vault before resorting to web queries.
Local AI Agent Integration via obsidian-skills
Through the newly released
obsidian-skills package, CLI-based AI tools can execute native operations directly on the vault:- Semantic Search: The agent queries notes by concept rather than exact keyword matches.
- Automated Reconciliation: The agent scans incoming raw materials (PDFs, meeting transcripts), extracts key insights, creates structured wiki notes, and links them back to existing concept pages.
- Contradiction Auditing: Background routines flag instances where new data contradicts previously recorded decisions or facts.
Because everything is stored in local Markdown files, your personal memory remains independent of any single model supplier.
3. The Singapore Context: Building Personal Knowledge Moats
In Singapore’s hyper-competitive economic landscape, professional differentiation relies on high-value synthesis. Whether analyzing regulatory shifts in regional fintech, evaluating AI supply-chain logistics across Southeast Asia, or managing regional FP&A portfolios, off-the-shelf AI tools provide the exact same answers to everyone.
The competitive edge belongs to those who combine global AI models with a hyper-specific, private context layer.
+-----------------------------------------------------------------+
| GLOBAL PUBLIC AI MODELS |
| (Commoditized Baseline Knowledge & Reason) |
+-----------------------------------------------------------------+
│
▼
+-----------------------------------------------------------------+
| LOCAL OBSIDIAN VAULT |
| • Private Industry Notes • Regional Regulatory Logs |
| • Internal Project History • Personal Strategic Principles |
+-----------------------------------------------------------------+
│
▼
+-----------------------------------------------------------------+
| HIGH-LEVERAGE DECISION OUTPUT |
| (Proprietary Insights & Contextual Strategy) |
+-----------------------------------------------------------------+
Consider a senior analyst based in Marina Bay. When evaluating a new AI governance policy, generic LLM queries return broad, surface-level summaries. However, an analyst operating Ango’s open-sourced vault pattern can run an agent command that cross-references the public regulatory document against years of internal meeting records, private industry notes, and local operational constraints stored in their local Markdown files.
Furthermore, with strict data sovereignty rules and increasing scrutiny over corporate data leaks, Ango’s local-first architecture keeps sensitive IP strictly on-device. The raw data never resides on third-party database servers, providing complete compliance peace of mind.
4. Practical Implementation: How to Deploy the Vault Step-by-Step
To adapt Steph Ango’s open-sourced setup for your daily workflow, follow this practical setup guide.
Step 1: Initialize the Local Vault
- Download and install Obsidian (free for personal use).
- Create a new local folder on your computer named
Second-Brain. - Establish a lightweight folder hierarchy:
0-raw/— Ingestion inbox for unorganized clipping, transcripts, and source PDFs.1-wiki/— Ever-green concept pages and atomic summaries.2-digests/— Weekly reviews, project briefs, and temporal logs.references/— Notes on books, articles, and external publications.
Step 2: Establish Your Root Identity and Rules
Create two Markdown files at the root level:
identity.md: Define who you are, your core operational role, current key projects, and communication preferences.AI agents read this first to calibrate their answers to your exact context. CLAUDE.md: Provide explicit rules for AI formatting:Markdown# Vault Rules - Always format tags as lowercase plural nouns (e.g., #frameworks). - Never alter files inside `0-raw/`. Treat raw files as read-only audit trails. - When creating wiki pages in `1-wiki/`, include frontmatter with `created: YYYY-MM-DD` and `categories: []`. - Link new notes to at least two existing wiki notes using [[Note Title]] syntax.
Step 3: Connect Local AI Agents
If you use terminal-based AI tools or local LLMs, connect them to your vault directory:
- Open your terminal and navigate to your vault path:
cd ~/Documents/Second-Brain. - Install the Obsidian skill set:
npx skills add kepano/obsidian-skills. - Run prompt tasks directly against your files:"Read the transcript in
0-raw/2026-11-05-strategy.md, extract key action items into2-digests/, and update the relevant concept notes in1-wiki/."
Key Practical Takeaways
- Embrace Plain Text Sovereignty: Store knowledge in open local Markdown files to ensure your second brain remains accessible regardless of which software or AI models come and go.
- Minimize Folder Overhead: Avoid complex sub-folder trees. Rely on root-level personal notes, reference folders, tag properties, and bi-directional links for fluid organization.
- Write Rules for Agents (
CLAUDE.md): Maintain a root configuration file outlining tagging rules, folder permissions, and metadata requirements so AI assistants can maintain your vault cleanly. - Protect Raw Ingestion: Store original PDFs, voice transcripts, and clippings in a dedicated
0-raw/directory as an untouched audit trail before synthesizing into permanent wiki notes. - Leverage Private Context as a Moat: Combine public AI intelligence with your localized vault context to produce unique, high-leverage strategic analysis.
Frequently Asked Questions
Does open-sourcing a vault mean my personal data is made public?
No. Steph Ango open-sourced his vault template, architecture, scripts, and configuration rules—not his private personal notes.
Do I need programming experience to use this Second Brain setup?
Not at all. At its core, Obsidian operates as a simple desktop app for writing Markdown notes.
obsidian-skills) enhance automated maintenance, you can comfortably use the folder layout, metadata rules, and standard Obsidian plugins entirely through the graphical interface.How does this approach differ from cloud tools like Notion or Evernote?
Cloud-first tools store content inside proprietary databases, locking your data into their specific app ecosystems.