# Obsidian Knowledge Base

> Use when the user explicitly asks to save, create, update, archive, or remember content in an Obsidian vault, to file or sort its Inbox, to check or audit the vault's health, or asks which parts of a conversation are worth capturing as durable knowledge. Conversation-harvest analysis and vault audits are read-only, and Inbox filing always shows a plan before it moves anything; never mutate the Va…

- **Type:** Skill
- **Install:** `agentstack add skill-spc-jgs-obsidian-kb-skill-qoderwork`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Spc-jgs](https://agentstack.voostack.com/s/spc-jgs)
- **Installs:** 0
- **Category:** [Productivity](https://agentstack.voostack.com/c/productivity)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Spc-jgs](https://github.com/Spc-jgs)
- **Source:** https://github.com/Spc-jgs/obsidian-kb-skill/tree/master/platforms/qoderwork

## Install

```sh
agentstack add skill-spc-jgs-obsidian-kb-skill-qoderwork
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Obsidian Personal Knowledge Base

## Overview

Agent-agnostic instructions to create, organize, and update notes in an Obsidian vault. Any tool that reads/writes local files can use it.

## DO NOT auto-save

This skill **never writes to the vault on its own**. Write only after **explicit save intent** ("save to Obsidian", "沉淀", "总结存档"). An explicit request to evaluate what from a conversation is worth capturing may run `conversation-harvest.md` as analysis only. For unrelated Q&A, debugging, or casual chat: do nothing.

## When the user asks to save or review capture candidates

1. **Route analysis before Vault discovery**: for an analysis-only conversation review, read `conversation-harvest.md`, return the candidate proposal, and stop without locating or scanning a Vault. Otherwise continue.
2. **Find vault for a write**: env `OBSIDIAN_KB_VAULT` → `~/.obsidian-kb-config` → ask. Refuse unless a real vault (`.obsidian/` + `Templates/`).
3. **Read the smallest operation-specific reference set before writing**. Read Vault governance first, then let one compact discovery call answer this: `required_references` names every file the selected type, template, and destination require, so read that set instead of discovering it one failure at a time. Pass the governed route as `--folder` — a crowded child folder does not make its parent look crowded. The full map:
   - New note: read only `note-creation.md`.
   - Finished source-backed article: after `note-creation.md` routes it, also read
     `web-capture.md`; verified captures additionally load `deep-capture.md`.
   - Crowded selected destination: when compact discovery reports it, also read
     `folder-routing.md`; uncrowded destinations do not load it.
   - Existing note: read only `update-note.md`.
   - Filing the Inbox: read only `process-inbox.md`. Filing moves notes the user
     already wrote; it never authors one, so `≤1 note written` does not bound it.
   - Conversation context archive: read `conversation-digest.md`.
   - Conversation knowledge review: read `conversation-harvest.md`; load
     `note-creation.md` only after one durable candidate is selected for writing.
   - Task Memory: read `task-memory.md` only after explicit opt-in (**off by default**).
   - YAML, rules, and Git references are troubleshooting or post-processing material: load `yaml-standards.md`, `rules-and-errors.md`, or `git.md` only when the current task requires it.
4. **Prefer bundled helpers** (never a one-off script): run `python /scripts/run_helper.py  ...`, where `` contains this `SKILL.md`. For new notes use `create-note --preflight-json`, inspect the structured validation, then apply with `--from-preflight  --apply --compact-json` instead of resending the body; `update-note` is only for Task Memory, while ordinary existing-note edits follow `update-note.md` with native file tools.
5. **Stay bounded**: ≤10 files scanned, ≤1 note written, ≤5 wikilinks. Never overwrite; add `-2` on name clash. Validate after.
6. **Route**: daily→`15-Daily` · meeting→`10-Work` · learning/article→`20-Learning` · insight/digest→`30-Insights` · project→`40-Projects` · person→`50-People` · quick/unread source→`00-Inbox`. An ordinary finished article uses standard capture; verified capture is explicit or evidence-sensitive.

## When the user asks to check or audit the Vault

Read only `audit-vault.md`. The audit is read-only and reports findings; it
never repairs a note. Fixing one is a separate request needing its own explicit
save intent — reporting a finding does not grant authority to act on it.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Spc-jgs](https://github.com/Spc-jgs)
- **Source:** [Spc-jgs/obsidian-kb-skill](https://github.com/Spc-jgs/obsidian-kb-skill)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-spc-jgs-obsidian-kb-skill-qoderwork
- Seller: https://agentstack.voostack.com/s/spc-jgs
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.