agentsclimarketplace

Example org coordinator

Skill bks-lab/open-bridge/examples/overlay-example/tree/skills/example-org-coordinator

Your AI coding agent starts every session knowing your repos, your clients, and how you work — a plain git repo of markdown + YAML it reads at session start, independent of model or frontend. Context compounds instead of restarting. MIT.

Install
npx -y skills add bks-lab/open-bridge --skill example-org-coordinator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.0 KB, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.