env-sync-push

name	env-sync-push
description	Push all local environments to the Prime Intellect Environments Hub. Use when environments are out of sync and need to be published.

Environment Sync Push

Running the push

bash skills/env-sync-push/push.sh

The script pushes every environments/*/ directory to the hub in parallel (5 at a time). Environments whose content hash already exists are skipped automatically — only actually changed environments get published.

Prerequisites

• PRIME_API_KEY must be set or configured with prime config set-api-key.
• Configure the destination team with prime config set-team-id <team-id> before pushing. In CI, read the ID from PRIME_TEAM_ID.
• The prime CLI must be installed (uv tool install prime).

What happens during a push

For each environment, prime env push -p environments/<dir> is called. The hub computes a content hash of the environment package:

• Hash matches: the environment is unchanged — the push is a no-op (reported as "skipped").
• Hash differs: a new version is published (reported as "updated").
• Push fails: reported as "failed" with the error output.

Output

The script only reports updated and failed environments. Skipped (unchanged) environments are counted but not listed, keeping the output focused on what actually changed.

When to use

• After merging PRs that modify environments — push the changed envs to the hub.
• After running /env-sync-check and seeing out-of-sync environments.
• As part of a release workflow to ensure all environments are published.