From trillo
The deploy step — push the app's metadata to Trillo AOS and watch it complete. Use when the user wants to deploy or redeploy, or after the model/functions are ready. Deploy is required before testing functions or seeding data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/trillo:deployThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pushes the app's metadata (entities, functions, agents, spec) to Trillo AOS,
Pushes the app's metadata (entities, functions, agents, spec) to Trillo AOS, which provisions the schema + APIs and makes the app runnable.
app_status — the app needs at least an entity model.deploy_app (load the deploy group via discovery_load_group if it's
not in your tool list) → returns a taskId.task_events until it ends; report success or the failure reason.app_status / app_select → deployStatus: deployed.function_test_sync), seed
data, run agents.After any metadata change (entities, functions, agents), redeploy to push it. Prod is locked — dev only; promotion to production is a Trillo UI workflow.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub trillo/tcs-claude-plugin --plugin trillo