connect-program-setup

Create or reuse Connect programs for ACE opportunities with PDD archetype alignment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually setting up and managing Connect programs for ACE opportunities is time-consuming and error-prone, especially when ensuring program IDs are correctly captured for all downstream lifecycle phases like solicitation creation and opportunity deployment.

Core Features & Use Cases

  • Archetype-matched program creation or reuse: Automatically finds existing Connect programs that match the opportunity's domain and archetype (from the PDD) or creates a new correctly configured program, avoiding mixed-method reporting issues from mismatched program assignments.
  • Idempotent budget headroom validation: Automatically checks and adjusts program budget ceilings to accommodate multiple ACE runs, preventing budget overruns that would block downstream opportunity creation.
  • Durable cross-run program reference storage: Saves the Connect program ID and metadata to a persistent opp.yaml file, so subsequent runs of the same opportunity skip redundant program setup and use the existing program.
  • Use Case: For a new vaccine hesitancy focus group ACE opportunity, this skill automatically creates a correctly named and configured Connect program (or reuses an existing matching one), validates its budget has enough headroom for future runs, and saves its ID so all later phases can access it without manual lookup.

Quick Start

Use the connect-program-setup skill to create or reuse a correctly configured Connect program for your current ACE opportunity and save its ID for all downstream workflow steps.

Frequently Asked Questions about connect-program-setup

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

FAQPage Schema
How do I automate Connect program setup for ACE opportunities?

To automate Connect program setup for ACE opportunities, use this skill to create or reuse programs that match the opportunity's domain and archetype from the PDD. It validates budget headroom and saves the program ID to opp.yaml for downstream lifecycle phases.

How does cross-run persistence work for Connect program IDs?

Cross-run persistence for Connect program IDs works by saving the program ID and metadata to a durable opp.yaml file. Subsequent runs of the same opportunity read this file to skip redundant setup and reuse the existing program configuration.

What is budget headroom validation for ACE program runs?

Budget headroom validation is an idempotent process that checks and adjusts Connect program budget ceilings to accommodate multiple ACE runs. This prevents budget overruns that would otherwise block downstream opportunity creation and deployment.

How do I ensure archetype matching when creating a Connect program?

To ensure archetype matching when creating a Connect program, the skill automatically finds existing programs that match the opportunity's domain and archetype from the PDD. It creates a new correctly named program if no match exists, avoiding mixed-method reporting issues.

Can I reuse an existing Connect program across multiple ACE lifecycle phases?

Yes, you can reuse an existing Connect program across multiple ACE lifecycle phases. The skill captures the program ID into a persistent opp.yaml reference, allowing solicitation creation and opportunity deployment phases to access it without manual lookup.

Why does manual Connect program configuration fail during ACE opportunity deployment?

Manual Connect program configuration fails during ACE opportunity deployment due to time-consuming setup and errors in capturing program IDs for downstream phases. Automating this setup eliminates configuration errors and ensures alignment with PDD archetype requirements.