菜单
Unified entrypoint for Obsidian note operations such as cleanup, merge, lint/fix, meeting archive, daily rollover, and docs sync. Use when the user wants one command surface over an existing notes-tools repo instead of calling many atomic scripts by hand.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Open local review artifacts in Xiaoer Omia when users ask to open, preview, inspect, or review a file.
Run a measured improvement loop for a skill by defining a yes/no checklist, capturing a baseline, scoring candidate outputs, and logging each iteration's keep/revert decision. Use when a skill works inconsistently and you want evidence-driven iteration instead of random prompt edits.
Build a static HTML report site from CSV, JSON, Markdown, or HTML inputs. Use when the user wants to turn existing data into a human-readable site, generate a data showcase page, create a static report website, or optionally publish the built site.
Add offline multilingual support to static HTML, small web projects, or reports by extracting text into tokens, maintaining language dictionaries, applying translated outputs, and optionally embedding a local language switcher. Use when the user asks for bilingual support, tokenizing Chinese copy, offline language switching, or i18n for reports and lightweight sites.
Test, tune, and regression-check LLM system prompts with a golden dataset. Use when the user wants to optimize a prompt, run prompt regression tests, manage `cases.yaml`, compare expected vs actual outputs, or follow a TDD workflow for prompts.
Evaluate whether a proposed skill is worth building by scoring it against five moat-oriented questions: differentiation, vertical fit, learning loop, user difficulty, and defensibility. Use when someone proposes a new skill and you want a fast build / deepen / reject decision before implementation.
| name | obsidian-note-hub |
| description | Unified entrypoint for Obsidian note operations such as cleanup, merge, lint/fix, meeting archive, daily rollover, and docs sync. Use when the user wants one command surface over an existing notes-tools repo instead of calling many atomic scripts by hand. |
| version | 1.0.0 |
| author | Vivi |
| tags | ["obsidian","notes","workflow","archive","orchestrator"] |
| platforms | ["all"] |
| dependencies | ["python3"] |
One front door for a mature note-ops tool family. This skill dispatches into an existing notes-tools repo and gives humans or agents a stable command surface for common Obsidian maintenance workflows.
python3 main.py list to inspect the public command surface.python3 main.py check after setting REPO_ROOT and VAULT_ROOT.Inspect available commands:
python3 main.py list
Validate config and dispatch map:
REPO_ROOT=/absolute/path/to/MyNotesTools \
VAULT_ROOT=/absolute/path/to/ObsidianVault \
python3 main.py check
Safe dry-run examples:
REPO_ROOT=/absolute/path/to/MyNotesTools \
VAULT_ROOT=/absolute/path/to/ObsidianVault \
python3 main.py meeting-archive --dry-run
REPO_ROOT=/absolute/path/to/MyNotesTools \
VAULT_ROOT=/absolute/path/to/ObsidianVault \
python3 main.py docs-sync --summary "docs sync" --dry-run --skip-moc
.env config, existing notes-tools repo, existing Obsidian vaultMinimum validation commands:
python3 main.py list
REPO_ROOT=/absolute/path/to/MyNotesTools VAULT_ROOT=/absolute/path/to/ObsidianVault python3 main.py check
docs-sync may need --skip-moc if the target vault does not have the Atlas MOC file