菜单
Channel management — messaging integrations overview, health checks, deployments, start/stop services. Reads infra/channels/*.yaml for channel definitions. For scheduled tasks / cron jobs: use the /schedule skill instead. Trigger: "/channel", "channel status", "channel health", "channel deploy", "start channel", "stop channel".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Contribute features and improvements from your Bridge back to the open-bridge OSS upstream (or your org overlay) as a fork-based pull request. Scans your user branch for upstream-worthy files, classifies them by scope, adapts org-specific content, runs the MANDATORY two-layer content-safety gate (leak scanner + per-repo blocklist, refuses on PII/customer hits), and opens the cross-fork PR with DCO sign-off — no upstream push access needed. Trigger: "/contribute", "contribute", "upstream contribution", "contribute to upstream", "contribute upstream", "submit improvement", "share my skill", "send this to open-bridge", "PR to upstream", "PR to overlay", "give back", "submit a feature".
Generates the Bridge Control Center — a single-file HTML dashboard that bundles Fleet (infra/remotes/), Work Board, Calendar (next 24h), Channels, Git activity, optional Bridge-Deck /metrics, and upstream drift into one view. Stands alone; the pixel-art Bridge-Deck renderer it can complement is not yet public (coming soon). Trigger: "/bridge-dashboard", "bridge dashboard", "control center", "ops dashboard", "open dashboard", "show me everything at a glance".
Content-leak scanner with categorized classification. Different from a raw blocklist grep: each hit is sorted into legitimate-self-reference, legitimate-sister-repo, personal-PII (always leak), or internal-vocabulary hardcoded (OSS-strict only). Use after a sync to verify the destination is actually clean — catches pre-existing leaks the source-side scan won't see. Also runs OSS-strictness vocabulary checks (e.g. "scope: bks" hardcoded in OSS-shipped skill docs that should use "scope: org" placeholder). Trigger: "/bridge-leak-check", "leak scan", "leak check", "OSS readiness", "pre-existing leaks", "cleanliness check", "is this OSS clean".
New user onboarding and reconfiguration — discovery-driven setup with permission-gated system scan, evidence-based feature suggestions, and a read-only catalogue of what else Bridge can do. Six-phase wizard (Identity / Discovery / Suggestions / Quick-Wins / Catalog / Validate) with re-entry modes for targeted later activation. Works without GitHub. Upstreams stay empty by default and wire later when the OSS upstream or your own upstream is live. Trigger: "/bridge-onboard", "onboard", "setup", "configure bridge", "new user", "ecosystem scan", "set up bridge", "reconfigure", "reconfigure bridge", "setup wizard".
Subscribe a Bridge to an ORG OVERLAY — a git repo an organisation publishes that ships its shared config (contexts, projects, mandants, accounts, org skills/agents/standing-orders, an ecosystem fragment) as a flat mirror tree. /overlay add <git-url> sparse-clones the overlay, validates its manifest, previews a per-file plan with risk flags, and materializes COPIES into your repo under a lockfile — never block-merging your config, never clobbering your edits (3-way merge), never touching CORE. sync/apply/status/diff/remove/list manage the subscription over time. The overlay is the LOWER layer; your user files always win. Trigger: "/overlay", "org overlay", "subscribe to overlay", "materialize org config", "pull org overlay", "unsubscribe overlay", "add org config by git url", "list overlays", "overlay status", "overlay diff".
Promote CORE changes from your user branch to upstream (Scope-Routing per scope: core → OSS upstream, org → your org overlay, user → local). Analyzes commits, categorizes by CORE/USER/ORG path+frontmatter rules, runs mandatory content-safety checks per repo (leak scanner + blocklist, refuses on PII/customer hits), and creates fork-based PRs to upstream repos — no upstream push access needed. For file-level community contributions with adaptation, use the bridge-contribute skill (/contribute) instead. Trigger: "/bridge-promote", "promote", "cherry-pick", "push to upstream", "promote to upstream", "promote commits".
| name | channel |
| description | Channel management — messaging integrations overview, health checks, deployments, start/stop services. Reads infra/channels/*.yaml for channel definitions. For scheduled tasks / cron jobs: use the /schedule skill instead. Trigger: "/channel", "channel status", "channel health", "channel deploy", "start channel", "stop channel". |
| metadata | {"scope":"core"} |
Manage messaging channels (imessage, email, telegram, whatsapp, signal, teams) and their runtime services. Read the referenced file ONLY when triggered.
| Concern | Owner |
|---|---|
| Channel inventory, health, deploy, start/stop | This skill |
| Scheduled messages, cron/launchd/systemd jobs | /schedule skill |
| Recipient groups for those messages | /mandants skill |
When the user asks about a scheduled message ("compliment for Mom",
"weekly-digest", cron timing) route to /schedule. Channel management
is the transport layer; scheduling is a separate concern.
| Argument | Effect | Default |
|---|---|---|
(none) | Channel overview | — |
{name} | Detail view of one channel | — |
health | Health check all channels | — |
deploy {name} | Deploy channel service | — |
start/stop/restart {name} | Service control | — |
User wants to...
├── Channel overview / status → Read references/workflow.md (§ Overview)
├── Channel health check → Read references/workflow.md (§ Health Check)
├── Start/stop a channel → Read references/workflow.md (§ Start/Stop)
├── Deploy channel services → Read references/workflow.md (§ Deploy)
├── Scheduled messages / cron jobs → Delegate to `/schedule` skill
├── Recipient group management → Delegate to `/mandants` skill
└── Questions about channels → Answer from this file