ワンクリックでManusで任意のスキルを実行

agent-bridge-runtime

スター3

フォーク5

更新日2026年4月6日 20:42

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

seanssoh

seanssoh/agent-bridge-public

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

When This Skill Triggers

You receive a message starting with [Agent Bridge]
Stop hook additionalContext mentions inbox, queued tasks, or agb inbox
Any context includes "queued tasks waiting", "inbox", or task references like next: #<id>

Required Actions (Mandatory)

When triggered, immediately execute the following. Do NOT just acknowledge with "got it", "understood", or any conversational reply. Use the Bash tool first.

Use the Bash tool and run exactly ~/.agent-bridge/agb inbox <your-agent-name>
If queued tasks exist, run ~/.agent-bridge/agb show <task-id> for the first one
Claim it: ~/.agent-bridge/agb claim <task-id> --agent <your-agent-name>
Do the work described in the task
Complete it: ~/.agent-bridge/agb done <task-id> --agent <your-agent-name> --note "summary"

If the nudge message contains Run exactly: ..., execute that command before any analysis or reply.

Cron Followup Tasks

When you receive a [cron-followup] task:

Read the summary and findings
Post a report to your Discord or Telegram channel — this is mandatory, not optional
If recommended_next_steps includes DM targets, send those DMs
Mark done with a note of what you reported

Cron followups exist so YOU can report results to your channel. If you just "done" the task without posting, the cron result is invisible to users.

Task Completion Rules

agb done 전에 반드시 결과를 전달해야 한다 (채널 메시지, 요청자에게 task create 등)
--note 없는 done은 금지. 무엇을 했는지 반드시 기록
[cron-followup]의 needs_human_followup=true면 반드시 채널에 포스팅 후 done
인프라 장애 감지 시 agent-bridge urgent <configured-admin-agent> "..." 에스컬레이션 필수

Prohibited

Responding to [Agent Bridge] with just "acknowledged", "noted", or "Cooking..." without running inbox — FORBIDDEN
Closing a cron-followup without posting to your channel — FORBIDDEN
Skipping inbox check — FORBIDDEN
Assuming inbox is empty without running the command — FORBIDDEN
Using bridge-task.sh, sqlite queries, or filesystem searches instead of agb CLI — FORBIDDEN
Running agb done without delivering results to the requester — FORBIDDEN
Running agb done without --note — FORBIDDEN

Queue Source of Truth

Live queue: ~/.agent-bridge/state/tasks.db
Never read ~/agent-bridge/state/tasks.db (repo copy)
Never infer queue state from memory or prior conversation

Example

~/.agent-bridge/agb inbox <your-agent-name>
~/.agent-bridge/agb show <task-id>
~/.agent-bridge/agb claim <task-id> --agent <your-agent-name>
# ... do the work / post report to channel ...
~/.agent-bridge/agb done <task-id> --agent <your-agent-name> --note "summary of what was done"

このリポジトリの他の Skills

同じリポジトリ

agent-factory

seanssoh/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.

2026-07-103

patch

seanssoh/agent-bridge-public

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.

2026-06-263

external-push-handling

seanssoh/agent-bridge-public

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`).

2026-06-183

cron-manager

seanssoh/agent-bridge-public

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

2026-06-133

agent-bridge-operating-manual

seanssoh/agent-bridge-public

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

2026-06-123

picker-resolve

seanssoh/agent-bridge-public

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

2026-06-103

~/.agent-bridge/agb inbox <your-agent-name> ~/.agent-bridge/agb show <task-id> ~/.agent-bridge/agb claim <task-id> --agent <your-agent-name> # ... do the work / post report to channel ... ~/.agent-bridge/agb done <task-id> --agent <your-agent-name> --note "summary of what was done"

name	agent-bridge-runtime
description	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.