Skip to the rows

agentsclimarketplace

Agent bus diagnose

Skill adjcjh777/agent-bus-skills/skills/agent-bus-diagnose

Codex Agent Bus skill family for local multi-agent coordination

Install

npx -y skills add adjcjh777/agent-bus-skills --skill agent-bus-diagnose

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Diagnose Agent Bus setup, registry, inbox, trigger, and delivery failures. Use when Agent Bus registration, list, inbox, send, resume, codex_app, pending-target claiming, ACK, reply, team dispatch, or visible delivery appears stuck, missing, ambiguous, or inconsistent.

SKILL.md

3.1 KB, 680 tokens by cl100k_base, as published. Nobody here has run it

Agent Bus Diagnose

Use this skill for read-mostly diagnosis of Agent Bus state and delivery failures.

Safety

Do not read Codex auth files, API keys, transcripts, or unrelated private state.
Do not edit ~/.codex/config.toml during diagnosis.
Do not expose unrelated message contents. Report only the identifiers and snippets needed for the issue.
Prefer read-only checks first.

Diagnostic Workflow

Establish scope.
- Confirm current cwd.
- Identify CODEX_AGENT_BUS_HOME or default to ~/.codex/agent-bus.
- Check whether ~/.codex/tools/codex-agent-bus/bin/agent-bus exists.
Run preflight when registration setup is suspect:

python3 ~/.codex/skills/agent-bus-register/scripts/register_self.py --preflight

Check Bus health and registry:

~/.codex/tools/codex-agent-bus/bin/agent-bus health
~/.codex/tools/codex-agent-bus/bin/agent-bus list

Check the relevant inbox when a target is known:

~/.codex/tools/codex-agent-bus/bin/agent-bus inbox --target <session_id_or_alias> --unread-only --limit 10

Inspect only recent relevant message metadata when a send or ACK is missing:

tail -n 20 ~/.codex/agent-bus/messages.jsonl

Filter the result mentally or with safe text tools to the relevant message_id, correlation_id, from_agent, to_session_id, target_query, pending_target, status, and timestamps.

Common Findings

CLI missing: global Agent Bus install is incomplete. Show the install command if the tool or preflight suggests one, but do not run it automatically.
No current session record: rerun $agent-bus-register with a real /status session id or open a fresh Codex session after enabling hooks.
Pending target not claimed: ensure the later session registers with the intended role alias, tag, or compatible cwd.
Message queued but not visible: Bus storage worked, but Codex-side visible delivery is unconfirmed.
codex_app missing or returned only a transport payload: call the available Codex App thread tool with the returned thread id and prompt, then require ACK/reply for proof.
resume or codex_app hung: stop parallel retries, preserve the canonical message_id, and route recovery through $agent-bus-delegate.
Ambiguous agent name: resolve by session_id; treat agent_id as a role hint only.

Recovery Guidance

For registration fixes, route to $agent-bus-register.
For resend, ACK, or reply, route to $agent-bus-delegate.
For role/team state, route to $agent-bus-team.
If the user says they cannot see a delegated task, treat it as a real visible-delivery failure until a target ACK or visible send result proves otherwise.

Use precise wording:

Bus storage is healthy, visible thread delivery failed or is unconfirmed.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.