Menu
Configure Microsoft Teams allowlists for the Agent Bridge Teams channel.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | teams-access |
| description | Configure Microsoft Teams allowlists for the Agent Bridge Teams channel. |
Use this skill when a Teams-connected Claude agent needs to explain or adjust Teams channel access.
The runtime state lives under TEAMS_STATE_DIR, usually <agent-workdir>/.teams.
Important files:
.env: contains TEAMS_APP_ID, TEAMS_APP_PASSWORD, and TEAMS_TENANT_ID.access.json: contains user allowlists and conversation policies.Prefer the deterministic Agent Bridge setup command instead of hand-editing
credentials. Pass the client secret via the BRIDGE_TEAMS_APP_PASSWORD
environment variable (or --app-password-file <path>) so it is not exposed in
shell history or the process table:
BRIDGE_TEAMS_APP_PASSWORD=<secret> agb setup teams <agent> --app-id <app-id> --tenant-id <tenant-id> --allow-from <aad-object-id> --yes
For team channels, require mentions unless the user explicitly asks for every message in the channel to wake the agent:
agb setup teams <agent> --conversation <conversation-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.
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