Individual skill

example-org-coordinator

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

examples/overlay-example/tree/skills/example-org-coordinator/SKILL.md

Read pinned source

Source commit 2554bda8eeb2d55671e922c31484905fc8c67af9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
13
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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:
Back to top