agentleFS
tboome33tboome33/obsidian-mcp-router/skills/read-get/SKILL.md

read-get

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Read the full content of a file from a vault (markdown + frontmatter).

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Call the obsidian-router get_file MCP tool with arguments parsed from $ARGUMENTS.

    line 16
  2. Distinctive:

    if user just says "the daily note" or similar without a clear path, ask for the path

    line 31
  3. Very specific:

    If path is missing, refuse to call the tool and ask the user for it.

    line 33

≈ “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

read-get

Call the obsidian-router get_file MCP tool with arguments parsed from $ARGUMENTS.

Arguments

Required:

  • path — file path relative to vault root (e.g. Sessions/2026-05-02.md).

Optional:

  • vault — vault name. If omitted, the router uses its default vault.

Argument parsing from $ARGUMENTS

  • bare path → path
  • <vault>/<path> if first segment matches a known vault name → split into vault + path
  • vault=X path=Y (key=value)
  • if user just says "the daily note" or similar without a clear path, ask for the path

If path is missing, refuse to call the tool and ask the user for it.

Output format

After fetching, render the markdown content. If the file has frontmatter, format it as a YAML code block at the top followed by the body. Don't truncate unless the file is huge (>2000 lines), in which case show the first 200 lines and offer to fetch more on request.

contentSha256 (for conditional writes)

The result also carries contentSha256 — a fingerprint of the file's current content. If you intend to modify the file after reading it, keep this value: pass it back as ifMatch on the subsequent write_file / patch_file / merge_frontmatter / move_file / delete_file so the change is refused if the file was modified in between. This is how you avoid overwriting a concurrent edit. Don't surface the hash to the user unless asked — it's plumbing.

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.