AgriciDaniel/claude-obsidian / skills/wiki
wiki
VerifiedInitialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| references/coordination.md | markdown | 1.9 KB |
| references/css-snippets.md | markdown | 4.3 KB |
| references/dataview.md | markdown | 1.6 KB |
| references/frontmatter.md | markdown | 2.7 KB |
| references/git-setup.md | markdown | 2.5 KB |
| references/install-modes.md | markdown | 1.9 KB |
| references/knowledge-recipes.md | markdown | 3.3 KB |
| references/mcp-setup.md | markdown | 1.9 KB |
| references/model-guidance.md | markdown | 1.6 KB |
| references/modes.md | markdown | 3.1 KB |
| references/operation-transactions.md | markdown | 6.0 KB |
| references/plugins.md | markdown | 2.7 KB |
| references/provenance.md | markdown | 3.2 KB |
| references/rest-api.md | markdown | 1.4 KB |
references/mcp-setup.md
View on GitHub# External read transports
The portable baseline reads vault files directly. The official Obsidian CLI is
an optional read surface when runtime probing reports it usable. MCP servers and
REST plugins are optional third-party integrations, never prerequisites.
## Selection policy
1. Prefer direct filesystem reads for portability and least privilege.
2. Use the official Obsidian CLI read-only when `detect-transport.sh --peek`
reports it usable.
3. Consider an MCP or REST adapter only when the user needs a capability the
first two choices cannot provide and explicitly approves installation.
4. Keep all vault mutations in a claude-obsidian operation transaction. An
external transport must not bypass expected hashes, journaling, or recovery.
## Third-party review
Installation recipes, package names, flags, and permissions change. Consult the
adapter's current primary documentation before use, pin a reviewed version,
and verify publisher and source. Do not execute floating `latest` packages,
unverified downloads, or opaque install scripts from this reference.
For any adapter:
- grant access only to the selected vault;
- bind network listeners to loopback unless the user has designed and approved
authenticated remote access;
- keep tokens out of notes, shell history, logs, and repository files;
- preserve TLS verification rather than using global bypass environment flags;
- default to read-only and test with non-sensitive data;
- document what data can leave the machine and how to disable the adapter.
Loopback binding reduces exposure but does not make disabled certificate
verification or leaked bearer tokens safe.
## Verification
Report adapter readiness only after a harmless read probe succeeds. Binary or
configuration presence alone means `available`, not `verified`. If a probe
fails, fall back to filesystem reads without changing mutation semantics.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |