googlicius/obsidian-steward/user-defined-command

User-Defined Command Skill

This skill enables you to create and edit valid Steward user-defined commands — YAML-based command definitions stored as markdown files in the Steward/Commands folder.

File Format

Each command is a markdown file (.md) containing one or more YAML code blocks. The file can also contain plain text, headings, and other markdown content that can be referenced by system prompts.

After creating or updating a UDC note, re-read the file and check the frontmatter status. If it is invalid, use the status error to fix the YAML and re-read again.

YAML Schema

Command-Level Fields

Step-Level Fields

Trigger Fields

CLI settings (v2)

Use the root-level cli field when a command runs shell tools and you want to control how the local shell behaves.

cli:
  shell: /bin/zsh # optional: override the shell executable for new sessions
  whitelist:
    - 'yt-dlp*'
    - 'Get-Content*'
    - 'rm *_temp_transcript*'
    - 'cat _temp_transcript.en.srt'

cli.shell

Optional path to the shell executable when Steward spawns a new session for this command. Falls back to global Steward CLI settings when omitted.

cli.whitelist

Optional list of patterns (max 50 entries). When the Super Agent sends a model shell line in transcript mode (not interactive terminal mode), a matching pattern skips the confirmation prompt.

Matching rules (applied to the trimmed command line):

Examples:

• Get-Content* — commands starting with Get-Content
• rm *_temp_transcript.en.srt — rm followed by optional flags/whitespace, then that file path
• rm *_temp_transcript* — rm commands that mention _temp_transcript (quoted or unquoted)
• *_temp_transcript.en.srt — any command that ends with that filename

Notes:

• An entry cannot be only * wildcards; include at least one literal character.
• Empty shell lines never match (opening an interactive shell still requires confirmation).
• Interactive terminal commands always require confirmation, even when whitelisted.

Command Syntax (Direct Tool Calls)

Steps can use command syntax in the query field to invoke tools directly without an AI round trip. This is the preferred approach for deterministic operations.

Syntax

c:<tool> [--arg=value]...

• c: prefix identifies a direct command call
• <tool> is a short alias (see reference below)
• --key=value pairs map to the tool's input schema
• Multiple commands can be chained with ; separator: c:read --blocks=1; c:edit --mode=replace_by_lines
• Quoted values for strings with spaces: --content="hello world"
• Comma-separated values for arrays: --files=Note1.md,Note2.md

Command Reference

c:read Flags

c:search Flags

c:delete Flags