技能详情（站内镜像，无评论）
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v1.0.0
统计：⭐ 0 · 109 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：可疑 · OpenClaw ：良性
Package：darinrowe/git-backed-obsidian-cli-workflows
安全扫描（ClawHub）
- VirusTotal ：可疑
- OpenClaw ：良性
OpenClaw 评估
The skill is internally consistent: it wraps the Obsidian CLI for read/write workflows and runs a bundled git-backed sync script after writes; nothing in the bundle asks for unrelated credentials or downloads external code.
目的
Name/description align with the included code and instructions. The Python wrapper and backup.sh implement conservative read/write workflows and a post-write git sync, which is coherent for a 'git-backed Obsidian CLI workflows' skill.
说明范围
SKILL.md directs use of the official obs CLI for queries and the bundled scripts for deterministic write+sync behavior. This is appropriate, but the post-write backup runs git operations (fetch, add, commit, pull, push) which will cause network activity to the repository's configured remote and may transmit changed notes. This behavior is expected for git-backed sync but is material and should be reviewed by the user.
安装机制
No install spec or external downloads; the skill is delivered with local scripts (Python and shell). No archives or remote installers are invoked by the bundle itself.
证书
The skill declares no required environment variables but the scripts read several optional ones (NOTES_VAULT_ROOT, NOTES_BACKUP_SCRIPT, NOTES_INBOX_NOTE, NOTES_OBS_CMD, NOTES_GIT_BRANCH). These are reasonable and proportional to the task, but the defaults (e.g., /root/obsidian-vault) should be checked to avoid accidental modification of unexpected paths. The skill does not request credentials explicitly but will use any existing Git credential…
持久
always is false and the skill does not request elevated platform privileges or modify other skills. It writes only to the configured vault path and runs a local backup script; no persistent platform-level changes are made by the bundle itself.
综合结论
This skill appears to do what it claims, but review a few things before installing: 1) Confirm NOTES_VAULT_ROOT (default: /root/obsidian-vault) to avoid accidental writes to an unexpected repository. 2) Inspect scripts/backup.sh so you understand which git remote/branch will be used—git push will transmit your notes using whatever Git credentials are configured. 3) Ensure the official obs CLI is installed and usable in the target environment (…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「git-backed-obsidian-cli-workflows」。简介：Use the official Obsidian CLI for note workflows in a Git-backed vault, includi…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/darinrowe/git-backed-obsidian-cli-workflows/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: git-backed-obsidian-cli-workflows
description: Use the official Obsidian CLI for note workflows in a Git-backed vault, including search, read, links/backlinks-style queries, daily-note operations, and lightweight note writes that auto-sync after successful write operations. Use when the official Obsidian CLI is already installed and usable on any supported environment, and the task is about querying or updating notes in an Obsidian vault with Git-backed backup behavior.
---
# Git Backed Obsidian CLI Workflows
Use the official Obsidian CLI as the primary workflow surface. Treat Git sync as a write-only follow-up, not part of read/query operations.
## Core rules
- Assume the official Obsidian CLI is already installed and usable.
- Use CLI-native read/query commands first for search, read, links, outline, tags, tasks, and related vault inspection.
- Use CLI-native write commands first for `daily`, `daily:append`, `create`, and similar lightweight note updates.
- After successful write operations, run the vault backup/sync script.
- Do not run Git sync after read-only operations.
- If a write-oriented CLI path is unavailable or unsuitable, fall back to direct file writing only when the workflow explicitly supports it.
- If sync fails after a successful write, report that the note was written but not synced.
## Environment model
This skill is **not server-only**. Use it anywhere the official Obsidian CLI is already available:
- desktop Linux
- macOS
- Windows environments where the official CLI is working
- headless/server environments that have already been adapted
If the environment is a headless server and the official CLI is not yet usable, use `obsidian-official-cli-headless` first. That skill handles server adaptation and installation. This skill handles the day-to-day note workflows after the CLI works.
## Fast path
1. Classify the request as either:
- read/query
- write/update
2. For read/query tasks, use the official CLI directly.
3. For write/update tasks, use the official CLI first, then run backup/sync.
4. Use fallback file writing only for supported write workflows when CLI writing is unavailable.
5. Report the target note/path, whether CLI or fallback was used, and whether sync succeeded.
## Common read/query commands
Prefer commands such as:
```bash
obs search query="..."
obs read file="..."
obs daily:read
obs links file="..."
obs outline file="..."
obs tags
obs tasks daily
obs vault
```
Use exact commands supported by the installed official CLI.
## Common write/update commands
Prefer commands such as:
```bash
obs daily
obs daily:append content="..."
obs create name="..." content="..."
```
After a successful write, run the backup script.
## Bundled scripts
Use `scripts/notes_workflow.py` when you need a deterministic wrapper for:
- daily-note append with sync
- lightweight memo/inbox capture with fallback write
- simple note create/append workflows with post-write sync
Use `scripts/backup.sh` as the default post-write Git sync path for this skill.
## References
- Read `references/query-vs-write.md` to choose whether a task should trigger sync.
- Read `references/fallbacks.md` for the fallback policy and reporting rules.
- Read `references/workflow-surface.md` to understand why the wrapper script supports a narrower write surface than the full official CLI.
- Read `references/environment-note.md` for the split between general CLI workflows and headless/server adaptation.
## What not to do
- Do not use this skill to install or configure the official CLI environment; use `obsidian-official-cli-headless` for that.
- Do not force-push from automation.
- Do not expand into full vault restructuring, plugin setup, or GUI management.
## What to report
Keep the result minimal:
- command or workflow used
- target note/path
- whether sync ran
- whether sync succeeded