Docyrus CLI

Command index for the docyrus CLI (@docyrus/docyrus). This skill is a quick reference to what commands exist. For exact flags, arguments, and payload shapes of any command, run its help — that is the authoritative, always-current source:

docyrus <command> --help                 # flags + args for a command or group
docyrus <command> <subcommand> --help     # drill into a subcommand
docyrus <command> --llms                  # machine-readable (LLM) manifest of a command tree

Conventions (apply across all commands)

• Output: add --json (or --format <toon|json|yaml|md|jsonl>) for machine-readable output; --verbose shows the full envelope.
• Flag forms: --help prints flags in kebab-case (--app-slug, --from-file); the parser also accepts the camelCase schema keys (--appSlug, --fromFile). Both work.
• Selectors are exclusive pairs — pass exactly one of each; the CLI resolves the other: --appId | --appSlug, --dataSourceId | --dataSourceSlug, --fieldId | --fieldSlug, etc.
• Write payloads: mutating commands take convenience flags and/or --data '<json>' / --from-file <path.json>. Explicit flags merge over the JSON. Complex objects (nested data, field_mapping, schemas, conditions) must go through --data/--from-file.
• Settings scope & sessions: settings live in a project-local ./.docyrus/ folder (ancestor-resolved from cwd); -g/--global uses ~/.docyrus/. Auth and the active tenant are per-scope.
• Escape hatch: docyrus curl <path> [-X .. -d .. -G] sends an authenticated request to any API path — use it for endpoints without a dedicated command (e.g. template render, webform items). For complex reads, pass query params as one JSON object with -G -d '{...}' (URL-encoded for you).