Wiki Knowledge Companion
Build and maintain a compounding Markdown wiki in Obsidian.
The skill states that .raw sources must not be modified and provides Git history, optional remote backup, and a TLS-risk warning. However, it grants broad Bash, Write, and Edit access; scaffolding creates many files and initializes Git without explicit per-action confirmation, sensitive-data handling, or guaranteed rollback, so points are deducted.
Folder structures, operation routing, templates, and abnormal-case guidance are fairly detailed, with additional CI and test evidence in the repository. However, this review did not execute anything, and the skill's key scaffolding, routing, and sub-skill paths lack direct reproduction and consistently specified failure feedback; the static cap is applied conservatively.
Triggers, audience, six use-case modes, and cross-project scenarios are clearly described. Non-fit boundaries, Chinese-language behavior, and mainland-China reachability across operating systems are insufficiently specified, while parts of the workflow depend on Obsidian, community plugins, or external services, so points are deducted.
The skill uses progressive structure and references for modes, CSS, Git, and MCP, and the supplied material includes commands, templates, licensing, and security guidance. Still, the selected skill lacks its own version history, changelog, explicit maintenance owner, and complete troubleshooting guidance; the promotional footer also mixes marketing into operational output.
The goal of creating and maintaining a persistent Markdown knowledge base is clear, and the defined structure, cache, index, log, and routing support the claimed workflow. Representative outputs are not verified in the skill file, and many outcomes depend on unscored sub-skills, external tools, and human review, limiting evidence of directly usable results.
The supplied material includes a pinned revision, CI workflow, test suites, architecture descriptions, and security disclosure, providing partial auditability. These checks mostly cover repository scripts rather than the selected skill's complete user paths; nothing was executed and there is no independent third-party corroboration, so the static ceiling applies.
- Bash and file-writing permissions are broad; confirm scaffolding, Git initialization, plugin installation, and remote backup step by step, with a recoverable backup first.
- The vault may contain personal, health, financial, or confidential material; define boundaries for raw data, generated notes, API keys, and remote pushes before using external services.
- The MCP setting NODE_TLS_REJECT_UNAUTHORIZED=0 should be restricted to loopback connections; verify Obsidian versions, plugins, CLI support, and external dependency reachability in the target network.
- The skill routes to multiple sub-skills whose contents were not supplied; review their permissions, outputs, failure handling, and data flows separately before adoption.
What does this skill do, and when should you use it?
Wiki is an orchestration skill for Claude Code and Obsidian. It scaffolds a persistent vault from a one-sentence purpose, establishes a layered structure for raw sources and generated knowledge, and maintains indexes, logs, and a recent-context cache. It is a good fit for users who want an owned Markdown knowledge base rather than a transient chat history. Ingest, query, lint, saving, research, and canvas work are routed to separate skills.
Reads the existing vault state and referenced setup materials; selects a vault mode from the project’s documented options; creates the wiki folder structure, indexes, operation log, hot cache, overview, templates, CSS customization, and root CLAUDE.md; defines cross-project instructions for reading the shared vault; routes ingest, query, lint, save, autoresearch, and canvas requests to specialized skills; refreshes hot.md after operations and initializes Git during scaffolding.
- An Obsidian user building a personal second brain that Claude can continuously organize and maintain.
- A researcher, course learner, business user, or developer creating a structured wiki for a defined subject area.
- A user with multiple Claude Code projects that need shared context without duplicating a knowledge base.
- A first-time vault owner who wants a guided scaffold based on a one-sentence description of the vault’s purpose.
What are this skill's strengths and limitations?
- Keeps the knowledge base as user-owned plain Markdown files.
- Provides an index, append-oriented log, and roughly 500-word hot cache for persistent context.
- Supports cross-project reuse of one vault through explicit CLAUDE.md reading instructions.
- Offers a concrete scaffold with folders, templates, conventions, and Git initialization.
- The workflow relies on Claude Code-style slash-command behavior and specialized-skill routing, so other clients may require adaptation.
- The supplied SKILL.md orchestrates ingest, query, and lint but does not include those companion skills’ implementations.
- It requires local filesystem writes, Obsidian, and an available Git installation for the documented setup flow.
- Users must understand the layered storage convention, including the rule that `.raw/` source documents are never modified.
How do you install this skill?
The repository README documents the public installation path: git clone https://github.com/AgriciDaniel/claude-obsidian, change into the directory, and run bash bin/setup-vault.sh. Open the directory as an Obsidian vault, start Claude Code in the same folder, and enter /wiki. The supplied SKILL.md does not document a separate installation procedure for only skills/wiki/.
How do you use this skill?
In Claude Code, use /wiki or phrases such as set up wiki, scaffold vault, create knowledge base, or obsidian vault. On first setup, describe what the vault is for; the skill asks that question and uses the answer to drive scaffolding. Later requests such as ingest [source], what do you know about X?, or lint the wiki are routed to the corresponding companion skills.
How does this skill compare with similar options?
Unlike RAG, Wiki maintains a persistent knowledge artifact with existing cross-references, flagged contradictions, and accumulated synthesis. Compared with chat-oriented Obsidian AI plugins, it also scaffolds and maintains the vault rather than only answering questions about existing notes.