ShadowBot CLI

Problem

ShadowBot CLI is useful when desktop automation needs to run through scripts, agents, or operations workflows. Examples, aliases, and old notes can be unreliable, and Windows paths, JSON, usernames, and cron strings should not be guessed. The skill requires checking the real executable help before running the smallest necessary action.

How it works

• Auth and session: start with auth current, then use auth account list and auth login --username ...; provide a password only when the account is not remembered.
• Apps and tasks: find the --app-id with console app and --search, run console task run --app-id ..., then use status, logs, and stop.
• Triggers and config: support console trigger list, add, update, --details-json, and --cron; handle config via config list, describe, get, and set.
• Studio and UI: run studio create, studio open, and ui --exec for window or mode switches.

Boundaries

Only execute commands and flags confirmed by shadowbot.shell-cli.exe -h; surface key fields from error JSON instead of inventing recovery. Preserve user-provided accounts, paths, UUIDs, cron strings, and JSON exactly.