example-org-coordinator

星标8

分支2

更新时间2026年6月28日 05:46

Single entry point for the example-org engagement — board sync against the example-board GitHub Project, status-report prep for the example-team mandant, documentation routing through the example-docs context, and tenant-aware cloud lookups via example-cloud. Reads field schemas from workflow/projects/example-board.yaml; routes per rules/org/example-routing.md. Trigger: "example-org", "example board", "example-org status", "example-team update", "sync example-org".

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

bks-lab

bks-lab/open-bridge

打开 GitHub 仓库查看创作者相关仓库

下载

Example-Org Coordinator

Org-overlay skill — materializes to skills/example-org-coordinator/SKILL.md in the consumer. Behavioural content: the overlay engine forces a per-file human [y] before this skill is applied. The top-level kind: skill tag and metadata.scope: org are the overlay tripwires; metadata.scope: org keeps it org-internal (never promoted to the CORE/public upstream) and is what scripts/validate-skill-scope.py reads.

What it does

Coordinates every example-org operation behind one trigger so the main session never reaches for raw gh or az commands:

Board — reads field values + state mappings from workflow/projects/example-board.yaml, then drives the board through github-projects-manager (issue creation, field transitions, board queries).
Status reports — collects board state into a weekly update for the example-team mandant (identity/mandants/example-team.yaml).
Docs — routes documentation through the example-docs context (workflow/contexts/example-docs.yaml) and its sync.defaults.
Cloud — resolves tenant ID + token URI from identity/accounts/example-cloud.yaml before any cloud op; never hardcodes.

Conventions

Never set a board item to "Done" directly — "In Review" first, human confirms.
Always use the exact Status option strings declared in the project config.
Follow rules/org/example-routing.md; on conflict with a CORE rule, the CORE rule wins.

同仓库更多 Skills

同仓库

bridge-contribute

bks-lab/open-bridge

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".

2026-07-188

bridge-dashboard

bks-lab/open-bridge

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".

2026-07-188

bridge-leak-check

bks-lab/open-bridge

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".

2026-07-188

bridge-onboard

bks-lab/open-bridge

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".

2026-07-188

bridge-overlay

bks-lab/open-bridge

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".

2026-07-188

bridge-promote

bks-lab/open-bridge

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".

2026-07-188

name	example-org-coordinator
kind	skill
description	Single entry point for the example-org engagement — board sync against the example-board GitHub Project, status-report prep for the example-team mandant, documentation routing through the example-docs context, and tenant-aware cloud lookups via example-cloud. Reads field schemas from workflow/projects/example-board.yaml; routes per rules/org/example-routing.md. Trigger: "example-org", "example board", "example-org status", "example-team update", "sync example-org".
metadata	{"scope":"org","tools":["Bash","Read","Glob","Grep"]}

Example-Org Coordinator

What it does

Coordinates every example-org operation behind one trigger so the main session never reaches for raw gh or az commands:

Board — reads field values + state mappings from workflow/projects/example-board.yaml, then drives the board through github-projects-manager (issue creation, field transitions, board queries).
Status reports — collects board state into a weekly update for the example-team mandant (identity/mandants/example-team.yaml).
Docs — routes documentation through the example-docs context (workflow/contexts/example-docs.yaml) and its sync.defaults.
Cloud — resolves tenant ID + token URI from identity/accounts/example-cloud.yaml before any cloud op; never hardcodes.

Conventions

Never set a board item to "Done" directly — "In Review" first, human confirms.
Always use the exact Status option strings declared in the project config.
Follow rules/org/example-routing.md; on conflict with a CORE rule, the CORE rule wins.