openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > Obsidian Organizer

Organize and standardize Obsidian vaults for reliability and long-term maintainability. Use when designing or cleaning vault folder structure, enforcing file...

开发与 DevOps

作者:Tony Simons @asimons81

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v1.0.0

统计:⭐ 0 · 725 · 9 current installs · 9 all-time installs

0

安装量(当前) 9

🛡 VirusTotal :良性 · OpenClaw :良性

Package:asimons81/obsidian-organizer

安全扫描(ClawHub)

  • VirusTotal :良性
  • OpenClaw :良性

OpenClaw 评估

The skill's files and instructions are coherent with its stated purpose (auditing and renaming Obsidian notes); it does local filesystem renames when you explicitly run with --apply and otherwise performs dry-runs.

目的

Name, description, reference docs, SKILL.md workflow, and the included Python audit script all align: they audit and optionally rename markdown files to a deterministic naming scheme for an Obsidian vault. No unrelated credentials, binaries, or external services are requested.

说明范围

Runtime instructions are limited to reading the included reference docs, running the audit script on a user-supplied vault path (dry-run by default), following a migration checklist, and manually fixing links. The script operates only on local files under the provided path and does not read other environment variables or send data externally. Note: the script performs recursive renames across the supplied path, so supplying the wrong path coul…

安装机制

No install mechanism is provided (instruction-only with a small included script). No downloads or third-party package installs are required.

证书

The skill requires no environment variables, credentials, or config paths. This is proportionate to its stated function of local file auditing and renaming.

持久

The skill is not forced-always and does not request persistent presence or modify other skills or system-wide settings. It can be invoked by the agent (normal default) but has no autonomous persistence requirements.

综合结论

This skill appears to do exactly what it claims: audit and optionally rename markdown files in an Obsidian vault. Before running with --apply, make a full backup of your vault and review the printed rename plan from the dry-run. Be aware renames may break Obsidian internal links — follow the checklist to fix links (the skill does not update links automatically). Also, double-check the vault path you pass to the script to avoid accidental chang…

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Obsidian Organizer」。简介:Organize and standardize Obsidian vaults for reliability and long-term maintain…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/asimons81/obsidian-organizer/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: obsidian-organizer
description: Organize and standardize Obsidian vaults for reliability and long-term maintainability. Use when designing or cleaning vault folder structure, enforcing file naming conventions, migrating messy vaults, reducing duplicate/ambiguous notes, or creating repeatable audit-and-fix workflows for Obsidian notes.
---

# Obsidian Organizer

Use this skill to make a vault predictable, searchable, and low-maintenance.

## Workflow

1. Snapshot current state
   - Count files and top-level folders.
   - Identify naming drift and duplicate patterns.

2. Apply standard structure
   - Read `references/folder-structure.md`.
   - Propose moves before applying.

3. Enforce naming rules
   - Read `references/naming-rules.md`.
   - Run audit script in dry-run mode:
     - `python scripts/obsidian_audit.py <vault-path>`
   - Apply only after confirmation:
     - `python scripts/obsidian_audit.py <vault-path> --apply`

4. Run migration checklist
   - Follow `references/migration-checklist.md` in order.

5. Verify
   - Re-run audit until zero naming issues.
   - Confirm daily notes use `YYYY-MM-DD.md`.
   - Confirm no orphaned notes remain in `inbox/`.

## Guardrails

- Never rename or move files without a dry-run first.
- Never delete notes automatically.
- Prefer deterministic naming over clever naming.
- Keep folder depth shallow (<=3 when possible).
- If link integrity is uncertain, pause and ask before bulk apply.