clarila-obsidian
Retrieve and maintain Clarila canonical Obsidian notes, sources, topics and reusable answers. Use for the actual Obsidian workspace, not as a generic research or procedure-activation skill.
SKILL.mdclarila-obsidian/SKILL.md
GitHubMaintain the canonical knowledge
Read the shared workflow contract before substantive work. This skill is part of the locally installed Clarila suite. Its source is in ~/Developer/skills; resolve sibling skills relative to this directory.
Procedure
- Resolve the configured local vault, read Wiki Schema and the content index, then query for existing relevant notes before writing.
- Read only relevant pages and primary evidence. Check dates/status and distinguish observed facts, policy and inference. Private email/calendar contents and credentials stay outside shared knowledge.
- Update existing source cards/topics/answers with citations and explicit uncertainty. Preserve originals and human edits; compare the current SHA before replacement.
- Prepare the factual proposal with native file tools, then use the bundled Go maintenance helper for plan/apply/update and discovery checks. It preserves Wiki Schema content, provenance, current-SHA checks, atomic replacement, shared locking, index and log receipts without the retired runtime's writer. Check note, log and each generated index outcome separately. If actual file access or permission is unavailable, retain a complete draft and the exact prerequisite. Never change protected policy or claim a draft was saved.
- Do not duplicate operating instructions into another authoritative copy. A factual note never grants task authority or activates a procedure; send learning proposals to clarila-learn.
Preserve the note's identity
Resolve existing notes through the vault's current path, aliases, properties and source identity before choosing an update target. Follow the vault's established internal-link syntax and metadata schema. Check affected links and required properties after a real save.
If the note changed after the recorded read, inspect the new content and merge the factual addition with current human edits, or retain a complete draft when the conflict cannot be resolved. Read back the saved content/hash, then update the required index and activity record. Report those actual file outcomes and any remaining semantic review.
Synchronization and handoff
Resolve the same issue/workspace/session association before substantive work, including direct invocation. Read and update the private handoff described in the shared contract using available native file tools. Record the actual stage, source, findings, evidence, outcome and next action. If no native session identity is available, retain an unbound record.
Deliverable
Return relevant cited knowledge or confirmed note updates, hashes, lint results and factual review limits.
Load only the relevant specialist from the catalog. Missing tools change the available evidence, never its meaning.
Read the operation-specific reference when performing this responsibility.