remote-codex-updater

Name: remote-codex-updater
Availability: InStock
Author: Pear

Sync remote Codex skill bundles from the Pear AI GitHub repository.

Updated May 15, 2026

Search Tags:#automation #skill-sync #github-sync #bundle-update #remote-codex #version-gating #codex-orchestrator

Ready to run

npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill remote-codex-updater

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: remote-codex-updater
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/remote-codex-updater
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill remote-codex-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the risk of running outdated remote Codex skill bundles that cause inconsistent behavior across worker, orchestrator, and test automation workflows.

Core Features & Use Cases

Canonical Skill Sync: Pulls the latest approved remote Codex skill bundle directly from the official Pear AI skills GitHub repository to local Codex and Claude skill directories.
Version Validation: Checks the installed bundle version against expected versions to identify stale automation prompts that need to be recreated.
Use Case: For teams running remote Codex automation, run this Skill at the start of every worker, orchestrator, or test invocation to ensure all components use the latest approved skill set and avoid errors from outdated prompts.

Quick Start

Use the remote-codex-updater skill to sync your remote Codex skill bundle and check if your current automation prompts are up to date.

Frequently Asked Questions about remote-codex-updater

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

FAQPage Schema

How do I sync local Codex skills with the remote Pear AI GitHub repository?▼

To sync remote Codex skills, pull the latest approved skill bundle directly from the official Pear AI GitHub repository into local Codex and Claude skill directories to resolve inconsistencies across distributed worker and orchestrator workflows.

Why are my remote Codex worker slots running outdated automation prompts?▼

Worker slots run outdated automation prompts when the installed skill bundle version is stale. Version validation detects these inconsistencies against expected versions and enforces protocol compatibility for queued jobs without disrupting existing execution states.

How do I validate bundle versions for remote Codex test automation workflows?▼

Validate bundle versions by checking the installed remote Codex skill bundle against expected canonical versions to identify stale automation prompts, satisfying version gating requirements before running test automation workflows.

Do I need git and gh installed to run remote Codex skill sync?▼

Yes, git, gh, and python3 are required dependencies to run remote Codex skill sync. These tools enable pulling the latest approved bundle from the Pear AI GitHub repository and applying updates to local skill directories.

When should I run remote Codex skill bundle validation across orchestrator workflows?▼

Run remote Codex skill bundle validation at the start of every orchestrator, worker slot, or test automation invocation to ensure all components use the latest approved skill set and avoid errors from outdated prompts.

What's the best way to enforce protocol compatibility for queued Codex jobs?▼

The best way to enforce protocol compatibility for queued Codex jobs is applying remote skill updates that validate bundle versions and detect stale automation prompts without disrupting existing job execution states.