obsidian-note-hub

Coordinate Obsidian note tools for archive, cleanup, merge, lint, and docs sync workflows.

18|2|Updated Mar 18, 2026

Search Tags:#automation #workflow #cli #orchestration #obsidian #notes-tools

Ready to run

npx skills add https://github.com/Onlyaguest/ViviStableSkills --skill obsidian-note-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: obsidian-note-hub
Source: https://github.com/Onlyaguest/ViviStableSkills/tree/main/obsidian-note-hub
Command: npx skills add https://github.com/Onlyaguest/ViviStableSkills --skill obsidian-note-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified orchestration for Obsidian note workflows by exposing a single, auditable entrypoint that coordinates existing tools without duplicating logic.

Core Features & Use Cases

Central command surface to run common tasks (archive, cleanup, merge, lint, docs sync) against an existing notes-tools repo.
Safe, audit-friendly operations with side-effect-free validation (list, check) before any vault changes.
Real-world scenario: a team wants to orchestrate daily note maintenance across multiple tools without scripting each step.

Quick Start

Run the orchestrator from the project root to discover available commands and validate your setup.

Frequently Asked Questions about obsidian-note-hub

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Obsidian note workflows like daily rollover and cleanup from a single command?▼

Automate Obsidian note workflows by using a single orchestration entrypoint that coordinates archive, cleanup, merge, lint, and daily rollover tasks without duplicating logic. It provides a central command surface to execute complex vault maintenance operations through one auditable interface.

Can I validate Obsidian vault changes before applying them to prevent data loss?▼

Validate Obsidian vault changes safely by running non-destructive 'list' and 'check' workflows before any modifications occur. The orchestrator applies side-effect-free validation to verify setup and preview operations, ensuring safe dispatch to underlying tasks.

Does the Obsidian notes orchestrator support dry-run mode for testing vault operations?▼

Dry-run support is implemented directly within the Obsidian notes orchestrator to test vault operations safely. It enables input validation and configuration mapping to preview task execution without applying actual changes to your notes repository.

What is the best way to orchestrate multiple note tools for a team's daily maintenance without custom scripts?▼

Orchestrate multiple note tools for team maintenance by routing all commands through a single auditable entrypoint that handles dispatch logic. This approach coordinates existing tools across your notes-tools repo, eliminating the need to script each maintenance step individually.

Do I need an existing notes-tools repository to use this orchestration surface?▼

An existing notes-tools repository is required as the orchestration surface coordinates tasks against your current setup rather than duplicating tool logic. Run the orchestrator from your project root to discover available commands and validate your environment.

Can I use this orchestrator to sync documentation with my Obsidian notes?▼

Docs sync is supported as one of the core workflows coordinated by the Obsidian note orchestrator. You can execute documentation synchronization safely alongside archive, cleanup, merge, and lint operations through the unified command surface.