env-sync-push

Publish changed local environment packages to the Prime Intellect Environments Hub.

113|35|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/PrimeIntellect-ai/research-environments --skill env-sync-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-sync-push
Source: https://github.com/PrimeIntellect-ai/research-environments/tree/main/skills/env-sync-push
Command: npx skills add https://github.com/PrimeIntellect-ai/research-environments --skill env-sync-push

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the tedious, error-prone process of manually publishing environment changes by batch-pushing local environment packages to the Prime Intellect Environments Hub.

Core Features & Use Cases

  • Parallel environment publishing: Pushes all environments/*/ packages with a configurable concurrency level (5 at a time).
  • Content-hash based skipping: Automatically skips environments whose hub content hash already exists, avoiding redundant publishes.
  • Actionable reporting: Reports only updated and failed environments (while still counting skipped ones in the summary), keeping output focused on what changed.

Use case example: After merging PRs that modify multiple environments, run this Skill to publish only the environments that actually changed, while leaving unchanged ones as no-ops.

Quick Start

Run this command to push local environment updates to the Prime Intellect Environments Hub: bash skills/env-sync-push/push.sh

Frequently Asked Questions about env-sync-push

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

FAQPage Schema
How do I batch publish multiple local environment packages to the hub after a merge?

Batch publishing local environment packages uses a script to push all `environments/*/` directories to the Prime Intellect Environments Hub. It processes up to 5 directories concurrently, reporting only updated and failed results while skipping unchanged ones.

How does content-hash detection skip unchanged environments during deployment?

Content-hash detection compares local environment packages against existing hub content hashes. If a matching hash is found, the environment deployment is skipped as a no-op, avoiding redundant publishes and reducing workflow execution time.

Do I need the Prime CLI to push environment updates to GitHub environments?

Yes, the Prime CLI is required to push environment updates to the hub. You must also configure a destination team ID before executing the batch publishing script for your release workflow.

What is the best way to synchronize out-of-sync local environments for a CI release workflow?

Running a batch synchronization script pushes all modified `environments/*/` packages to the hub simultaneously. It leverages content-hash detection to publish only changed environments, making it ideal for post-merge maintenance.

Why does the environment deployment script only report updated and failed results?

The deployment script reports only updated and failed environments to keep output focused on actionable changes. Skipped environments are counted in the summary but omitted from the main output to reduce noise during batch publishing.

Can I use this batch publishing method if my environment directories have no changes?

Yes, running the script on unchanged directories is safe. Content-hash detection identifies matching hashes and skips those environments, executing no operations while still providing a summary count of skipped items.