agentleFS
maroffomaroffo/claude-forge/skills/obsidian/SKILL.md

obsidian

Skill17 starsChanged 51 days agoMITView on GitHub

Obsidian vault operations via CLI. Use for note management, search, daily notes, knowledge graph analysis, tasks, properties.

96 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 10 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

  • emanueleieloSkill

    sonos

    Control Sonos speakers: discover, play/pause, volume, grouping, favorites, and queue management via sonos CLI.

    Also in 5 projects that use this

  • +2 more from molt-bot

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 91 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Note CRUD: create, read, append, prepend, move, delete

    line 17
  2. Distinctive:

    Daily Notes: read, append, prepend to today's note

    line 19
  3. Distinctive:

    When the Obsidian CLI is unavailable (app not running, CLI errors, tool not found), access vault markdown files directly.

    line 71
  4. Very specific:

    Use Read/Write/Edit/Glob/Grep tools on .md files in the vault path

    line 75
  5. Very specific:

    Search: use Grep on vault path instead of obsidian search

    line 79
  6. Very specific:

    Always use silent flag for create/append when user doesn't need the note opened

    line 84
  7. Very specific:

    Prefer file=<name> (wikilink resolution) over path= for convenience

    line 85

“Common” is measured: kept by at least 6 in 10 of the 91 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

ABOUTME: Obsidian vault management via official CLI (1.12+)

ABOUTME: CRUD, search, daily notes, tags, properties, graph analysis, tasks, templates

Obsidian Vault Operations

CLI reference: See ../_OBSIDIAN.md for full command reference. Integration: See ../_SECOND_BRAIN.md for category routing when adding knowledge.

Capabilities

  1. Note CRUD: create, read, append, prepend, move, delete
  2. Search: full-text with folder filtering, JSON output
  3. Daily Notes: read, append, prepend to today's note
  4. Tags & Properties: list, set, read, remove frontmatter properties and tags
  5. Knowledge Graph: backlinks, outgoing links, orphans, dead-ends, unresolved links
  6. Tasks: list, toggle, mark done/todo across vault or daily note
  7. Templates: list, read (with variable resolution), create from template
  8. History: diff versions, restore from file recovery or sync

Common Workflows

Quick capture to daily note

obsidian daily:append content="- [ ] <task or note>" silent

Find related notes

obsidian backlinks file=<name> counts
obsidian links file=<name>

Vault health check

obsidian orphans total
obsidian deadends total
obsidian unresolved verbose

Search and read

obsidian search query="<term>" matches limit=10
obsidian read file=<result>

Add knowledge to Second Brain

# 1. Read existing content to check for duplicates
obsidian read file="Second Brain - <Topic>"
# 2. Append extracted content (follow _SECOND_BRAIN.md template)
obsidian append file="Second Brain - <Topic>" content="<extracted>"
# 3. Update timeline
obsidian append file="Second Brain - Timeline" content="- **YYYY-MM-DD** | [Topic] | Source: ..."

Onboard project to vault

# Run the project onboarding protocol from _VAULT_CONTEXT.md
# Detects project info from CLAUDE.md, creates Overview/Log/Solutions, registers in MOC
# See _VAULT_CONTEXT.md "Project Onboarding" for full steps

Fallback: Direct File Access

When the Obsidian CLI is unavailable (app not running, CLI errors, tool not found), access vault markdown files directly.

Vault path: '/Users/maroffo/Library/Mobile Documents/iCloud~md~obsidian/Documents'

  • Use Read/Write/Edit/Glob/Grep tools on .md files in the vault path
  • Note names map to <vault>/<note name>.md (subfolders for organized notes)
  • Frontmatter is standard YAML between --- delimiters
  • Daily notes: <vault>/Daily Notes/YYYY-MM-DD.md
  • Search: use Grep on vault path instead of obsidian search
  • Append: use Edit tool to add content at end of file

Rules

  • Always use silent flag for create/append when user doesn't need the note opened
  • Prefer file=<name> (wikilink resolution) over path= for convenience
  • For Second Brain operations, follow ../_SECOND_BRAIN.md routing
  • Multiline content: use \n for newlines in content strings
  • CLI first, direct file access as fallback. Try CLI; on failure, switch to direct access silently.

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.