PERSISTENT WORK COORDINATION / GitHub community
Workshop coordinator
Coordinates workstreams using shared artifacts, desk journals and structured escalation signals across independent sessions.
“Room coordinator for a multi-agent workshop. Sees all desks, routes work, tracks state, manages journals, and emits coordination signals. Not a desk — the person who sees the whole room.”
01 / THE REASONING
Why this made the selection.
- It uses files and journals to carry state across sessions and treats peer findings as evidence to review.
- The companion desk-open workflow resumes an existing journal instead of overwriting it.
- The profile is a room coordinator: it routes work, reads journals, and emits signals, and it says it is not itself a desk.
- It forbids creating a repository inside an existing git tree, and it says the signal canvas does not load automatically.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- agents/workshop-ta.agent.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable
- workshop-create, desk-open, bench-read, desk-journal and signal-write SKILL.md files (complete)
Our findings
- The five inspected companion skills define workshop scaffolding, desk storage, shared bench reading, journal entries and signal JSON.
- A desk is persistent state, not a process: desk-open creates storage and does not launch an autonomous session.
- The TA coordinates desks. It is not a desk, and another desk's output is input rather than an instruction.
- Creating a workshop may use an existing directory or a new private repository, and the file forbids creating a repo inside another repo.
- The profile names workshop-create, desk-open, bench-read, signal-write, and desk-journal. It does not declare tools, and it says the canvas does not auto-load.
- Partnership signals are stored under desks/_ta so a dashboard scan can see them. Stop, with no output, is allowed.
Not established by this review
- No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Use the role in your project.
- Read the pinned definition and MIT licence; review the host permissions before use.
- Install or review the complete workshop skill context, choose an existing workspace or explicitly authorize new-repository setup, and configure only the needed filesystem/GitHub actions.
- Provide a workshop directory, current journals/artifacts and the work that needs an owner.
Before you start
- Copilot with the companion workshop skills
- An explicit workshop path and scopes for desk artifacts
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/workshop-ta.agent.md
Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE
Supports: Licence and attribution requirements
https://docs.github.com/en/copilot/reference/custom-agents-configuration
Supports: Host setup and permission defaults
- Workshop skill lifecycle ↗Checked
https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/desk-open/SKILL.md
Supports: Storage versus session lifecycle
- Workshop setup paths ↗Checked
https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/workshop-create/SKILL.md
Supports: Local scaffolding versus repository creation
https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/skills/signal-write/SKILL.md
Supports: Signal schema and subjective assessment