菜单
Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when investigating an agent-harness CLI's internals (Claude Code, codex, opencode, or similar): extracting the system prompt or tool descriptions, finding what code path produces a specific UI message, decoding minified function names or Rust symbols, understanding undocumented config keys, or otherwise spelunking a shipped binary (or its pinned source) to figure out how the tool actually behaves.
Use when about to lock in a non-trivial or hard-to-reverse decision, fire AskUserQuestion to offload a call, proceed on your own preferred option, or assert something is done / found / tested / fixed / "that's how it works" — especially when the basis is memory, the handoff, the first framing, or an unchecked assumption rather than something verified this session. Also invoked as /gut-check. Use even when you feel confident; confidence is the symptom, not the all-clear.
Analyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.
Diagnose and fix LSP setup for the current project's detected ecosystems (Rust, TypeScript, Ruby). Use when the SessionStart hook nudged about a missing LSP plugin, when the env isn't ready (no `bundle install`, no `cargo build`, missing server binary), when LSP calls are failing, or when the user invokes `/actually-lsp-doctor` directly. Walks the per-ecosystem state machine, reports what's missing, then runs the fix.
Use when structuring prose so readers can skim it - drafting or restructuring READMEs, docs, PR or issue bodies, design docs, RFCs, or any long-form text where a wall of prose hides the structure. Also use when explicitly asked to make something scannable or skimmable, convert prose to a list, surface a buried list, fix a wall of text, or decide whether bullets or prose fit. Strong signal: text with parallel sentence shapes, contrast markers ("that's distinct from", "versus"), bolded terms followed by colons, or an embedded "X, Y, and Z" series. Composes with prose-clarity skills (concision) and voice skills (personality) rather than replacing them. Skip for source code and for casual one-line replies where formatting reads as overkill.
Ignore actually-lsp nudges for an ecosystem in this project. Use when the user wants to silence, dismiss, or ignore the LSP setup nudges for a specific ecosystem (Rust, TypeScript, Ruby), or invokes `/actually-lsp-ignore` directly. Writes `dismissed=true` to `.claude/actually-lsp.json`. Persistent across sessions for this project only.
基于 SOC 职业分类
| name | obsidian |
| description | Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown. |
Tool-specific mechanics for working with Obsidian vaults.
A directory is an Obsidian vault if it contains .obsidian/ folder.
Syntax: [[Note Title]] or [[path/Note Title]]
[[Note Title|display text]]Obsidian stores settings in .obsidian/ at vault root:
| File | Purpose |
|---|---|
daily-notes.json | Daily note folder and template |
templates.json | Templates folder location |
zk-prefixer.json | Zettelkasten/inbox settings |
app.json | General settings (new file location, attachments) |
plugins/ | Installed plugin data |
// daily-notes.json
{
"folder": "Fleeting",
"template": "Templates/daily"
}
// templates.json
{"folder": "Templates"}
// zk-prefixer.json
{
"folder": "📫 Inbox",
"template": "Templates/frontmatter"
}
// app.json
{
"newFileFolderPath": "📫 Inbox",
"attachmentFolderPath": "🖇 Attachments"
}
Finding today's note:
.obsidian/daily-notes.json for folderYYYY-MM-DD.md (Obsidian default){folder}/{YYYY-MM-DD}.mdTemplate application:
daily-notes.jsonIf Glossary.md exists at vault root:
Vaults should have a CLAUDE.md at root describing:
See templates/vault-claude-md.md for template.
When a vault has areas with semantic overlap (e.g., "tool sharpening" vs "software engineering"), the vault CLAUDE.md can include ### Disambiguation: sections that guide routing decisions.
The routing algorithm checks for:
See references/routing.md for the full disambiguation format and how to build custom rules.
For methodology (tool-agnostic):
references/para.md - PARA organizational systemreferences/zettelkasten.md - Naming conventionsreferences/note-patterns.md - Note templatesreferences/routing.md - Routing algorithm with disambiguation supportreferences/daily-linking.md - Linking captured notes to daily notereferences/pipeline.md - Processing pipeline stages and status flowreferences/routing-memory.md - Routing correction and learning loop