@qiqiangvae/dsh-obsidian 0.1.0

package/skills/obsidian-cli/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: obsidian-cli
+description: Interact with a running Obsidian instance through its CLI: read, create, search, manage notes/tasks/properties, and dev-loop plugins/themes. Use when the user asks to control Obsidian from the terminal or to debug an Obsidian plugin.
+---
+
+# obsidian-cli
+
+Talk to a running Obsidian instance. Requires Obsidian to be open and CLI
+enabled (Settings → General → Enable CLI).
+
+## Common commands
+
+```bash
+obsidian read file="My Note"
+obsidian create name="New Note" content="# Hello" template="Template" silent
+obsidian append file="My Note" content="New line"
+obsidian search query="search term" limit=10
+obsidian daily:read
+obsidian daily:append content="- [ ] New task"
+obsidian property:set name="status" value="done" file="My Note"
+obsidian tasks daily todo
+obsidian tags sort=count counts
+obsidian backlinks file="My Note"
+```
+
+- Use `file=<name>` for wikilink-style targeting; `path=<path>` for exact.
+- Use `vault=<name>` first to disambiguate when more than one vault is open.
+- Pass `--copy` to put the result on the clipboard.
+
+## Plugin / theme dev loop
+
+```bash
+obsidian plugin:reload id=my-plugin
+obsidian dev:errors
+obsidian dev:screenshot path=screenshot.png
+obsidian dev:dom selector=".workspace-leaf" text
+obsidian dev:console level=error
+obsidian eval code="app.vault.getFiles().length"
+```
+
+1. Reload → 2. Check errors → 3. Verify visually → 4. Check console → loop.

package/skills/obsidian-markdown/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: obsidian-markdown
+description: Create and edit Obsidian Flavored Markdown (.md) with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Always-on reference for any markdown the agent writes into the vault.
+---
+
+# obsidian-markdown
+
+Use Obsidian Flavored Markdown (OFM), not generic Markdown.
+
+## Wikilinks
+
+```
+[[Page Name]]                  → link
+[[Page Name|alias]]            → link with custom text
+[[Page Name#Heading]]          → link to a heading
+![[Page Name]]                 → embed (transclude) the page
+![[Page Name#Heading]]         → embed a section
+```
+
+## Properties (YAML frontmatter)
+
+```yaml
+---
+title: My Note
+type: resource
+tags: [rust, async, ownership]
+created: 2026-08-29
+updated: 2026-08-29
+source: https://example.com/article
+source_hash: a1b2c3...
+aliases: [Note Alias]
+status: seedling
+---
+```
+
+- `type` — required, drives folder routing (see wiki skill)
+- `created` — set once, never overwrite
+- `updated` — set on every write
+- `source` / `source_hash` — provenance for ingested content
+
+## Callouts
+
+```markdown
+> [!note]
+> Plain callout body.
+
+> [!warning] Optional title
+> Body with a title.
+
+> [!quote] Title
+> For quoted material with attribution.
+```
+
+Other useful types: `tip`, `info`, `example`, `question`, `success`, `failure`, `danger`, `bug`.
+
+## Standard markdown
+
+Headings, lists, tables, code blocks, links, blockquotes, images: standard
+CommonMark works. Do not re-introduce it from scratch in a skill body.

package/skills/save/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: save
+description: File conversation insights back into the vault as new pages or annotations. Trigger when the user says "save this", "remember this insight", or "add this to my notes" during a conversation.
+---
+
+# save
+
+Persist a conversational insight to the vault.
+
+## When to use
+
+- "Save this insight to my notes"
+- "Add a note about this conversation"
+- "I want to remember that…"
+
+## Workflow
+
+1. **Identify the type**: is this a resource (a fact / concept), a project
+   note (a decision or status), or a source (something external)?
+2. **Pick or draft a title**: prefer an existing `[[title]]` if the topic
+   is in the vault. Otherwise draft a short noun phrase.
+3. **Body**: keep it tight. If the user said something quotable, use a
+   `> quote` block with `**Source:** conversation, YYYY-MM-DD`.
+4. **Write** via `wiki_write`. Pass `source_path: "conversation"` to record
+   provenance without a real file hash.
+5. **Confirm** with the user, including the resolved path and the master
+   index entry that was added.
+
+## Don't
+
+- Do not save without explicit consent ("save this", "remember this",
+  "add a note"). A "huh, interesting" is not consent.
+- Do not duplicate an existing page without checking. `wiki_query` first.

package/skills/think/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: think
+description: The 10-principle reasoning loop (OBSERVE → ORIENT → DECIDE → ACT → REVIEW) that every other wiki skill maps onto. Use when the user asks for careful reasoning, a multi-step plan, or a structured decision.
+---
+
+# think
+
+A 10-step reasoning loop. Use it before any non-trivial operation.
+
+## The 10 principles
+
+1. **OBSERVE** — what is the actual state? (read tools, don't assume)
+2. **ORIENT** — what is the goal? what is the gap?
+3. **DECIDE** — pick the smallest reversible action
+4. **ACT** — do it (call the right tool)
+5. **REVIEW** — did it work? what changed?
+6. **REPORT** — tell the user what happened, with citations
+7. **REFLECT** — was there a better way? log it for next time
+8. **PRESERVE** — if there's a new insight, save it (the `save` skill)
+9. **RECORD** — append to the log via `wiki/log.md` (the tool does this)
+10. **REST** — stop. Don't loop. Cap at 3-5 tool calls per turn.
+
+## When to use
+
+- "Help me think through this"
+- Before any `wiki_write` or `wiki_rename` that touches more than one page
+- When the user is about to make a destructive change

package/skills/wiki/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: wiki
+description: Scaffold a new vault, manage wiki/ folders, and handle cross-project referencing. Trigger when the user asks to set up an Obsidian vault, create a wiki structure, or reference notes across projects.
+---
+
+# wiki
+
+Scaffold and maintain the LLM Wiki pattern layout in an Obsidian vault.
+
+## When to use
+
+- "Set up a new vault" / "scaffold my Obsidian" / "init a wiki here"
+- "Where should I put this note?" / "move this to the right folder"
+- "List my wiki structure"
+
+## Operations
+
+### SCAFFOLD (dry-run by default)
+
+Call the `wiki_scaffold` tool with `{ template: "default", apply: false }` to preview.
+Pass `apply: true` to write the layout. Typical new vault: `apply: true`.
+
+### TYPE ROUTING
+
+| Type      | Folder (default)   |
+| --------- | ------------------ |
+| `domain`  | `wiki/areas`       |
+| `area`    | `wiki/areas`       |
+| `project` | `wiki/projects`    |
+| `resource`| `wiki/resources`   |
+| `source`  | `wiki/sources`     |
+| `archive` | `wiki/archive`     |
+
+Override per-vault by setting `config.typeFolders` in your profile.
+
+### CROSS-PROJECT REFERENCING
+
+The vault is host-local user data outside any session workspace. Pages link
+by `[[bare title]]`, which resolves vault-wide via `wiki_query`.
+
+## Don't
+
+- Do not write to `wiki/meta/` directly; tools manage that directory.
+- Do not rename `index.md`, `hot.md`, or `log.md`; tools depend on them.
+- Do not put page content in `inbox/`; that is for raw sources only.

package/skills/wiki-ingest/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: wiki-ingest
+description: Ingest a source (URL, file, or pasted text) into the vault: extract entities and concepts, cross-reference existing notes, log the operation. Trigger when the user says "save this to my vault", "ingest this article", or "capture this".
+---
+
+# wiki-ingest
+
+Ingest external sources into the vault as first-class wiki pages.
+
+## When to use
+
+- "Save this article to my vault" / "ingest this URL"
+- "Capture these notes" / "add this to my second brain"
+- Pasted text + "remember this"
+
+## Workflow
+
+1. **Plan**: parse the source into one or more wiki pages. Pick a `type`
+   per page (resource/source/project/etc.). Avoid putting a single source
+   into multiple pages unless the user asked for a split.
+2. **Pre-flight check**: call `wiki_query` with the source's main topics to
+   find existing notes. Plan links from the new page to those notes.
+3. **Write**: for each page, call `wiki_write` with:
+   - `title` — short noun phrase, becomes the filename
+   - `type` — pick from the wiki SKILL routing table
+   - `content` — markdown body with `[[wikilinks]]` to existing pages
+   - `source_path` — the local path or `inbox/` file; SHA-256 is recorded
+   - `tags` — 2-5 lower-case tags
+4. **Acknowledge unresolved links**: `wiki_write` returns
+   `unresolvedLinks`. Tell the user about any forward links and, if
+   reasonable, draft placeholder pages in a second pass.
+5. **Log the operation**: the tool appends to `wiki/log.md` automatically.
+
+## Don't
+
+- Do not write to `wiki/` directly. Always go through `wiki_write`.
+- Do not paraphrase a source as if it were original work; copy quotes with
+  a clear `> quote` block and a `source:` frontmatter entry.
+- Do not invent claims or page numbers. If the source doesn't say it,
+  don't write it.

package/skills/wiki-lint/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: wiki-lint
+description: Vault health check. Use to find orphan notes, dead wikilinks, missing frontmatter, empty sections, and stale index/hot entries. The result is written to wiki/meta/Lint Report <date>.md.
+---
+
+# wiki-lint
+
+Audit the vault for structural rot.
+
+## When to use
+
+- "Check my vault health" / "lint my vault"
+- Before a major rewrite or migration
+- After a bulk import
+
+## Workflow
+
+1. Call `wiki_lint`. It returns a structured report and writes a copy to
+   `wiki/meta/Lint Report YYYY-MM-DD.md`.
+2. Group the issues by category. The categories the linter checks:
+   - `duplicate-filename` (error)
+   - `dead-link` (warn)
+   - `frontmatter` (warn / info)
+   - `empty-section` (info)
+   - `orphan` (info)
+   - `stale-index` (info)
+   - `stale-hot` (info)
+3. For each error, propose a fix using `wiki_write` / `wiki_rename`. Do
+   not auto-fix without user consent.
+4. Re-run `wiki_lint` to confirm issues are resolved.
+
+## Don't
+
+- Do not mass-rename pages. Each `wiki_rename` is a separate confirmation.
+- Do not delete orphan pages without checking with the user.
+- Do not modify `wiki/meta/Lint Report …` files; they are machinery.

package/skills/wiki-query/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: wiki-query
+description: Answer a question by reading the vault: search via BM25, follow the link graph, return citations with source locators. Trigger when the user asks "what's in my vault about X", "do I have notes on Y", or wants a synthesis of existing pages.
+---
+
+# wiki-query
+
+Answer from the vault with citations.
+
+## When to use
+
+- "What's in my vault about Rust async?"
+- "Do I have notes on Karpathy's LLM Wiki pattern?"
+- "Summarize what I know about topic X"
+
+## Workflow
+
+1. **Quick check first**: call `wiki_query` in `mode: "quick"` to read
+   `hot.md` + `index.md` verbatim — this is the model's recent context
+   and the master index. Often enough to answer the question.
+2. **Full search**: if not enough, call `wiki_query` in `mode: "standard"`
+   (default) with the user's question. Get top-N hits with snippets and
+   the inbound/outbound link graph.
+3. **Follow links**: if a top hit looks promising, call `wiki_query` again
+   on the top hit's outbound titles to expand the context. Up to 2 hops.
+4. **Synthesize**: write the answer with explicit `[[wikilink]]` citations.
+   Quote verbatim where useful; never invent.
+
+## Don't
+
+- Do not answer from prior knowledge alone if the vault is the source of
+  truth for this question. Always cite the page.
+- Do not loop indefinitely. Cap at 3-5 `wiki_query` calls per turn.
+- Do not return more than ~6 hits to the user; summarize instead.