user-defined-command

To create custom Obsidian Steward commands using YAML, define a command following the YAML schema in a Markdown file within the Steward/Commands directory. You can specify triggers, system prompts, and steps to automate repetitive vault tasks.

A user-defined command in Obsidian Steward is a customizable automation pipeline stored as YAML. It allows users to define command workflows with specific steps, triggers, and system prompts to standardize vault tasks.

You edit and troubleshoot Steward command workflows by modifying the YAML definitions within the Steward/Commands directory. Adjust the step definitions, triggers, and system prompts conforming to the schema to resolve issues and customize automation pipelines.

Yes, you can reuse and share Obsidian Steward command definitions across projects. Because the commands are stored as YAML files, you can copy them between vaults to standardize automation and reduce manual setup.

Yes, Steward supports optional tool usage within YAML command definitions. The schema allows you to specify optional tools alongside triggers and system prompts when creating user-defined commands.