alvera-agent

Outcome-driven Alvera platform provisioning. The user describes a business goal ("send review SMS after appointments", "onboard patient data from CSV", "create an AI agent for claim triage") and the skill derives the full dependency chain, checks what already exists, and provisions everything in the correct order — bottom-up execution, top-down design. Handles all resource types: datalakes, data sources, tools, generic tables (with compliance gate and column profiling), AI agents, agentic workflows (with templates and dry-run testing), connected apps, interop contracts, data activation clients, file ingestion (anti-pattern detection, Liquid template generation, sandbox testing), and PostgREST explorer scaffolding. Drives the `alvera` CLI from `@alvera-ai/platform-sdk`. Auth is session-based — the user runs `alvera login` themselves. Emits an `alvera-<tenant-slug>.yaml` receipt. Use when the user says anything about setting up, provisioning, onboarding, creating, or configuring Alvera platform resources.

End-to-end provisioning of a healthcare host on Alvera, walking the canonical 11-phase setup defined by `tests/healthcare/_order.json` in `@alvera-ai/platform-sdk@0.8.0` (the executable contract). Each phase delegates to a primitive skill (`guided`, `custom-dataset-creation`, `DAC-upload`, `agentic-workflow-creation`, `query-datasets`) and ends with a verification pointer back at the corresponding integration-tests spec, so the conversational setup and the automated suite never drift apart. Use when the user says "set up healthcare", "provision a healthcare tenant", "walk me through healthcare setup end to end", or similar. Domain-first orchestrator — invoke the primitive skills directly for ad-hoc / out-of-sequence work.

End-to-end provisioning of an accounts-receivable host on Alvera. Currently a STUB — the canonical setup walk lives in `tests/accounts_receivable/_order.json` at `@alvera-ai/platform-sdk@0.8.0`, which today contains only a smoke spec because the AR industry is not yet productionised. Use this skill to get a stub setup conversation that lists the AR-specific resource types and routes to `/guided` for ad-hoc creation. Real domain orchestration replaces this stub when AR integration coverage lands. Use when the user says "set up accounts-receivable", "provision an AR tenant", or similar.

End-to-end provisioning of a payment-risk host on Alvera. Currently a STUB — the canonical setup walk lives in `tests/payment_risk/_order.json` at `@alvera-ai/platform-sdk@0.8.0`, which today contains only a smoke spec because the payment-risk industry is not yet productionised. Use this skill to get a stub setup conversation that lists payment-risk-specific resource types and routes to `/guided` for ad-hoc creation. Real domain orchestration replaces this stub when payment-risk integration coverage lands. Use when the user says "set up payment-risk", "provision a KYC/AML tenant", "fraud setup", or similar.