القائمة
Use when user says "research X", "what do my notes say about X", "co mam w notatkach o X". Synthesizes an answer from the vault citing wikilinks; offers to save substantial answers to `_outputs/answers/`.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when user says "export [[Note]] ...", "export
Use when user says "import <file.zip>", "zaimportuj paczkę", "import bundle/pack of notes". Imports a brain-pack zip (made by /export in another brain) into this vault - validates, triages collisions, places notes into this vault's taxonomy, stamps provenance, updates all 3 indexes, writes a report. At most 2 user prompts per run.
Use when user says "ingest", "process inbox", "przetworz nowe pliki", or when files appear in `content/_raw/inbox/`. Processes raw sources into wiki notes, handles intra-batch clustering with confirmation, updates all 3 indexes.
Use when user says "lint", "health check", "audit". Checks vault for missing frontmatter, broken wikilinks, orphans, stub notes, inconsistent tags, TODO markers, stale content; saves report to `_outputs/reports/`.
Read research outline, launch independent agent for each item for deep research. Disable task output.
Conduct preliminary research on a topic and generate research outline. For academic research, benchmark research, technology selection, etc.
| name | qa |
| description | Use when user says "research X", "what do my notes say about X", "co mam w notatkach o X". Synthesizes an answer from the vault citing wikilinks; offers to save substantial answers to `_outputs/answers/`. |
Trigger phrases: "research X", "what do my notes say about X", "co mam w notatkach o X". The user wants an answer drawn from existing vault content.
Read content/_indexes/vault-map.md → identify relevant folders and tags for the question.
Read matching sections of content/_indexes/catalog.md → identify candidate notes. Note each candidate's repo-root-relative file path (content/<TOPIC>/.../<Note>.md) from its catalog folder section — you'll need it for citations.
Read content/_indexes/graph.md for link chains starting from candidates.
Read the actual note files — only the ones identified, not the whole vault.
Synthesize the answer. Cite every vault-drawn claim as a markdown link, not a wikilink: [Note Title](<percent-encoded repo-root path>). Rules:
%20, ( → %28, ) → %29. An unencoded space or ) breaks the link.[Open Knowledge Format (OKF)](content/AI/KNOWLEDGE/INFO/Open%20Knowledge%20Format%20%28OKF%29.md)[[ ]] syntax and do NOT wrap the URL in quotes.Clearly distinguish wiki content from inference. Flag gaps where the vault has no coverage.
If the answer is substantial, offer the user three follow-ups:
content/_outputs/answers/YYYY-MM-DD_<topic>.md (type answer-note). Inside the saved vault note, cite with [[wikilinks]], not markdown links — wikilinks are the vault convention, render in Obsidian, and feed graph.md. The markdown-link form is for the chat answer only.compile skill.enhance skill.CLAUDE.md "Navigation Protocol" — read on every operation before this workflow.