interview-domain-bootstrap

Provision paired CommCare HQ project spaces and OCS chatbot instances from domain.yaml.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill interview-domain-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-domain-bootstrap
Source: https://github.com/dimagi-internal/ace/tree/main/skills/interview-domain-bootstrap
Command: npx skills add https://github.com/dimagi-internal/ace --skill interview-domain-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually provisioning paired CommCare HQ project spaces, cross-platform integrations, and OCS chatbot instances for Connect Interviews programs is time-consuming, requires specialized knowledge of multiple systems, and is prone to human error during repetitive configuration steps.

Core Features & Use Cases

  • End-to-end domain provisioning: Automatically creates and links master and downstream CommCare HQ project spaces, configures Connections, Data Forwarding repeaters, UCR-linked Configurable Form Repeaters, Inbound APIs, and lookup tables.
  • OCS bot deployment: Clones the pre-configured Dynamic Router Bot template for the new program, eliminating manual chatbot setup work.
  • Idempotent execution: Checks for existing resources before creating new ones to avoid duplicates, and generates a clear list of remaining manual steps for unautomated configuration tasks.
  • Use case: A product team launching a new Connect Interviews program can run this skill once to set up all required infrastructure in minutes instead of hours of manual work across CommCare, OCS, and Connect platforms.

Quick Start

Use the interview-domain-bootstrap skill to provision a new Connect Interviews project space pair by providing your completed domain.yaml configuration file.

Frequently Asked Questions about interview-domain-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate CommCare project space setup for Connect Interviews?

Automating CommCare project space setup involves using a skill to provision paired domains, configure data forwarding repeaters, UCR-linked repeaters, inbound APIs, and lookup tables from a domain.yaml file.

What is the process for provisioning paired CommCare HQ project spaces?

Provisioning paired CommCare HQ project spaces requires linking a master and downstream domain, applying cross-platform integrations, and deploying an OCS chatbot instance through idempotent execution to prevent duplicate resources.

Can I automatically configure UCR-linked repeaters and lookup tables in CommCare?

Automatically configuring UCR-linked repeaters and lookup tables in CommCare is possible by running an idempotent automation skill that checks for existing resources before applying the repeatable domain configuration.

Does CommCare domain provisioning also handle OCS chatbot deployment?

CommCare domain provisioning can handle OCS chatbot deployment by cloning a pre-configured Dynamic Router Bot template, eliminating manual chatbot setup for new programs.

What are the limitations of automating Connect Interviews domain provisioning?

The limitation of automating Connect Interviews domain provisioning is that not all steps are fully automated; the skill generates an explicit list of remaining manual provisioning steps required to complete the infrastructure setup.

Do I need a domain.yaml file to bootstrap a new Connect Interviews program?

You need a completed domain.yaml configuration file to bootstrap a Connect Interviews program, as it provides the required parameters for the automated, idempotent infrastructure setup across CommCare and OCS platforms.