← ClaudeAtlas

aevatar-automationlisted

Aevatar scheduling & workflow automation: scheduled_agent_creator (cron/one-shot) for independent scheduled Ornn skill agents and reminders — NOT an alias for Studio Team member automation — the long-running task automation playbook, workflow creation semantics (Scope Workflow vs Ornn publish), agent_builder lifecycle, the typed required_nyx_services contract (exact user_service_id is the authorization; a slug snapshot never substitutes), dedicated Agent Key semantics (vault-held raw material, borrowed durable reference late-resolved per use, exact non-wildcard grants, ~90-day projected expiry, reauthorize-then-revoke, independent NyxID and Vault revocation tracks), accepted-is-admission-only receipts, and a token_expired triage protocol that reads credentialSourceKind before assuming any TTL.
ChronoAIProject/NyxID · ★ 36 · AI & Automation · score 78
Install: claude install-skill ChronoAIProject/NyxID
#### scheduled_agent_creator (scheduled Ornn skill agents) Use `scheduled_agent_creator` to create a new caller-owned scheduled automation agent from an Ornn skill reference, or to create a single delayed reminder. **This tool is for an independent scheduled Ornn skill agent or a one-shot reminder. It is NOT an alias for Studio Team member automation.** If the thing being scheduled is an already-bound Team member workflow, the canonical path is `aevatar_schedule_member_workflow` or `/api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations` — see `aevatar-scheduler`. Do not route a Team member here, and do not route an independent skill agent to generic `/api/schedules`. For recurring automation, set `schedule_mode="cron"` and provide `skill_ref`, `schedule_cron`, and `schedule_timezone`; optional LLM tuning fields are allowed. If the loaded skill body will call connected NyxID services through `nyxid_proxy` beyond Ornn and the Lark outbound channel, declare them with the typed requirement contract: ```text required_nyx_services[] = { user_service_id, service_slug_snapshot } ``` **The exact `user_service_id` is the authorization; the slug snapshot is an integrity/display value and can never substitute for it.** `nyx_user_service_id` identifies the exact outbound provider where applicable. The older `required_service_slugs` contract has been removed — do not recommend it, and never infer a UserService ID from a slug, a vendor name, or a catalog service ID (a con