skills.rest
IgorGanapolsky
IgorGanapolskyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

status

Report latest Codex bridge artifact metadata from the codex-bridge.js status command.

25|7|Updated Mar 3, 2026
Search Tags:#troubleshooting#claude code#agent workflow#status#codex bridge#artifact metadata
One-click install
npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill status-igorganapolsky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/IgorGanapolsky/ThumbGate/tree/main/plugins/claude-codex-bridge/skills/status
Command: npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill status-igorganapolsky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Status lets you quickly verify whether the Claude Code → Codex bridge produced an artifact, so you can avoid re-running the same step or guessing where the output was saved.

Core Features & Use Cases

  • Latest artifact metadata: Shows the most recent bridge run details including mode, timestamp, and exit status.
  • Artifact path visibility: Reports the saved artifact locations so you can find outputs for downstream steps.
  • Use case: When debugging an agent workflow, you can confirm whether the bridge executed successfully and where its results were written.

Quick Start

Ask your agent: Check the latest Codex bridge status and where the latest artifact was saved.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check if the Codex bridge already ran in Claude Code?▼

To check if the Codex bridge ran, execute the codex-bridge.js status command. This reports the latest artifact metadata, including mode, timestamp, and exit status, confirming whether a prior run already happened.

Where are Codex bridge artifacts saved after an agent workflow executes?▼

Codex bridge artifacts are saved to specific file paths reported by the status command. Running codex-bridge.js status reveals these artifact path locations so you can find outputs for downstream steps.

How do I troubleshoot an agent workflow when the Claude Code bridge fails?▼

Troubleshooting an agent workflow bridge failure involves running the status command to verify execution mode and exit status. This metadata helps you decide whether to re-run the bridge or locate the saved outputs.

Can I avoid re-running the Codex bridge if a previous execution succeeded?▼

You can avoid re-running the Codex bridge by checking the latest artifact metadata. The status command reports the timestamp and exit status, allowing you to confirm a successful prior execution before repeating the step.

What metadata does the Codex bridge status command report?▼

The Codex bridge status command reports the latest artifact metadata produced by Claude Code. It summarizes the execution mode, timestamp, exit status, and artifact paths to verify whether a prior run already happened.

When should I verify Codex bridge execution mode during troubleshooting?▼

You should verify Codex bridge execution mode during troubleshooting when deciding to re-run the bridge. Checking the status command output confirms whether a prior run already happened and validates the current agent workflow state.

Related Skills

Explore More Software Engineering Skills→
IgorGanapolskyIgorGanapolsky
25

setup

Validate Codex bridge plugin readiness inside Claude Code.

Community
Basic
NVIDIA-OmniverseNVIDIA-Omniverse
179

content-workflow-convert-to-usd

Convert CAD, mesh, URDF, and MuJoCo assets into OpenUSD format.

Official
Advanced
xfs96192xfs96192

claude-to-im

Bridge Claude Code sessions to Telegram, Discord, Feishu, and QQ.

Community
Advanced
tiankong0101-bytetiankong0101-byte

ask

Route prompts to local Claude, Codex, or Gemini CLIs and store responses as artifacts.

Community
Intermediate