بنقرة واحدة
vault-search
Search the vault by tag, MOC, note type, or relationship — structured queries that understand frontmatter
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Search the vault by tag, MOC, note type, or relationship — structured queries that understand frontmatter
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze the current or a past Claude Code session to extract knowledge worth persisting to the vault. Proposes items, you pick, it writes them to the right place. This skill activates when you say capture this session, what should we save, what did we learn, or at end-of-session when valuable knowledge was generated.
One-time setup wizard — personalize the vault with your name, domains, and preferences
Hands-on guided tour of the vault — learn by doing with real examples
Migrate content from staging, chunk large files, and handle bulk note reorganization
Transform and organize notes in the Obsidian vault — add frontmatter, detect note types, create relationships
Extract URL content and create literature notes and review notes from web articles
| name | vault-search |
| description | Search the vault by tag, MOC, note type, or relationship — structured queries that understand frontmatter |
| activation | ["vault search","find notes","search vault","search by tag","search by type","notes under","notes tagged","find orphans","what's under","what's in"] |
Structured search that understands frontmatter, MOC hierarchy, and vault conventions. Use this instead of raw grep when the user wants to find notes by their organizational properties.
For content-level search (finding text within notes), regular grep is fine. This skill is for structural queries.
"find all notes tagged practitioner"
# Search in frontmatter tags lists
grep pattern: "^ - practitioner$" across all *.md files
# OR in single-line tags
grep pattern: "^tags:.*practitioner"
ml) and search for both"what notes are under Machine Learning?"
grep pattern: 'up: "\[\[Machine Learning\]\]"' across all *.md files
up: points to a child of the target MOC)"show all review notes"
grep pattern: "^type: review$" across all *.md files
"find notes with no up: link"
type: frontmatter propertyup: property"find practitioner notes under Machine Learning"
up: "[[Machine Learning]]")practitioner in their tags:)"what notes are related to X?"
"[[X]]" in related: frontmatter sectionsup: "[[X]]" (children)source: "[[X]]" (sourced from)[[X]] in body text (unlinked mentions)"find all draft notes" or "show high-quality resources"
grep pattern: "^ - draft$" across all *.md files
draft, practitioner, high-quality*.md files in vault rootAlways return results as a markdown table:
| File | Type | Parent | Tags |
|---|---|---|---|
| Note Name | atomic | Machine Learning | ml, practitioner |
Include a count summary: "Found 12 notes matching query."
For large result sets (20+), group by parent MOC:
| File | Type | Tags | ...
| File | Type | Tags | ...
ml (canonical form of machine-learning)"Vault Index.md for the full tag census if the user wants to explore available tags