agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/obsidian/SKILL.md

obsidian

Skill5 starsChanged 8 months agoMITView on GitHub

Create, search, read, and link notes in an Obsidian vault using direct markdown file access and the obsidian-cli. Use when user says "add to Obsidian", "find note in vault", "create Obsidian note", or "link notes".

  • Installs packages

101 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, discord-e2e and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • molt-botSkill

    discord-e2e

    Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.

    Also in 10 projects that use this

  • molt-botSkill

    openclaw-repair-sweep

    Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

    Also in 10 projects that use this

  • clawdbotSkill

    openclaw-performance

    Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.

    Also in 7 projects that use this

  • clawdbotSkill

    plugin-sdk-impact

    Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.

    Also in 7 projects that use this

  • hkyutongSkill

    node-connect

    Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

    Also in 18 projects that use this

  • +2 more from molt-bot

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 96 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Add to ~/.zshrc or ~/.bashrc for persistence.

    line 46
  2. Very specific:

    Always check that OBSIDIAN_VAULT is set: [ -z "$OBSIDIAN_VAULT" ] && echo "Not configured"

    line 126
  3. Very specific:

    If not set, ask the user for their vault path and suggest adding it to ~/.zshrc

    line 127
  4. Distinctive:

    Prefer direct file access over CLI tools for simple read/write operations

    line 128
  5. Distinctive:

    When creating notes, always use proper Markdown formatting with YAML frontmatter for tags/metadata

    line 129
  6. Very specific:

    When reading long notes (> 100 lines), display only the first 50 lines and save full content to workspace/

    line 130
  7. Very specific:

    Use Obsidian wikilink syntax [[Note Name]] for internal links, not regular markdown links

    line 131
  8. Distinctive:

    Keep responses concise: confirm file path and action in 1-2 lines

    line 134

“Common” is measured: kept by at least 6 in 10 of the 96 edited versions of this file we could read. “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

Obsidian

Manage Obsidian vaults via direct markdown file access and the obsidian-cli tool. Obsidian vaults are plain markdown files — most operations work without any special CLI.

Prerequisites

Option 1: Direct file access (no install needed) Obsidian vaults are directories of .md files. Read/write them directly with Bash.

Option 2: obsidian-cli for richer operations:

npm install -g obsidian-cli

Or using the community obsidian-export tool:

cargo install obsidian-export

Configure vault path:

export OBSIDIAN_VAULT="$HOME/Documents/ObsidianVault"

Add to ~/.zshrc or ~/.bashrc for persistence.

Commands

Direct File Operations (no CLI needed)

OperationCommand
List all notesfind "$OBSIDIAN_VAULT" -name "*.md" -type f
Search note contentgrep -r "<query>" "$OBSIDIAN_VAULT" --include="*.md" -l
Read a notecat "$OBSIDIAN_VAULT/<Note Name>.md"
Create a noteWrite to "$OBSIDIAN_VAULT/<Note Name>.md"
Append to noteecho "\n<content>" >> "$OBSIDIAN_VAULT/<Note Name>.md"
List by folderls "$OBSIDIAN_VAULT/<Folder>/"

Wikilinks (Obsidian's link format)

[[Note Name]]                  ← Link to another note
[[Note Name|Display Text]]     ← Link with custom text
[[Note Name#Heading]]          ← Link to a heading

Frontmatter (YAML metadata)

---
tags: [project, meeting]
date: 2026-03-21
aliases: [alternative name]
---

Daily Notes

# Create or open today's daily note
TODAY=$(date +%Y-%m-%d)
NOTE_PATH="$OBSIDIAN_VAULT/Daily Notes/$TODAY.md"

Usage Examples

Create a new note with frontmatter:

cat > "$OBSIDIAN_VAULT/Projects/New Idea.md" << 'EOF'
---
tags: [idea, project]
date: 2026-03-21
---

# New Idea

## Summary
Brief description here.

## Links
- [[Related Note]]
EOF

Search vault for a topic:

grep -r "machine learning" "$OBSIDIAN_VAULT" --include="*.md" -l

Append to an existing note:

echo "\n\n## Update 2026-03-21\nNew information here." >> "$OBSIDIAN_VAULT/Projects/New Idea.md"

Find all notes tagged with "meeting":

grep -r "tags:.*meeting" "$OBSIDIAN_VAULT" --include="*.md" -l

List all notes in a folder:

ls "$OBSIDIAN_VAULT/Projects/"

Rules

  • Always check that OBSIDIAN_VAULT is set: [ -z "$OBSIDIAN_VAULT" ] && echo "Not configured"
  • If not set, ask the user for their vault path and suggest adding it to ~/.zshrc
  • Prefer direct file access over CLI tools for simple read/write operations
  • When creating notes, always use proper Markdown formatting with YAML frontmatter for tags/metadata
  • When reading long notes (> 100 lines), display only the first 50 lines and save full content to workspace/
  • Use Obsidian wikilink syntax [[Note Name]] for internal links, not regular markdown links
  • Preserve existing frontmatter when appending to notes — read the file first
  • File names should match Obsidian conventions: avoid special characters except - and _
  • Keep responses concise: confirm file path and action in 1-2 lines

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.