How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-automationBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
AE Automation
See command risks. Read the command contract before writing or executing an automation. Use ae-cli automation --help and leaf help to discover flags.
- Resolve the host and space. A local user signs in with
ae-cli auth login; a sandbox uses the current conversation user's injected CLI token, never a shared sandbox's user binding. Pass--agent-space-idwhen the user identifies a space. Without an explicit space, the CLI inherits the current AgentSpace from its runtime context, working directory or verified current conversation; only a local invocation without space context uses the personal default. Show the resolved space when it matters. - Discover the automation with
automation listand inspectautomation get. Use the returned IDs; names are not unique. - For creation, select an Agent or team through the corresponding discovery commands. Match configuration to the target type. Use
--weekdaysor--days-of-monthJSON arrays for multiple days with one time; skip dates absent in a month. For the actual last day of every month use--days-of-month '["L"]', or combine it with dates, e.g.'[1,15,"L"]'; overlapping selections execute only once. Both Agent and Agent Team accept result notifications. Confirm the complete configuration before creation; save only the recurring task instructions as--message, never the automation-creation guide. Preview writes with--dry-runwhen useful; the CLI shows a redacted request and asks the server to validate authentication, space, permissions, target state, fields, and idempotency without applying the operation. - Execute the requested operation. Deleting an automation or stopping an execution requires confirmation; use
--yesonly when the user already authorized that action. In a non-interactive shell, these operations fail immediately unless global--yesis present. - Read the returned run ID, then
automation runs result. Report acceptance separately from completion. Use--waitonly when the user needs the final outcome now.
Results are read from the server and work outside the sandbox. This skill does not read complete conversations or continue a chat. Never infer an output from a different execution sharing the same conversation.
