agentleFS
manazoid4manazoid4/maz-works-knowledge-vault/skills/wiki-cli/SKILL.md

wiki-cli

Skill0 starsChanged 3 months agoMITView on GitHub

Default vault-mutation transport for Maz Works Knowledge Vault. Wraps the Obsidian CLI as the preferred way to read, write, search, and modify vault notes from agents, with a direct-filesystem fallback. Triggers on: wiki-cli, obsidian cli, obsidian read, obsidian write, obsidian search, daily note, obsidian create, obsidian append, vault transport, transport detection.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When working on this skill, apply the 10-principle loop.

    line 165

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

wiki-cli: Default Transport Layer

Maz Works Knowledge Vault standardizes on the Obsidian CLI (shipped with Obsidian 1.12) as the preferred transport for vault mutations on desktop. This skill is the recipe reference for using it.

Substrate preference (v1.7+): This skill is a self-contained fallback. Prefer kepano/obsidian-skills (by Steph Ango, Obsidian CEO) as the authoritative substrate — its obsidian-cli skill is the canonical CLI reference for any Agent Skills runtime. If that separate skill is available, use it. The recipes below keep Maz Works Knowledge Vault functional when kepano's marketplace is not installed. Install kepano: claude plugin marketplace add kepano/obsidian-skills.


Why CLI over MCP

ConcernMCP (Options A/B)Obsidian CLI
InstallLocal REST API plugin + MCP server configBuilt into Obsidian 1.12+
AuthAPI key + TLS bypass (NODE_TLS_REJECT_UNAUTHORIZED=0)None — direct subprocess
LatencyHTTP round-trip per callIn-process binary
Failure modePlugin disabled → silent breakageBinary missing → loud command -v failure
ReentrancySelf-MCP-calls inside Claude session can deadlockPure subprocess, safe
Mobile / headlessLimitedLimited (CLI is desktop-only too)

CLI loses to MCP on exactly one axis: it only works on machines where Obsidian itself is installed. For headless servers and mobile, fall through to the next transport in the chain.


Detection

At session start (or vault setup), run:

bash scripts/detect-transport.sh

This writes .vault-meta/transport.json with the schema:

{
  "preferred": "cli",
  "fallback_chain": ["cli", "filesystem"],
  "available": {
    "cli": {"present": true, "binary": "obsidian-cli", "version_string": "..."},
    "filesystem": {"present": true},
    "mcp_obsidian": {"present": null, "detection": "deferred"},
    "mcpvault": {"present": null, "detection": "deferred"}
  }
}

Read this file before any non-trivial vault mutation. Skills that need to read or write should consult preferred and pick the corresponding transport. The decision tree lives at wiki/references/transport-fallback.md.

Refresh detection with --force after installing/removing the Obsidian CLI:

bash scripts/detect-transport.sh --force

Recipes (CLI-first; fallback noted inline)

Each recipe shows the CLI form first. If the CLI is unavailable per the detection snapshot, fall through to the noted fallback. Variable substitution: $VAULT is the absolute vault root; $NOTE is a vault-relative path like wiki/concepts/Foo.md.

Read a note

# CLI
obsidian-cli read "$VAULT" "$NOTE"

# Fallback: Claude's Read tool with absolute path
# Read $VAULT/$NOTE

Create or overwrite a note

# CLI
obsidian-cli write "$VAULT" "$NOTE" < /path/to/content.md

# Fallback: Claude's Write tool with absolute path
# Write $VAULT/$NOTE with the desired content string

Append to a note

# CLI
echo "additional content" | obsidian-cli append "$VAULT" "$NOTE"

# Fallback: Read $VAULT/$NOTE, append manually, Write back

Search note content (CLI uses Obsidian's own search ranking)

# CLI
obsidian-cli search "$VAULT" "<query>"

# Fallback: ripgrep
rg --type=md "<query>" "$VAULT/wiki/"

Today's daily note (if Daily Notes plugin is enabled)

# CLI
obsidian-cli daily:today "$VAULT"
obsidian-cli daily:append "$VAULT" "captured at $(date)"

# Fallback: compute path manually
NOTE="$VAULT/wiki/daily/$(date +%Y-%m-%d).md"

Patch a frontmatter property

# CLI
obsidian-cli property:set "$VAULT" "$NOTE" status "evergreen"

# Fallback: read frontmatter, parse, mutate, rewrite (use mcp__obsidian-vault__update_frontmatter if MCP is configured)

List backlinks for a page

# CLI
obsidian-cli backlinks "$VAULT" "$NOTE"

# Fallback: ripgrep for wikilink references
rg --type=md "\[\[$(basename "$NOTE" .md)" "$VAULT/wiki/"

Open a Bases (.base) file's resolved view

# CLI
obsidian-cli bases "$VAULT" "$NOTE"
# (returns the resolved row list; supplements obsidian-bases skill which handles the .base file's YAML)

# Fallback: read the .base file directly; no resolved-view available without Obsidian itself

Tags + bookmarks

obsidian-cli tags "$VAULT"
obsidian-cli bookmarks "$VAULT"

When CLI is NOT the right choice

  • Mobile (iOS Share extension): filesystem write into .raw/ is the only path; CLI is desktop-only.
  • CI / headless ingest jobs: filesystem with manual frontmatter parsing.
  • Cross-vault operations: CLI binds to one vault root per invocation; for federation, fall back to filesystem walks.
  • Live edits while Obsidian is mid-save: rare race; CLI handles it correctly but in pathological cases the v1.7 wiki-lock.sh advisory locks (see skills/wiki-fold/ and agents/wiki-ingest.md) should be acquired first.

Cross-reference

  • Decision tree: wiki/references/transport-fallback.md
  • Legacy MCP options (A/B/C/D): skills/wiki/references/mcp-setup.md
  • Concurrency policy (v1.7+): skills/wiki-ingest/SKILL.md §Concurrency
  • Detection script: scripts/detect-transport.sh

How to think (10-principle mapping)

When working on this skill, apply the 10-principle loop. See skills/think/SKILL.md for the canonical framework.

#PrincipleApplication here
1OBSERVE (ext)Detect which Obsidian CLI binaries are installed; check if Obsidian app is running. Read .vault-meta/transport.json if it exists.
2OBSERVE (int)Don't be biased toward filesystem fallback when CLI is actually available — verify auto-detection caught what's installed.
3LISTENIf manual_override: true is set in transport.json, the user has spoken — preserve their preferred and fallback_chain.
4THINKCompute the right fallback chain for this environment. CLI > MCP > filesystem; freshness check before recomputing.
5CONNECT (lat)How does this transport choice affect every other skill's write? Six downstream skills depend on this snapshot.
6CONNECT (sys)Schema stability of transport.json matters more than feature richness — consumers parse the JSON via simple shell idioms.
7FEELError message when no transport works should tell the user EXACTLY what to do (install CLI, configure MCP, etc.).
8ACCEPTFilesystem fallback is fine. Admit when CLI doesn't exist; don't fabricate a binary that isn't there.
9CREATEWrite transport.json atomically (temp + rename). Round-trip manual_override every cycle.
10GROWAs MCP support matures, auto-detection should cover the deferred tiers. Track that as v1.7.x scope.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.