agent-bridge-public

Scaffold new internal or external agent workdirs and starter files. Use when an operator needs a repeatable starting point for a new long-lived or disposable agent role.

Call the admin repair role from shell automation and route the result back into queue or channel delivery. Use when cron or another runtime helper needs patch to inspect or repair the bridge.

Use when an injected line matching `[Agent Bridge] event=...` arrives in context, or when wording like "inbox notification", "queue event", "external push", "pushed task", "pending-attention flush", or "nudge from daemon" shows up. Encodes the 7-step external-push routine the receiving Claude/Codex session must follow for daemon-delivered work items. Steps: parse whichever metadata fields are present (`event` is required; `agent`/`count`/`top`/`priority`/`title`/`from` are optional and event-kind-dependent) → `agb show <id>` → decide inline-handle vs delegate (delegate by default) → compose a subagent prompt in own words with explicit acceptance criteria → dispatch via the `Task` tool → verify the subagent's JSON return against those criteria → close with `agb done`, or surface `user_message`, or re-dispatch on failure. Source of truth for the subagent return schema (`files_changed`, `checks_run`, `acceptance_met`, `blockers`, `user_review_needed`, `user_message`).

Create, inspect, update, and delete Agent Bridge native cron jobs with `agb cron`.

Agent Bridge 운영의 단일 진입점(목차/체크리스트). admin·static·dynamic·cron 세션이 "이 상황엔 어느 절차/문서를 따르나"를 한 곳에서 찾도록 한다. 본문은 복사하지 않고 각 canon(SSOT)을 가리킨다. 세션 시작 직후, 그리고 태스크 처리· 업그레이드·릴리즈·handoff·메모리·에스컬레이션을 시작하기 전에 참조한다.

Use when a daemon-filed `[picker]` queue task arrives (an agent stuck on an interactive picker screen the no-LLM detector would not auto-key), or when wording like "stuck picker", "unknown picker", "classify this pane", "extend the picker catalog", or "picker auto-resolve escalation" shows up. Encodes the admin classify→resolve→extend-catalog loop for the

Ship multiple GitHub issues or tracks **in parallel** as 2-4-PR waves. Use whenever the user has multiple open issues/PRs to process, mentions "wave", "Track A/B/C/D", "parallel fixer", "ship these issues", asks to dispatch issue-fix agents, wants codex code review on a complex PR, or describes a backlog they want batched into focused PRs rather than one bundled change. **Parallelism is the default, not the exception** — independent fixers are dispatched in one message with multiple Agent tool calls so they fan out via run_in_background. Captures the field-tested orchestration pattern (brief writing → issue-fixer dispatch into isolated worktrees → codex-rescue review for >300-LOC specialized work or direct orchestrator review for mid-size → squash-merge with structured notes) that has landed 15+ PRs per session with zero regressions on the Agent Bridge repo. Bundles a project-agnostic `issue-fixer` agent and a `general-purpose` fallback dispatch shape so the workflow is portable across Claude Code installs. I

Configure Microsoft Teams allowlists for the Agent Bridge Teams channel.

Configure Mattermost allowlists for the Agent Bridge Mattermost channel.

MANDATORY when an inbox task title begins with `[PERMISSION]`. The admin agent (patch) MUST invoke this skill immediately on any `[PERMISSION] <agent> needs approval for <tool>` task — it parses the escalation body, asks the human operator to approve-once / approve-always / deny, applies the decision to the requesting agent's `settings.local.json` and the origin queue task, and writes a `permission_decision` audit entry. Trigger phrases: `[PERMISSION]`, `permission_escalation_requested`, `needs approval for`, `permission approval`, `approve tool use`.

Use when a conversation, task, or channel message contains durable facts, preferences, decisions, or project context that should be preserved in the agent's markdown-first memory wiki.

Manage structured data in Railway PostgreSQL — emails, calendar events, tasks, facts, reminders, projects, and notifications. Use when tracking emails, scheduling reminders, managing tasks/todos, recording important facts from conversations, syncing calendar events, generating daily digests, or querying historical data.

CRITICAL: When you see '[Agent Bridge]' in any message or context, you MUST use the Bash tool and run the exact `agb inbox` command immediately. This is not optional.