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- .yaml receipt. Use when the user says anything about setting up, provisioning, onboarding, creating, or configuring Alvera platform resources.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
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- .yaml receipt. Use when the user says anything about setting up, provisioning, onboarding, creating, or configuring Alvera platform resources.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
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.
About this listing
Category
Engineering
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI