Docyrus CLI App
Use the Docyrus CLI (`docyrus`) to interact with the Docyrus platform from the terminal. Use when the user asks to authenticate, list apps, query or manage data records (`ds`), manage dev app data source schema objects (`studio`) including data sources, fields, enums, data views, forms, webforms, HTML/PDF export templates, and email templates, manage automations and their triggers/action nodes (`automation`), build or edit custom AI agents and their sub-resources (`agent`), set an app's AI agent context or manage app-scoped AI tools (`apps`), list tenant email accounts and send emails (`messaging`), manage tenant account settings — brands, the current user's profile, and tenant regional/formatting preferences (`account`), discover and call connectors (`connect`), send API requests, switch tenants/accounts, discover tenant OpenAPI specs, drive browser automation (`browser`), chat with platform agents (`docy`), launch the pi cowork/coding agents (`worky`/`cody`/`coder`), run the agent bridge server (`server`), manage the repo knowledge graph (`knowledge`) and project plan (`project-plan`), cut releases (`release`), or use the terminal UI via `docyrus tui`. Triggers on `docyrus ds list`, `docyrus ds comments`, `docyrus ds files upload`, `docyrus studio`, `docyrus studio search-fields`, `docyrus automation`, `docyrus automation create-node`, `docyrus agent`, `docyrus apps create`, `docyrus apps set-agent-context`, `docyrus apps ai-tools`, `docyrus messaging email send`, `docyrus account brands`, `docyrus account user-profile`, `docyrus account tenant-preferences`, `docyrus connect`, `docyrus discover`, `docyrus auth`, `docyrus browser`, `docyrus knowledge`, `docyrus project-plan`, `docyrus release`, `docyrus server`, `docyrus tui`, or any terminal-based Docyrus workflow.
- Skill ID
- docyrus/agent-skills/docyrus-cli-app
- Publisher
- docyrus
- Repository
- agent-skills
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
docyrus/agent-skills/docyrus-cli-appInstalls these files- SKILL.md
What this skill tells the agent
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 treeConventions (apply across all commands)
- Output: add
--json(or--format <toon|json|yaml|md|jsonl>) for machine-readable output;--verboseshows the full envelope. - Flag forms:
--helpprints 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 (nesteddata,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/--globaluses~/.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).
Command index
Run docyrus <command> --help for flags. Groups marked (group) have their own subcommands — drill in with --help.
auth — authentication, accounts, tenants
login · logout · who · tenant · set-tokens · sso-session · github · sandbox · git-credential · accounts (group) · tenants (group)
apps — apps & app-scoped resources
create (requires --slug) · clone · templates · check-slug (app creation + local-dev bootstrap — see docyrus-create-app) · list · update · delete · restore · permanent-delete · set-agent-context · actions (group: action CRUD + run) · ai-tools (group: app-scoped AI tool CRUD — see docyrus-app-ai-tools)
ds — data records (CRUD + sub-objects)
get (data source metadata) · list (query records) · create · update · delete · comments (group: record comments) · files (group: record file attachments, incl. upload)
dsql — logical SQL querying
query (read-only SELECT over appSlug.dataSourceSlug) · ask (NL → query → run) · generate (NL → query, no run) · schema (group: schema discovery). See docyrus-dsql-query-design. Custom query records (saved, parameterized query templates): list-custom-query · get-custom-query · create-custom-query · update-custom-query · delete-custom-query · run-custom-query (execute; --debug = compiled SQL, --simulate = EXPLAIN ANALYZE). See docyrus-custom-query.
studio — dev app schema CRUD
Data sources: create-data-source · get-data-source · update-data-source · delete-data-source · restore-data-source · permanent-delete-data-source · list-data-sources · bulk-create-data-sources Fields: create-field · get-field · update-field · delete-field · list-fields · create-fields-batch · update-fields-batch · delete-fields-batch · search-fields Enums: create-enums · update-enums · delete-enums · list-enums · search-enums · search-enum-sets Data views: create-data-view · get-data-view · update-data-view · delete-data-view · list-data-views Forms: create-form · get-form · update-form · delete-form · list-forms Webforms: create-webform · get-webform · update-webform · delete-webform · list-webforms (see docyrus-webform-design) HTML/PDF templates: create-html-template · get-html-template · update-html-template · delete-html-template · list-html-templates (see docyrus-print-pdf-template-design) Email templates: create-email-template · get-email-template · update-email-template · delete-email-template · list-email-templates (see docyrus-email-template-design) → Design how-to: docyrus-data-source-design.
automation — workflows
Automations: create · get · update · delete · list Triggers: create-trigger · update-trigger · delete-trigger · get-trigger · list-triggers Action nodes: create-node · update-node · delete-node · get-node · list-nodes → Design how-to: docyrus-automation-design.
agent — custom AI agents & sub-resources
Agent: create · get · update · delete · list · upload Sub-resource groups (each list/get/create/update/delete): models · tools · data-sources · docs · mcps · connections · dynamic-contexts · workflow-steps · deployments · deployment-tools · deployment-data-sources · workflow-jobs (read-only + delete) · tasks · recurring-tasks → Design how-to: docyrus-agent-design.
messaging — email & notifications
accounts (list tenant email accounts) · email (group: incl. send)
account — tenant account management
brands (group: tenant brand CRUD — list · get · create · update · delete · fetch-from-website) · user-profile (group: get · update the current user's own profile) · tenant-preferences (group: get · update the tenant's regional/formatting preferences)
- `brands` — the tenant's visual identity, typography, voice, and content guidelines (
tenant_brand).create/updatetake camelCase convenience flags (1:1 with the snake_case DTO keys) plus--data/--from-file;--nameis required oncreate. → Manage how-to (incl. full field catalog): docyrus-tenant-brand-management. - `user-profile` — the authenticated user's own profile (
get/update, no selector).updateflags cover the self-service fields:--firstname·--lastname·--mobile·--dateOfBirth·--gender·--timeZone·--language. - `tenant-preferences` — the workspace's regional/formatting settings.
updateis tenant-admin only and takes camelCase flags (1:1 with the snake_case--datakeys) plus--data/--from-file:--language·--locale·--timeZone·--startWeekOn·--fiscalYear·--dateFormat·--dateTimeFormat·--timeFormat·--longDateFormat·--businessHoursBegin·--businessHoursEnd·--dailyWorkingHours(seconds) ·--weeklyWorkingCapacity·--timeRounding·--baseCurrency·--currencyAbbrPosition(BEFORE/AFTER) ·--decimalPrecision·--decimalSeparator·--thousandSeparator.getreturns just the preferences record (camelCase keys).
→ user-profile / tenant-preferences how-to (incl. full field catalog): docyrus-account-settings.
connect — connectors & actions
list-connectors · get-connector · list-connections · get-action · run-action · curl (request through a connector's provider auth) → Usage how-to: docyrus-integrations-and-connectors.
discover — tenant OpenAPI discovery
api (download spec) · namespaces · path · endpoint · entity · search
curl — raw API
docyrus curl <path> [-X <method>] [-d <body>] [-G] [-H <header>] — authenticated request to any Docyrus API path.
- Body:
docyrus curl -X POST /v1/apps -d '{"name":"..."}'— a JSON-dis sent as the request body. - Query params: with
-G, pass-da single JSON object — each key becomes a query param, nested values are JSON-stringified, and every value is URL-encoded for you. This is the way to send complex reads (columns,filters,childQueries) without escaping:
More from docyrus
Use this skill in a project
Open any RiverX project, search the Skills panel for docyrus/agent-skills/docyrus-cli-app, and install it in one click.
