# Vault Read

> Retrieve reliable information from a long-term Markdown Vault without modifying it. Use for questions that require finding current facts, configuration, project state, or relevant history in the Vault.

- Skill: `faroxdev/vault-read` (Agent Skill)
- Install (CLI): `npx skillmds@latest add faroxdev/vault-read`
- Raw SKILL.md: https://api.skillmd.com/api/skills/faroxdev/vault-read/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: faroxdev (https://skillmd.com/u/faroxdev)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/faroxdev/vault-read

---


# Vault Read

## Purpose

Safely retrieve high-quality information from a long-term Markdown Vault.

## When to Use

Use this skill to answer questions from existing Vault content, locate canonical knowledge, or trace relevant historical context.

## When Not to Use

Do not use this skill to create, edit, move, rename, or delete notes. Use `vault-maintain` for persistent changes and `vault-review` for knowledge-base audits.

## Principles

Apply these evidence priorities:

```text
Current > History
Active > Archived
Explicit fact > inference
Canonical entity note > chronological note
20-Tech / 30-Projects > 10-Daily > 00-Inbox
```

Treat the Markdown Vault as the source of truth. Any search index is only a rebuildable aid.

## Workflow

1. Clarify the information being requested and the required level of certainty.
2. Search titles, aliases, and relevant keywords.
3. Identify the likely canonical entity or project note.
4. Read its summary and current-state sections first.
5. Read relevant architecture, configuration, operations, or troubleshooting sections.
6. Inspect history or chronological notes only when current content is insufficient or the question is historical.
7. Follow relevant links when they are needed to confirm context or resolve ambiguity.
8. Answer with explicit facts, distinguish inference, and note unresolved conflicts.

## Rules

- Use Current as the starting point, not proof of freshness. If later dated evidence contradicts it, report the conflict rather than silently preferring either statement.
- Distinguish document edits from factual verification. Report the evidence date and scope; a recent `updated` value does not establish live system state.
- Do not infer that a component remains in production merely because an old record mentions it.
- Treat `00-Inbox` as unorganized input and `10-Daily` as chronological context, not authoritative current state.
- Prefer long-term technical notes in `20-Tech` and lifecycle/project notes in `30-Projects` when evidence conflicts.
- Report uncertainty when no canonical or current statement resolves a conflict.
- Do not mutate the Vault.

## Completion Criteria

The answer identifies the strongest current evidence, separates facts from inference, uses history only for the requested context, and makes no Vault changes.