Agent · Conductor

AGENT PROFILE · CONDUCTOR

Conductor

Conductor is the coordination role named in Tinker's instructions: the agent that manages a larger piece of work across other agents. The role has evidence; a public original prompt does not.

Referenced role, original not recovered

Tinker's bundled prompt refers to “Conductor's job once it exists”. The searched public agent paths and history did not yield a full Conductor file. That is a bounded search result, not proof that nobody ever wrote one.

What we can establish

Berd's orchestrator skill supplies an operational approach to coordinating sessions while keeping one conversation available. It is a skill, not the missing persona.

Goose's recovered Solo and Buzz's example Skip are concrete coordination designs. Neither establishes that Conductor had the same voice, rules or ancestry. Goose's article about acting as a conductor describes a workflow pattern, not a recovered named agent.

If you already have a Conductor

Keep its approved local instructions as the authority for that agent. Do not replace them with Solo or Skip merely because those originals are recoverable. Compare specific choices instead: who owns the plan, how results return, who can write which files, and when the coordinator must ask you.

A personal Conductor created after the research is a new design. It is not automatically a recovered historical prompt or part of the public bundle.

Learn more

• Missing agents
• Tinker
• Skills found in the code archaeology

Agent prompt

Not recovered. There is not enough evidence to publish an original Conductor prompt. This page deliberately contains no invented replacement and does not reproduce a personal agent file.

Verified

Source history · 2026-09-19