Menu
Deploy the labs environment to AWS via GitHub Actions. Use when the user wants to deploy, release, or push changes to the labs environment.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use this skill when iterating on a live workflow in labs — reading JSX, editing render code, pushing it back — via the connect_labs MCP. Triggers on phrases like "pull workflow", "fix the workflow UI", "edit workflow X", "update the render code on workflow N", "clone this workflow", "make this a template". Do NOT use for editing seed template .py files in the repo (use workflow-templates for that).
Use this skill ONLY when authoring a new SEED template — a Python file in connect_labs/workflow/templates/ that ships with labs and scaffolds new workflows via workflow_create_from_template. For editing a live workflow instance in labs (the common case), use workflow-author instead. For editing a live pipeline schema, use pipeline-author.
Use when composing or editing a labs "surface" — a card landing page at /labs/p/<slug> — via the connect_labs MCP. Triggers on "build a program hub", "make a landing page for program/opp X", "add an audit card", "create a pages surface".
Use when the user wants to set up or refresh their labs MCP Personal Access Token (PAT). Triggers on "set up labs mcp", "I need a labs token", "configure claude for labs", "my labs token expired", "connect me to labs". Opens the labs UI to approve a new token, receives it via a localhost callback, and registers a `connect_labs` MCP server in Claude Code via `claude mcp add --scope user`.
Use this skill when iterating on a live pipeline in labs — editing schemas, previewing sample rows, saving changes — via the connect_labs MCP. Triggers on phrases like "add a field to pipeline X", "change the aggregation on", "preview pipeline", "why is pipeline N returning wrong data". Do NOT use for workflow JSX edits (use workflow-author for that).
Add or update environment variables in the AWS ECS Fargate deployment. Use when the user wants to add env vars, secrets, or update task definitions for the labs environment.
| name | deploy-labs |
| description | Deploy the labs environment to AWS via GitHub Actions. Use when the user wants to deploy, release, or push changes to the labs environment. |
dimagi-internal/connect-labsmainDeploy to AWS Labsgh workflow run "Deploy to AWS Labs" -R dimagi-internal/connect-labs --ref main -f run_migrations=false
With migrations:
gh workflow run "Deploy to AWS Labs" -R dimagi-internal/connect-labs --ref main -f run_migrations=true
gh run list -R dimagi-internal/connect-labs --workflow="Deploy to AWS Labs" --limit 1
gh run watch -R dimagi-internal/connect-labs <run_id>
maingit push origin main