latex-paper-skills: Skill for Codex

Collaborator CLI Health Check

When to use

• Before starting any collaboration workflow that depends on Gemini or Claude Code.
• When diagnosing CLI connectivity or authentication issues.
• After installing or reconfiguring either CLI.

When not to use

• Both CLIs are already confirmed working in the current session.
• The task does not involve cross-agent collaboration.

Inputs

• Current OS environment (auto-detected).

Outputs

• Summary table: Collaborator x CLI / Version / Auth / API / Status.
• Actionable remediation advice for any failed step.

Workflow

Run the Gemini and Claude detection chains in parallel where possible. For each collaborator, execute steps sequentially and short-circuit on the first failure — skip subsequent steps and mark the failure reason.

Step 0: Detect OS

Determine the platform to choose the correct binary-lookup command:

• Windows (win32): use where
• Unix/macOS: use which

Detect via uname -s 2>/dev/null (returns nothing or errors on Windows) or check $OSTYPE.

---

Gemini Detection Chain

1. CLI Exists

# Unix
which gemini
# Windows
where gemini

Pass: command exits 0 and outputs a path. Fail: command not found — suggest: npm install -g @anthropic-ai/gemini-cli or see https://github.com/google-gemini/gemini-cli

2. Version

timeout 15 bash -c 'GEMINI_CLI_NO_RELAUNCH=true gemini --version'

On Windows (no timeout command), run directly:

GEMINI_CLI_NO_RELAUNCH=true gemini --version

GEMINI_CLI_NO_RELAUNCH=true is required to prevent the CLI from hanging.

Pass: output contains a version string (e.g., 0.32.1). Fail: timeout or no version output.

3. Auth

Check for any of the following (any one is sufficient):

1. Environment variable GEMINI_API_KEY is set and non-empty.
2. Environment variable GOOGLE_API_KEY is set and non-empty.
3. File ~/.gemini/oauth_creds.json exists.

[[ -n "$GEMINI_API_KEY" ]] || [[ -n "$GOOGLE_API_KEY" ]]
test -f "$HOME/.gemini/oauth_creds.json"