skills.rest
yellow-seed
yellow-seedCOMMUNITY
Explore all skills by this author →
GitHub

sync-codex

Port Dockerfile RUN and ENV steps into portable shell scripts for Codex environments.

2|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/yellow-seed/AgentUsageWidget --skill sync-codex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-codex
Source: https://github.com/yellow-seed/AgentUsageWidget/tree/main/.github/skills/sync-codex
Command: npx skills add https://github.com/yellow-seed/AgentUsageWidget --skill sync-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex environment setup often requires translating Dockerfile steps into portable shell scripts. This Skill provides a repeatable, script-driven setup workflow that removes container-specific hurdles and aligns Codex environments across projects.

Core Features & Use Cases

  • Dockerfile-to-shell porting: Convert RUN and ENV steps into reliable shell script equivalents for Codex.
  • Guided setup steps: Step-by-step instructions to install GitHub CLI, configure the Codex environment, and synchronize skill directories.
  • Use Case: A team wants to re-create a consistent Codex workspace across multiple repos without Docker.

Quick Start

Use the codex setup sequence to initialize a consistent Codex environment:

  • Run the gh-setup script
  • Run the env-setup script
  • Run the skills-setup script

Frequently Asked Questions about sync-codex

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

FAQPage Schema
How do I convert Dockerfile RUN and ENV steps into portable shell scripts for Codex?▼

You can convert Dockerfile steps by porting RUN and ENV commands into reliable shell script equivalents, removing container-specific hurdles and standardizing the Codex environment setup without Docker commands.

What is the best way to set up a consistent Codex environment across multiple repos without Docker?▼

The best way to set up a consistent Codex environment without Docker is using a guided script-driven workflow that runs setup hooks to install CLI tools, configure environments, and synchronize skill directories across teams.

How do I synchronize Codex skill directories across a team?▼

You synchronize Codex skill directories by executing the .codex/hooks/gh-setup.sh, .codex/hooks/env-setup.sh, and .claude/hooks/skills-setup.sh scripts in sequence to align workspaces across projects.

Do I need Docker installed to use this Codex environment setup workflow?▼

No, you do not need Docker installed. This setup workflow specifically targets Codex environments requiring no Docker commands by translating container steps into portable shell scripts.

What prerequisites are needed to run the Codex shell script setup?▼

The prerequisite for running the Codex shell script setup is the presence of the relevant hooks and scripts, specifically .codex/hooks/gh-setup.sh, .codex/hooks/env-setup.sh, and .claude/hooks/skills-setup.sh, to execute the setup across teams.

Related Skills

fabnfabn
1

claude-remote:verify

Verify Claude Code cloud session health by scanning setup scripts and running shell probes.

Community
Advanced
julianobarbosajulianobarbosa
7

Iterm2

Manage iTerm2 and tmux workflows with native -CC integration.

Community
Intermediate
einverneeinverne
119

dotfiles-manager

Organize, sync, and deploy dotfiles across macOS, Linux, and Windows.

Community
Advanced
floxflox
12

flox-containers

Containerize Flox environments into OCI-compatible images for Docker or Podman.

Official
Advanced