菜单
Use when creating or modifying notes in a Knowlery-structured vault (formerly BYOAO). Enforces frontmatter requirements, wikilinks, and naming conventions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | vault-conventions |
| description | Use when creating or modifying notes in a Knowlery-structured vault (formerly BYOAO). Enforces frontmatter requirements, wikilinks, and naming conventions. |
You MUST follow these conventions when creating or modifying any note in this vault.
Before creating any note:
AGENTS.md — check the knowledge base structure (user notes vs agent-maintained pages)Projects/, Daily/); agent knowledge pages live only under entities/, concepts/, comparisons/, or queries/Choose the writing tool by the operation, not by whether Obsidian is running:
| Operation | Preferred tool | Why |
|---|---|---|
| New page with long or complex content (frontmatter + body, code blocks, quotes) | Write the .md file directly at the exact path | Obsidian indexes new files automatically; no shell escaping can corrupt content |
| Short new note, or appending a line or two | obsidian create path="dir/note.md" content="..." / obsidian append | Cheap when the content is small; \n escapes newlines |
| Rename / move an existing note | obsidian rename (Obsidian running) | The CLI rewrites wikilinks across the vault — the real graph-consistency win |
obsidian create passes content as one shell-quoted argument. Inside a
bash double-quoted string, backticks run as command substitution, $ expands,
and nested quotes end the argument — so a page containing a code fence or
quoted prose will usually break the command or corrupt the content. If
create fails once on content escaping, do not fight the shell: write the
file directly with identical frontmatter and naming conventions, then verify
with obsidian read (or knowlery health after bulk changes).
When you do use obsidian create, pass path="dir/note.md" — name=
resolves like a wikilink and lands in the default new-note location, not
necessarily the directory the page belongs in.
Treat any page containing frontmatter plus body, Mermaid or other charts, code
fences, tables, or quoted prose as a full page and write the .md file
directly.
In headless environments (Obsidian closed, CLI-initialized workspaces), write
.md files directly, and run knowlery health after bulk changes.
Dot-directories (.claude/, .knowlery/, .agents/) are outside
Obsidian's vault index. Obsidian CLI commands that depend on the vault index —
including read and create — cannot reach them even with path=; use
your file tools directly.
Claude Code and OpenCode load Knowlery rules through their platform
configuration at session start (.claude/CLAUDE.md imports /
opencode.json instructions). Codex does not automatically receive
per-vault rule contents; follow the workspace AGENTS.md and read the
relevant hidden rule files directly with your file tools.
Every note MUST have these fields:
| Field | Values |
|---|---|
title | Descriptive title |
type | meeting, idea, reference, daily, project, person, entity, concept, comparison, query, etc. |
date | YYYY-MM-DD — today's date or extracted from content |
tags | Array of relevant tags |
Additional fields (optional):
| Field | Purpose |
|---|---|
domain | Knowledge area (e.g. ai-agents, product-strategy) |
references | Related notes as wikilinks: [[Note Name]] |
status | draft, active, completed, archived |
updated | YYYY-MM-DD — last substantive edit (common on agent pages) |
contradictions | Cross-links when conflicting claims need review (agent pages) |
ALWAYS use wikilinks for:
[[Person Name]][[Project Name]][[Concept Name]][[Note Name]]Rules:
[[wikilinks]] for internal vault connections[text](url) for external URLs only[[Note Name#Heading]] for specific section links[[Note Name|Display Text]] for custom display textSCHEMA.md): lowercase with hyphens, no spaces
(response-time-metrics.md); one topic per file under entities/, concepts/,
comparisons/, or queries/YYYY-MM-DD format where applicableAfter creating or modifying a note, verify:
[[wikilinks]]Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
Open-ended Q&A against the knowledge base. Locates candidate pages with one call to the deterministic retrieval script (.knowlery/bin/query.mjs), then reads the promising ones with Obsidian CLI and synthesizes an evidence-based answer with citations. Use when the user asks questions about vault content like "what is X", "why did we decide Y", "explain Z", "what do my notes say about", "summarize what I know about", or any question that should be answered from accumulated knowledge rather than general training data.
Manage a Knowlery knowledge base from the command line with the standalone knowlery CLI — initialize and sync workspaces, run health checks, query knowledge, detect stale pages, and install, export, and review knowledge bundles. Use when the user asks to operate their knowledge base headlessly (without Obsidian), share knowledge as a bundle, install a bundle someone shared, or verify the workspace after bulk changes.
Work a Knowlery knowledge base through its MCP tools — choose the right tool for the job, run the capture-to-cook loop, and behave well while doing it. Use when Knowlery MCP tools (query, capture, stale, health, init_kb, register_kb, sync, list_kbs, list_bundles) are available in the session, especially in clients without a shell.
The core knowledge compilation skill. Reads raw notes and external sources, then distills them into structured, cross-referenced knowledge pages in entities/, concepts/, comparisons/, and queries/. Keeps SCHEMA.md tag and domain taxonomy in sync when new tags or domains appear. Use this skill whenever the user mentions compiling notes, digesting material, updating the knowledge base, running a cook cycle, or says anything like "process my notes", "compile this", "add this to the wiki", "what's new in my notes", or "update knowledge pages". Also activate when the user pastes external content and wants it integrated into the knowledge base.
Pressure-tests beliefs against vault evidence. Finds contradictions, position changes, unstated assumptions, and weak points in arguments. Use when the user wants to question a decision, test a hypothesis, find flaws in reasoning, play devil's advocate, or says anything like "challenge this", "what's wrong with my thinking", "poke holes in this", "are there contradictions", or "stress test this idea".