Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计通过

obsidian-restObsidian rest 搜索

Agent Skill

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

总安装

3,725

周安装

160

GitHub Stars

公开资料未说明

下载量

1,306
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:obsidian-rest(Obsidian rest 搜索)
来源仓库:https://github.com/nj070574-gif/obsidian-rest
安装命令:
openclaw skills install obsidian-rest
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install obsidian-rest

简介

通过 Windows、macOS 或 Linux 上的本地 REST API 读取、写入、搜索、附加、修补和管理任何 Obsidian 保管库中的注释。

SKILL.md

name
obsidian-rest
description
Read, write, search, create, append, patch, and manage notes in any Obsidian vault via the Local REST API plugin (Windows, macOS, or Linux). Use when asked to save notes, find information, read a document, append to a file, search the vault, write a runbook, update documentation, or manage Obsidian content. Triggers: "save this to Obsidian", "note this", "add to obsidian", "read my note on X", "find in obsidian", "update the runbook", "what did I save about X", "list my vault", "create a note", "append to", "sv".
homepage
https://github.com/nj070574-gif/openclaw-obsidian-vault-skill
metadata

Obsidian Local REST API Skill

Control any Obsidian vault from OpenClaw using the Local REST API plugin. Works on any OS where Obsidian Desktop runs (Windows, macOS, Linux). No extra CLI tools needed — just curl.


Critical: Known Pitfalls (Read First)

These issues were discovered in real-world use and will cause silent failures if ignored:

1. Trailing slashes are mandatory on directory paths

The API returns {"message":"Not Found","errorCode":40400} if you omit trailing slashes on directory endpoints.

PathResult
$OBSIDIAN_URL/vault/✅ Correct — lists vault root
$OBSIDIAN_URL/vault❌ 40400 error
$OBSIDIAN_URL/vault/My%20Folder/✅ Correct — lists subfolder
$OBSIDIAN_URL/vault/My%20Folder❌ 40400 error

2. The root health check endpoint is / — nothing else

There is no /api/, /api/healthz, /healthz, /status, or /health endpoint.

PathResult
$OBSIDIAN_URL/✅ Returns plugin status JSON
$OBSIDIAN_URL/api/❌ 40400 error
$OBSIDIAN_URL/api/healthz❌ 40400 error

3. Shell variable expansion may fail in exec contexts

$OBSIDIAN_URL and $OBSIDIAN_API_KEY are available in the gateway process but child shells spawned by the exec tool may not inherit them depending on your OpenClaw configuration. Always test variable expansion before using them in curl:

echo "URL=$OBSIDIAN_URL KEY_LEN=${#OBSIDIAN_API_KEY}"

If either is empty, use hardcoded values in your curl commands for this session.

4. Never dump raw JSON to the user

Always interpret API responses and reply in plain English. See the Output Formatting section.


Prerequisites

  1. Obsidian Desktop installed and running with a vault open.
  2. Local REST API plugin installed and enabled in Obsidian:

- Open Obsidian → Settings → Community plugins → Browse → search "Local REST API" → Install → Enable.

  1. API Key copied from: Settings → Local REST API → API Key.
  2. Port noted (default: 27124). HTTPS is strongly recommended.
  3. Env vars set in your OpenClaw service (see Setup below).

Setup

1. Add env vars to your OpenClaw systemd service

sudo nano /etc/systemd/system/openclaw.service

Add these two lines in the [Service] block:

Environment=OBSIDIAN_URL=https://YOUR_OBSIDIAN_HOST:27124
Environment=OBSIDIAN_API_KEY=your_api_key_here

Then reload and restart:

sudo systemctl daemon-reload
sudo systemctl restart openclaw.service

2. Verify env vars are live in the gateway process

PID=$(pgrep -f "openclaw-gateway" | head -1)
cat /proc/$PID/environ | tr "\0" "\
" | grep "^OBSIDIAN"

Both OBSIDIAN_URL and OBSIDIAN_API_KEY should appear with correct values.

3. Test the connection

curl -sk \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  "$OBSIDIAN_URL/" \
  | python3 -c "import json,sys; d=json.load(sys.stdin); print('OK — Obsidian', d['versions']['obsidian'], '| Plugin', d['versions']['self'], '| Auth:', d['authenticated'])"

Expected: OK — Obsidian 1.x.x | Plugin 3.x.x | Auth: True

If $OBSIDIAN_URL is empty, substitute the literal URL:

curl -sk \
  -H "Authorization: Bearer YOUR_API_KEY_HERE" \
  "https://YOUR_OBSIDIAN_HOST:27124/" \
  | python3 -c "import json,sys; d=json.load(sys.stdin); print('OK — Obsidian', d['versions']['obsidian'], '| Plugin', d['versions']['self'], '| Auth:', d['authenticated'])"

4. Install the skill

# Via ClawHub
openclaw skills install obsidian-rest

# Or manually
git clone https://github.com/nj070574-gif/openclaw-obsidian-vault-skill.git
cp -r openclaw-obsidian-vault-skill/skill ~/.openclaw/workspace/skills/obsidian-rest

Environment Variables

VariableRequiredDescription
OBSIDIAN_URL✅ YesFull base URL including protocol and port, e.g. https://192.168.1.100:27124
OBSIDIAN_API_KEY✅ YesAPI key from Obsidian → Settings → Local REST API

Always use curl -sk — the plugin uses a self-signed certificate by default.


API Reference

All requests require the auth header:

Authorization: Bearer $OBSIDIAN_API_KEY

Check API status (root endpoint only)

curl -sk -H "Authorization: Bearer $OBSIDIAN_API_KEY" "$OBSIDIAN_URL/"

Returns: {"status":"OK","authenticated":true,"versions":{"obsidian":"1.x.x","self":"3.x.x"}, ...}


List vault root (trailing slash required)

curl -sk -H "Authorization: Bearer $OBSIDIAN_API_KEY" "$OBSIDIAN_URL/vault/" \
  | python3 -c "import json,sys; [print(f) for f in sorted(json.load(sys.stdin)['files'])]"

List a subfolder (trailing slash required)

curl -sk -H "Authorization: Bearer $OBSIDIAN_API_KEY" "$OBSIDIAN_URL/vault/My%20Folder/" \
  | python3 -c "import json,sys; [print(f) for f in json.load(sys.stdin)['files']]"
URL encoding: spaces → %20 | forward slash within a path segment → %2F

Encode any path automatically:

python3 -c "import urllib.parse; print(urllib.parse.quote('My Folder/My Note.md', safe=''))"

Read a note

curl -sk -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  "$OBSIDIAN_URL/vault/PATH%2FTO%2FNOTE.md"

Returns raw Markdown content.


Create or overwrite a note (PUT)

curl -sk -X PUT \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  -H "Content-Type: text/markdown" \
  --data-binary "# My Note Title

Content goes here." \
  "$OBSIDIAN_URL/vault/PATH%2FTO%2FNOTE.md"

Returns HTTP 204 No Content on success. Warning: PUT replaces the entire file. Use POST to append safely.


Append to an existing note (POST)

curl -sk -X POST \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  -H "Content-Type: text/markdown" \
  --data-binary "

## New Section $(date +%Y-%m-%d)

Content to append." \
  "$OBSIDIAN_URL/vault/PATH%2FTO%2FNOTE.md"

Returns HTTP 204 No Content on success.


Patch / insert at a heading (PATCH)

curl -sk -X PATCH \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  -H "Content-Type: text/markdown" \
  -H "Obsidian-API-Operation: append" \
  -H "Heading: My Section Heading" \
  --data-binary "Content to insert under the heading." \
  "$OBSIDIAN_URL/vault/PATH%2FTO%2FNOTE.md"

Valid operations: append | prepend | replace


Delete a note

curl -sk -X DELETE \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  "$OBSIDIAN_URL/vault/PATH%2FTO%2FNOTE.md"

Returns HTTP 204 No Content on success.


Search vault (full-text)

curl -sk -X POST \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  "$OBSIDIAN_URL/search/simple/?query=YOUR+SEARCH+TERM&contextLength=150" \
  | python3 -c "
import json, sys
results = json.load(sys.stdin)
if not results:
    print('No matches found.')
else:
    print(f'Found {len(results)} match(es):')
    for r in results[:5]:
        print(' -', r['filename'])
        for m in r.get('matches', [])[:1]:
            ctx = m.get('context', '').strip()
            if ctx: print('   ...', ctx[:100])
"

Get currently active file in Obsidian

curl -sk -H "Authorization: Bearer $OBSIDIAN_API_KEY" "$OBSIDIAN_URL/active/"

List available Obsidian commands

curl -sk -H "Authorization: Bearer $OBSIDIAN_API_KEY" "$OBSIDIAN_URL/commands/" \
  | python3 -c "import json,sys; [print(c['id'], '|', c['name']) for c in json.load(sys.stdin).get('commands',[])]"

Execute an Obsidian command

curl -sk -X POST \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"commandId": "editor:save-file"}' \
  "$OBSIDIAN_URL/commands/execute/"

Output Formatting Rules

Never dump raw JSON to the user. Always interpret results and reply in plain English.

SituationWhat to say
Status check returns "authenticated": true"✅ Obsidian vault connected — Obsidian v1.x.x, plugin v3.x.x"
Status check fails / 40400 error"❌ Cannot reach Obsidian vault: [exact error]. Check Obsidian is running."
Vault listed"Your vault contains X items: [list files and folders]"
Subfolder listed"Found X notes in [folder]: [list]"
Note readReturn the note content (or a summary if it's long)
Note created (HTTP 204)"✅ Created [path]"
Note saved / overwritten (HTTP 204)"✅ Saved to [path]"
Note appended (HTTP 204)"✅ Appended to [path]"
Search returns results"Found X notes matching '[query]': [list filenames]"
Search returns nothing"No notes found matching '[query]'"
40400 error"❌ API returned Not Found — check the path and trailing slashes"
401 error"❌ Unauthorised — check OBSIDIAN_API_KEY is set correctly"

Workflow Guide

Saving content ("sv" / "save this")

  1. Check env vars expand: echo "URL=$OBSIDIAN_URL LEN=${#OBSIDIAN_API_KEY}"
  2. Pick the right folder from context (infrastructure → Infrastructure/, daily log → Daily/)
  3. Choose a descriptive hyphenated filename, e.g. Setup-Guide-2026-04-12.md
  4. Check if file exists: GET /vault/PATH.md — HTTP 404 means safe to create
  5. Use PUT to create, POST to append to existing
  6. Confirm with plain English: "✅ Saved to Infrastructure/Setup-Guide.md"

Finding a note

  1. Search: POST /search/simple/?query=TERM
  2. If multiple results, list filenames and ask which to open
  3. GET the file and return its content or a summary

Updating a note

  1. Read the file first to understand its structure
  2. POST to append, or PATCH with Heading header for targeted insertion
  3. Confirm what was added and where

Creating new folders

New folders are created automatically when you PUT a file into a path that doesn't exist yet.


Common Patterns

Save a runbook

NOTE_PATH="Infrastructure%2FRunbook-$(date +%Y-%m-%d).md"
curl -sk -X PUT \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  -H "Content-Type: text/markdown" \
  --data-binary "# Runbook — $(date +%Y-%m-%d)

## Steps

1. Step one
2. Step two
" \
  "$OBSIDIAN_URL/vault/$NOTE_PATH"
echo "Saved to vault/$NOTE_PATH"

Append a timestamped log entry

curl -sk -X POST \
  -H "Authorization: Bearer $OBSIDIAN_API_KEY" \
  -H "Content-Type: text/markdown" \
  --data-binary "
- $(date '+%Y-%m-%d %H:%M') — Log entry here" \
  "$OBSIDIAN_URL/vault/Daily%2FLog.md"

URL Encoding Quick Reference

CharacterEncoded
Space %20
/ (within a path segment)%2F
#%23
&%26
+%2B

Troubleshooting

SymptomLikely causeFix
curl: (7) Failed to connectObsidian not running or wrong host/portCheck Obsidian is open; verify OBSIDIAN_URL
{"message":"Not Found","errorCode":40400}Wrong path — missing trailing slash, or non-existent endpointAdd / to end of directory paths; use only documented endpoints
HTTP 401 UnauthorizedWrong or missing API keyVerify OBSIDIAN_API_KEY matches plugin settings
SSL certificate errorSelf-signed certAlways use curl -sk — never curl -s alone
$OBSIDIAN_URL empty in curlEnv var not inherited by exec shellTest with echo $OBSIDIAN_URL; use literal values if empty
Skill shows △ needs setupEnv vars not setAdd Environment= lines to openclaw.service, reload, restart
Obsidian on Windows, agent on LinuxFirewall blocking portAllow TCP 27124 inbound in Windows Defender Firewall

Windows Firewall (Obsidian on Windows, OpenClaw on Linux)

Windows Defender Firewall → Advanced Settings → Inbound Rules → New Rule
→ Port → TCP → 27124 → Allow → All profiles → Name: "Obsidian Local REST API"

Plugin Information

  • Plugin: Obsidian Local REST API by Adam Coddington
  • Default port: 27124
  • Protocol: HTTPS (self-signed cert) or HTTP
  • Obsidian minimum version: 0.12.0
  • Plugin version tested: 3.2.0

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

77.61%
按下载量换算1,014

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills