Menu
Configure Mattermost allowlists for the Agent Bridge Mattermost channel.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | mattermost-access |
| description | Configure Mattermost allowlists for the Agent Bridge Mattermost channel. |
Use this skill when a Mattermost-connected Claude agent needs to explain or adjust Mattermost channel access.
The runtime state lives under MATTERMOST_STATE_DIR, usually <agent-workdir>/.mattermost.
Important files:
.env: contains MATTERMOST_URL, MATTERMOST_BOT_TOKEN, and BRIDGE_AGENT_ID.access.json: contains user allowlists and channel policies (dmPolicy, allowFrom, per-channel requireMention and allowFrom).<agent-workdir>/.mcp.json (one level up): registers mattermost-mcp-server for outbound replies.Prefer the deterministic Agent Bridge setup command instead of hand-editing credentials:
agb setup mattermost <agent> --url <mattermost-url> --bot-token <token> --allow-from <user-id> --yes
For team channels, require mentions unless the user explicitly asks for every message in the channel to wake the agent:
agb setup mattermost <agent> --channel <channel-id> --require-mention --yes
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.
Staged canary ladder for taking a freshly-cut Agent Bridge version from tag to full-fleet deploy — VM (connected + disconnected tracks) → dev farm → prod farm → keystone (operator's own box) — verifying per-rung acceptance and iterating (fix → re-cut → re-test) on any failure, then reporting. Use whenever the operator says "테스트해서 릴리즈 해줘" / "test then release" / "roll this cut out to the fleet" / "canary this version", or after any release cut when the version must be validated on real environments before fleet-wide adoption. Encodes the fixed rung order, per-rung acceptance sets, remote-reach mechanics (A2A to each server's own patch — never operator ssh), the autonomy vs operator-gate boundary (prod visibility report, cut/tag/release, keystone confirm-first, unrecoverable-access HOLD), and the hard-won gotchas from the 2026-07-08 v0.17.4 rollout (macOS setsid absence, attached-agent restart-required, self-restart-forbidden, connected-gated fires only when updater-connected, Touch-ID ssh gate).
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·메모리·에스컬레이션을 시작하기 전에 참조한다.