app-release-eval

Grade release completeness of Learn and Deliver app builds across four weighted dimensions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unreleased Learn and Deliver app builds silently break downstream Connect workflows by producing empty deliver unit lists, requiring time-consuming manual debugging to resolve.

Core Features & Use Cases

  • 4-dimension weighted grading: Evaluates release completeness across both apps released, CCZ marker integrity, build ID traceability, and Connect deliver unit enumerability.
  • Edge case handling: Detects and accounts for known CCZ regex false positives in the upstream app-release step to avoid incorrect scoring.
  • Use Case: For ACE Connect opportunity teams, use this skill immediately after the app-release phase to confirm all builds are properly released and ready for the Sync Deliver Units step.

Quick Start

Use the app-release-eval skill to verify that both Learn and Deliver app builds for your current Connect opportunity are fully released and unblock downstream deliver unit synchronization.

Frequently Asked Questions about app-release-eval

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

FAQPage Schema
Why are deliver units empty in CommCare Connect after an app release?

Empty deliver units in CommCare Connect occur when Learn and Deliver app builds are not fully released. Verifying release completeness across build traceability and CCZ markers detects these gaps to unblock downstream synchronization.

How do I verify CommCare Connect app release completeness before syncing deliver units?

You verify app release completeness by grading both Learn and Deliver builds across four weighted dimensions: release status, CCZ marker integrity, build ID traceability, and Connect deliver unit enumerability.

What causes CCZ marker false positives during the app-release phase?

CCZ marker false positives occur when upstream app-release regex matching incorrectly flags builds as released. The evaluation accounts for these known false positives to avoid incorrect release grading scores.

Can I detect build ID mismatches between Learn and Deliver apps before Connect processing?

Yes, build ID traceability is evaluated as one of the four weighted dimensions to detect mismatches between Learn and Deliver app builds, ensuring proper release readiness before downstream Connect workflows.

When should I run an app release evaluation for ACE Connect opportunity workflows?

You should run an app release evaluation immediately after the app-release phase and before the Sync Deliver Units step to confirm all builds are properly released and ready for downstream Connect processing.

What are the limitations of relying on CCZ markers for release grading?

CCZ markers can produce false positives in the upstream app-release step, leading to incorrect scoring. The evaluation detects these edge cases but requires both Learn and Deliver builds to be present for complete grading.