sweep-live-set

Parse opp.yaml and run_state.yaml files to generate a timestamped live-set.yaml artifact.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical problem of incorrectly flagging active ACE opportunity identifiers as orphans during system sweeps, which occurs when there is no centralized reference of which identifiers are still in use across all active opportunities.

Core Features & Use Cases

  • Cross-opp Identifier Aggregation: Collects and merges identifier data from all active ACE opportunity directories stored in Google Drive.
  • Sweep Safety Reference: Produces a timestamped live-set artifact that all per-system sweep operations use to filter out active resources from orphan candidate lists.
  • Use Case: Before running a sweep of CommCareHQ resources to identify unused assets, use this Skill to generate the current live set so only truly abandoned resources are flagged for cleanup.

Quick Start

Use the sweep-live-set skill to generate a current live set of active ACE opportunity identifiers before running any system sweep.

Frequently Asked Questions about sweep-live-set

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

FAQPage Schema
How do I prevent false orphan detection during ACE system sweeps?

To prevent false orphan detection during ACE system sweeps, generate a cross-opportunity live set of active identifiers. This merged, timestamped reference filters out active resources from orphan candidate lists across all per-system sweep operations.

How do I aggregate active opportunity identifiers across Google Drive for ACE cleanup?

Aggregate active opportunity identifiers by parsing opp.yaml and run_state.yaml files from ACE Drive opportunity directories. This process merges the parsed data into a single timestamped live-set.yaml artifact for sweep operations.

Do I need to generate a live identifier set before sweeping CommCareHQ resources?

Yes, generating a current live identifier set is a prerequisite before sweeping any ACE lifecycle system, including CommCareHQ. It ensures only truly abandoned resources are flagged for cleanup by providing a safety reference.

Which ACE environments are covered by cross-opportunity identifier aggregation?

Cross-opportunity identifier aggregation applies to all ACE lifecycle operations across Drive, Connect, Open Chat Studio, CommCareHQ, and Connect Labs environments, ensuring comprehensive sweep safety wherever unused resources need identifying.

What is the purpose of a live-set.yaml artifact in opportunity management?

A live-set.yaml artifact serves as a centralized, timestamped sweep safety reference in opportunity management. It consolidates active identifiers from all active opportunities so per-system sweep operations can accurately distinguish used resources from orphans.

Why are active ACE resources being incorrectly flagged as orphans during sweeps?

Active ACE resources are incorrectly flagged as orphans during sweeps when there is no centralized reference of active identifiers. Building a cross-opportunity live set solves this by providing a merged reference to filter out active resources.