How agents, skills, connectors and clients fit together
- Agent
- does the work of a workflow step: instructions, a model, the skills it carries and the tools it may call. An internal agent runs in Choregos, under a budget; an external agent is an AI client registered here, whose calls carry its name and limits.
- Skill
- know-how an agent carries — a SKILL.md and its files. A skill grants no right.
- Connector
- an installed instance of a system Choregos reaches OUT to: a directory, a device fleet, an MCP server. Each operation is allowed, needs an approval, or is forbidden. A catalogue lists what the platform offers (MCP servers, connector types); installing one from it makes a connector. A project's delivery tools — tracker, repository, CI, deployment — are set in the project's settings.
- Client
- an AI assistant that reaches IN to Choregos through its MCP door — Claude Code, Cursor, ChatGPT — with its human's access token: their rights, never more, fewer once registered as an external agent. It never decides.
- A client or a tracker opens a work item
- →
- Its workflow hands each step to an agent
- →
- The agent calls connectors under the policy
- →
- A person approves what the policy asks
A supplier's agent that you call over MCP is a connector (an MCP server), not an agent of your registry.