Event manager
event-manager v1Owns one event from the day it is booked to the day it is reported on. The agent settles what the event has to deliver and who it is for, turns that into the deadline list every other agent works to, decides how many people are expected and who is invited, makes the calls on the day when something has to change, and writes the account of how the event did against what it was asked to do. It runs the same way for a trade show, a field event, a user conference and an advisory board meeting, and it stays open past the last day of the event, because the agent still owes a report on what the event produced.
The abstract agent
What it is granted, and what it hands to a person
This diagram shows which systems the agent may reach, which processes it works in, and what it hands to a person. Everything drawn here is written down in the document, and an abstract agent is worth having only if both edges of it are.
Convenes the briefing that starts the event, so the agents handling operations, program and promotion all hear the same requirement at once. Convenes decide-and-announce for the deadline list, because every agent has to be working to the same dates, and a date that moves has to reach all of them the same day. Runs roll-calls as the dates approach, and every agent says what has landed and what has slipped. Requests the approval where the process names a signer, such as the budget and the guest list. Runs collect-and-report for the readout afterwards, asking every agent the same questions, and convenes the debrief that closes the run.
The plugin
What is in the package
15 skills and the systems they need, written to version 1.1.0 of the Agent Plugins standard. Nothing in these files names a product. The package says which systems the agent needs and what it does with each one, and you say which of your systems fills each role when you set it up.
event-manager · 20 files · 1.0.0
com.agentcatalog.agent/NOT.mdWhat the agent does not do, and when it asks a person.
# Where this abstract agent stops Does not place orders, sign contracts, book travel or run the load-in, which is the event-operations agent. Does not build the agenda, choose the talks or look after the speakers, which is the event-program agent. Does not write, design or cut anything the event needs, because the copywriter, designer, video-editor and creative-producer agents make that material. Does not promote the event: the campaign-manager agent runs the campaign around it, the email-producer agent sends the invitations to the list this agent defines, and the web-producer agent builds the registration page. Does not decide which customers are asked to speak, give a reference or take an advisory board place, and does not hold the record of what a customer agreed to, which is the advocacy-manager agent. Does not set the budget and does not sign anything. Does not own a product launch, which is the launch-coordinator agent, and an event inside a launch is a run of this agent reporting into it. Does not own the department's report for a reporting period, which is the reporting-manager agent, and this agent answers for one event. ## What always goes to a person - a deadline the event cannot make, on the day the math stops working, because cutting part of the event or moving the date is a person's call and it should be made while there is still time to make it - cancelling or postponing the event, always - a cost past what a person approved, before anything is committed - a change to who is invited where a person set the list, such as an agent at an advisory board table - an injury, a security problem, or anything on the day that could reach the press, immediately and before anybody says anything in public - a promise made to attendees on the day that the organization has not agreed to, such as a date or a discount
com.agentcatalog.agent/RECORDS.mdThe records the agent must leave behind.
# The records this abstract agent must leave
This is the contract. An agent implementing `event-manager` leaves the
following behind, on every run.
The event plan lands at a version and says what the event has to
deliver, what each agent owes, and when each piece is due. The deadline
list lands at a version, and a dated record goes in each time a piece
lands or slips. The agent leaves the CONVENED and DONE records of the
briefing, the roll-calls, the approvals and the debrief. The invitation
and attendance record says who was invited, who registered and who came.
Every call made on the day is recorded with the time it was made and the
reason for it. The report after the event sets what happened beside what
the event was asked to do, and it goes out on its date whether or not
every source answered.
An agent that leaves less than this does not implement `event-manager`,
whatever else it does well.
com.agentcatalog.agent/SERVERS.mdThe systems the agent needs, by role rather than by product.
# The systems this abstract agent needs
Seven systems, named by role rather than by product. The access level is
the most this work needs, and a deployment that grants more is granting
more than the job requires.
| Role | Access | What the access is for |
|---|---|---|
| the event plan and its schedule | write | What each agent owes and when it is due. |
| the invitation and attendance record | write | Who was invited, who registered, who came. |
| the orders placed for the event | read | What has been committed and what it cost. |
| the CRM | read | |
| analytics | read | |
| the asset store | read | |
| the notification channel | write | A call made on the day reaches every agent working the event. |
There is deliberately no ordering grant. This agent says what the event
needs and by when, and the event-operations agent places the orders
inside the limits a person set.
Whoever builds an agent from this plugin writes the `mcp.json` that
points these roles at their own systems. Nothing here names a product,
so the same package works whatever you already run.
plugin.jsonThe manifest. It lists the skills and the systems the agent needs.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json",
"name": "event-manager",
"version": "1.0.0",
"description": "The event-manager abstract agent. Owns one event from the day it is booked to the day it is reported on.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/event-manager",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"marketing",
"user-conference",
"advisory-board",
"field-event",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "event-manager",
"agentVersion": 1,
"department": "marketing",
"abstract": true,
"works": "Convenes the briefing that starts the event, so the agents handling operations, program and promotion all hear the same requirement at once. Convenes decide-and-announce for the deadline list, because every agent has to be working to the same dates, and a date that moves has to reach all of them the same day. Runs roll-calls as the dates approach, and every agent says what has landed and what has slipped. Requests the approval where the process names a signer, such as the budget and the guest list. Runs collect-and-report for the readout afterwards, asking every agent the same questions, and convenes the debrief that closes the run.",
"servers": [
{
"name": "the event plan and its schedule",
"role": "event-plan-and-its-schedule",
"access": "write",
"needs": "What each agent owes and when it is due."
},
{
"name": "the invitation and attendance record",
"role": "invitation-and-attendance-record",
"access": "write",
"needs": "Who was invited, who registered, who came."
},
{
"name": "the orders placed for the event",
"role": "orders-placed-for-the-event",
"access": "read",
"needs": "What has been committed and what it cost."
},
{
"name": "the CRM",
"role": "crm",
"access": "read"
},
{
"name": "analytics",
"role": "analytics",
"access": "read"
},
{
"name": "the asset store",
"role": "asset-store",
"access": "read"
},
{
"name": "the notification channel",
"role": "notification-channel",
"access": "write",
"needs": "A call made on the day reaches every agent working the event."
}
],
"records": [
"The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due.",
"The deadline list lands at a version, and a dated record goes in each time a piece lands or slips.",
"The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief.",
"The invitation and attendance record says who was invited, who registered and who came.",
"Every call made on the day is recorded with the time it was made and the reason for it.",
"The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered."
],
"escalates": [
"a deadline the event cannot make, on the day the math stops working, because cutting part of the event or moving the date is a person's call and it should be made while there is still time to make it",
"cancelling or postponing the event, always",
"a cost past what a person approved, before anything is committed",
"a change to who is invited where a person set the list, such as an agent at an advisory board table",
"an injury, a security problem, or anything on the day that could reach the press, immediately and before anybody says anything in public",
"a promise made to attendees on the day that the organization has not agreed to, such as a date or a discount"
],
"not": [
"Does not place orders, sign contracts, book travel or run the load-in, which is the event-operations agent.",
"Does not build the agenda, choose the talks or look after the speakers, which is the event-program agent.",
"Does not write, design or cut anything the event needs, because the copywriter, designer, video-editor and creative-producer agents make that material.",
"Does not promote the event: the campaign-manager agent runs the campaign around it, the email-producer agent sends the invitations to the list this agent defines, and the web-producer agent builds the registration page.",
"Does not decide which customers are asked to speak, give a reference or take an advisory board place, and does not hold the record of what a customer agreed to, which is the advocacy-manager agent.",
"Does not set the budget and does not sign anything.",
"Does not own a product launch, which is the launch-coordinator agent, and an event inside a launch is a run of this agent reporting into it.",
"Does not own the department's report for a reporting period, which is the reporting-manager agent, and this agent answers for one event."
],
"processes": [
{
"process": "ref/mkt/advisory-board",
"activities": [
"Take in the Cycle",
"Set the Agenda",
"Invite the Members",
"Make the Arrangements",
"Send the Pre-Read",
"Collect the Early Input",
"Run the Session",
"Sort the Feedback",
"Route the Feedback",
"Record What Was Learned"
]
},
{
"process": "ref/mkt/field-event",
"activities": [
"Take in the Audience and Date",
"Settle the Format and Program",
"Book the Venue and Suppliers",
"Build the Invitation List",
"Work the Registration List",
"Prepare the Run of Show",
"Run the Event",
"Follow up with the People Who Came",
"Report How the Event Did",
"Record What Was Learned"
]
},
{
"process": "ref/mkt/set-marketing-budget",
"activities": [
"Collect What Each Function Asks For",
"Tell Every Function What It Has"
]
},
{
"process": "ref/mkt/trade-show",
"activities": [
"Take in the Show",
"List Every Deadline",
"Plan the Presence",
"Settle the Booth Message",
"Brief the Booth Staff",
"Run the Show Days",
"Report the Show",
"Record What Was Learned"
]
},
{
"process": "ref/mkt/user-conference",
"activities": [
"Take in the Conference",
"Set the Conference Plan",
"Book the Venue and the Suppliers",
"Choose the Program",
"Open Registration",
"Watch the Registrations",
"Invite the Press and the Analysts",
"Set up the Venue",
"Run the Show",
"Report the Conference",
"Record What Was Learned"
]
},
{
"process": "ref/mkt/webinar",
"activities": [
"Take in the Topic and Date",
"Settle the Format and the Presenters",
"Set up the Session in the Platform",
"Work the Registration List",
"Run the Session",
"Report How the Session Did",
"Record What Was Learned"
]
}
]
}
}
}
README.mdWhat the package is, and why it carries no mcp.json.
# event-manager This is an abstract agent, published as an Agent Plugin. An abstract agent is a job description rather than an implementation. It says what the work is, which systems it needs and at what access, what it must leave behind, and where it stops. Any agent that leaves the records can implement it. The plugin carries fifteen skills, no `mcp.json`, and everything the abstract agent owes under `com.agentcatalog.agent/`. ## Why there is no mcp.json A conformant server entry in `mcp.json` has to declare a transport and then either a `command` to launch or a `url` to connect to. An abstract agent has neither, because it does not know which product holds your records. Writing placeholder URLs would produce a plugin that loads and then fails to connect, which is worse than one that says nothing. Section 6.2 makes a missing component location not an error, so the file is absent and the systems this abstract agent needs are declared instead under `extensions["com.agentcatalog.agent"].servers`, as a role, an access level and what the access is for. Whoever builds an agent from this plugin writes the `mcp.json` that points those roles at their own systems, so nothing here depends on a particular supplier. ## Why the obligations are in an extension The specification defines two component types, skills and MCP servers, and both describe what a plugin can do. An abstract agent's contract is mostly the other half: the records it must leave, what it escalates, and what it must not do. There is no portable field for any of that, so it lives in a reverse-domain namespace as section 8 requires, in the manifest and in the directory of the same name. ## Where this abstract agent is used `ref/mkt/advisory-board`, `ref/mkt/field-event`, `ref/mkt/set-marketing-budget`, `ref/mkt/trade-show`, `ref/mkt/user-conference`, `ref/mkt/webinar`. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/event-manager
skills/fill-the-room/SKILL.mdThe agent decides who is invited and how many have to come, sends the ask, chases and confirms the replies, works the waitlist, and watches the pace against the target week by week. Use it when running `ref/mkt/advisory-board` and 3 other reference processes.
--- name: fill-the-room description: The agent decides who is invited and how many have to come, sends the ask, chases and confirms the replies, works the waitlist, and watches the pace against the target week by week. Use it when running `ref/mkt/advisory-board` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Fill the room ## What it does The agent decides who is invited and how many have to come, sends the ask, chases and confirms the replies, works the waitlist, and watches the pace against the target week by week. ## Where it happens The agent does this in five activities across four reference processes. Each one names the activity as that process words it. - **Build the Invitation List** - `ref/mkt/field-event`, activity 5 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Invite the Members** - `ref/mkt/advisory-board`, activity 4 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - **Invite the Press and the Analysts** - `ref/mkt/user-conference`, activity 11 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Watch the Registrations** - `ref/mkt/user-conference`, activity 9 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Work the Registration List** - `ref/mkt/field-event`, activity 10 - [Host Field Event](../../../../processes/marketing/field-event.md) - `ref/mkt/webinar`, activity 9 - [Produce Webinar](../../../../processes/marketing/webinar.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/follow-up-with-the-people-who-came/SKILL.mdAfter the event the agent sends the promised material to the people who attended and routes the interested ones to whoever picks them up. Use it when running `ref/mkt/field-event`.
--- name: follow-up-with-the-people-who-came description: After the event the agent sends the promised material to the people who attended and routes the interested ones to whoever picks them up. Use it when running `ref/mkt/field-event`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Follow up with the people who came ## What it does After the event the agent sends the promised material to the people who attended and routes the interested ones to whoever picks them up. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Follow up with the People Who Came** - `ref/mkt/field-event`, activity 14 - [Host Field Event](../../../../processes/marketing/field-event.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/open-the-sign-up/SKILL.mdThe agent gets the registration live, with the form, the sessions and the tracking set up so every sign-up is recorded. Use it when running `ref/mkt/user-conference` and `ref/mkt/webinar`.
--- name: open-the-sign-up description: The agent gets the registration live, with the form, the sessions and the tracking set up so every sign-up is recorded. Use it when running `ref/mkt/user-conference` and `ref/mkt/webinar`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Open the sign up ## What it does The agent gets the registration live, with the form, the sessions and the tracking set up so every sign-up is recorded. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Open Registration** - `ref/mkt/user-conference`, activity 7 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Set up the Session in the Platform** - `ref/mkt/webinar`, activity 3 - [Produce Webinar](../../../../processes/marketing/webinar.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/plan-the-day-and-check-the-site-is-ready/SKILL.mdThe agent works out the footprint, who is where and what happens minute by minute, then walks the site before doors open to confirm it matches the plan. Use it when running `ref/mkt/field-event`, `ref/mkt/trade-show` and `ref/mkt/user-conference`.
--- name: plan-the-day-and-check-the-site-is-ready description: The agent works out the footprint, who is where and what happens minute by minute, then walks the site before doors open to confirm it matches the plan. Use it when running `ref/mkt/field-event`, `ref/mkt/trade-show` and `ref/mkt/user-conference`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Plan the day and check the site is ready ## What it does The agent works out the footprint, who is where and what happens minute by minute, then walks the site before doors open to confirm it matches the plan. ## Where it happens The agent does this in three activities across three reference processes. Each one names the activity as that process words it. - **Plan the Presence** - `ref/mkt/trade-show`, activity 3 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - **Prepare the Run of Show** - `ref/mkt/field-event`, activity 11 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Set up the Venue** - `ref/mkt/user-conference`, activity 12 - [Host User Conference](../../../../processes/marketing/user-conference.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/record-what-was-learned/SKILL.mdThe agent writes down what to repeat and what to change next time, and keeps it where the next run of the same kind of event starts from it. Use it when running `ref/mkt/advisory-board` and 4 other reference processes.
--- name: record-what-was-learned description: The agent writes down what to repeat and what to change next time, and keeps it where the next run of the same kind of event starts from it. Use it when running `ref/mkt/advisory-board` and 4 other reference processes. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Record what was learned ## What it does The agent writes down what to repeat and what to change next time, and keeps it where the next run of the same kind of event starts from it. ## Where it happens The agent does this in one activity across five reference processes. Each one names the activity as that process words it. - **Record What Was Learned** - `ref/mkt/advisory-board`, activity 16 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - `ref/mkt/field-event`, activity 16 - [Host Field Event](../../../../processes/marketing/field-event.md) - `ref/mkt/trade-show`, activity 16 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - `ref/mkt/user-conference`, activity 17 - [Host User Conference](../../../../processes/marketing/user-conference.md) - `ref/mkt/webinar`, activity 18 - [Produce Webinar](../../../../processes/marketing/webinar.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/report-how-the-event-did/SKILL.md"The agent writes the account of the event: who came, what it cost, what it produced, and how that compares with what the event was asked to do. Use it when running `ref/mkt/field-event` and 3 other reference processes."
--- name: report-how-the-event-did description: "The agent writes the account of the event: who came, what it cost, what it produced, and how that compares with what the event was asked to do. Use it when running `ref/mkt/field-event` and 3 other reference processes." license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Report how the event did ## What it does The agent writes the account of the event: who came, what it cost, what it produced, and how that compares with what the event was asked to do. ## Where it happens The agent does this in four activities across four reference processes. Each one names the activity as that process words it. - **Report How the Event Did** - `ref/mkt/field-event`, activity 15 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Report How the Session Did** - `ref/mkt/webinar`, activity 17 - [Produce Webinar](../../../../processes/marketing/webinar.md) - **Report the Conference** - `ref/mkt/user-conference`, activity 16 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Report the Show** - `ref/mkt/trade-show`, activity 15 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/run-the-event-on-the-day/SKILL.md"The agent runs the event while it is happening: people are checked in, the program keeps to time, every visitor is recorded, and the calls that have to be made on the day get made and written down. Use it when running `ref/mkt/advisory-board` and 4 other reference processes."
--- name: run-the-event-on-the-day description: "The agent runs the event while it is happening: people are checked in, the program keeps to time, every visitor is recorded, and the calls that have to be made on the day get made and written down. Use it when running `ref/mkt/advisory-board` and 4 other reference processes." license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Run the event on the day ## What it does The agent runs the event while it is happening: people are checked in, the program keeps to time, every visitor is recorded, and the calls that have to be made on the day get made and written down. ## Where it happens The agent does this in four activities across five reference processes. Each one names the activity as that process words it. - **Run the Event** - `ref/mkt/field-event`, activity 12 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Run the Session** - `ref/mkt/advisory-board`, activity 11 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - `ref/mkt/webinar`, activity 12 - [Produce Webinar](../../../../processes/marketing/webinar.md) - **Run the Show** - `ref/mkt/user-conference`, activity 13 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Run the Show Days** - `ref/mkt/trade-show`, activity 12 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/run-the-request-and-answer-round/SKILL.mdThe agent runs a round where every function submits what it is asking for in one format by one date, and then tells each function what it was given and the rules that come with it. Use it when running `ref/mkt/set-marketing-budget`.
--- name: run-the-request-and-answer-round description: The agent runs a round where every function submits what it is asking for in one format by one date, and then tells each function what it was given and the rules that come with it. Use it when running `ref/mkt/set-marketing-budget`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Run the request and answer round ## What it does The agent runs a round where every function submits what it is asking for in one format by one date, and then tells each function what it was given and the rules that come with it. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Collect What Each Function Asks For** - `ref/mkt/set-marketing-budget`, activity 4 - [Set Marketing Budget](../../../../processes/marketing/set-marketing-budget.md) - **Tell Every Function What It Has** - `ref/mkt/set-marketing-budget`, activity 14 - [Set Marketing Budget](../../../../processes/marketing/set-marketing-budget.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/send-the-material-before-the-session/SKILL.mdThe agent gets the reading material to the people attending ahead of time and collects the answers they owe before they arrive. Use it when running `ref/mkt/advisory-board`.
--- name: send-the-material-before-the-session description: The agent gets the reading material to the people attending ahead of time and collects the answers they owe before they arrive. Use it when running `ref/mkt/advisory-board`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Send the material before the session ## What it does The agent gets the reading material to the people attending ahead of time and collects the answers they owe before they arrive. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Collect the Early Input** - `ref/mkt/advisory-board`, activity 10 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - **Send the Pre-Read** - `ref/mkt/advisory-board`, activity 9 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/settle-the-pitch-and-brief-the-staff/SKILL.mdThe agent cuts the story down to what can be said in a short conversation, and makes sure the people working the floor know the pitch, the questions to ask and the steps to record a visitor. Use it when running `ref/mkt/trade-show`.
--- name: settle-the-pitch-and-brief-the-staff description: The agent cuts the story down to what can be said in a short conversation, and makes sure the people working the floor know the pitch, the questions to ask and the steps to record a visitor. Use it when running `ref/mkt/trade-show`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Settle the pitch and brief the staff ## What it does The agent cuts the story down to what can be said in a short conversation, and makes sure the people working the floor know the pitch, the questions to ask and the steps to record a visitor. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Brief the Booth Staff** - `ref/mkt/trade-show`, activity 11 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - **Settle the Booth Message** - `ref/mkt/trade-show`, activity 4 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/settle-the-shape-of-the-event/SKILL.mdThe agent settles what kind of event it is, how long it runs, what the budget and the target are, and what actually happens in it, down to the sessions and the order they come in. Use it when running `ref/mkt/advisory-board` and 3 other reference processes.
--- name: settle-the-shape-of-the-event description: The agent settles what kind of event it is, how long it runs, what the budget and the target are, and what actually happens in it, down to the sessions and the order they come in. Use it when running `ref/mkt/advisory-board` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Settle the shape of the event ## What it does The agent settles what kind of event it is, how long it runs, what the budget and the target are, and what actually happens in it, down to the sessions and the order they come in. ## Where it happens The agent does this in five activities across four reference processes. Each one names the activity as that process words it. - **Choose the Program** - `ref/mkt/user-conference`, activity 5 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Set the Agenda** - `ref/mkt/advisory-board`, activity 2 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - **Set the Conference Plan** - `ref/mkt/user-conference`, activity 2 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Settle the Format and Program** - `ref/mkt/field-event`, activity 2 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Settle the Format and the Presenters** - `ref/mkt/webinar`, activity 2 - [Produce Webinar](../../../../processes/marketing/webinar.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/settle-the-space-and-the-suppliers/SKILL.mdThe agent says what space, food, equipment and travel the event needs and on what dates, and holds the record of what has been committed against the plan. Use it when running `ref/mkt/advisory-board`, `ref/mkt/field-event` and `ref/mkt/user-conference`.
--- name: settle-the-space-and-the-suppliers description: The agent says what space, food, equipment and travel the event needs and on what dates, and holds the record of what has been committed against the plan. Use it when running `ref/mkt/advisory-board`, `ref/mkt/field-event` and `ref/mkt/user-conference`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Settle the space and the suppliers ## What it does The agent says what space, food, equipment and travel the event needs and on what dates, and holds the record of what has been committed against the plan. ## Where it happens The agent does this in three activities across three reference processes. Each one names the activity as that process words it. - **Book the Venue and Suppliers** - `ref/mkt/field-event`, activity 3 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Book the Venue and the Suppliers** - `ref/mkt/user-conference`, activity 3 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Make the Arrangements** - `ref/mkt/advisory-board`, activity 6 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/sort-and-route-the-feedback/SKILL.mdThe agent groups what was said into themes with the quotes behind each one, and gets every theme to the owner who can act on it. Use it when running `ref/mkt/advisory-board`.
--- name: sort-and-route-the-feedback description: The agent groups what was said into themes with the quotes behind each one, and gets every theme to the owner who can act on it. Use it when running `ref/mkt/advisory-board`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Sort and route the feedback ## What it does The agent groups what was said into themes with the quotes behind each one, and gets every theme to the owner who can act on it. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Route the Feedback** - `ref/mkt/advisory-board`, activity 14 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - **Sort the Feedback** - `ref/mkt/advisory-board`, activity 13 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/take-in-what-the-event-must-deliver/SKILL.mdThe agent works out who the event is for, what it has to accomplish and by when, and records that as the thing the whole run is measured against. Use it when running `ref/mkt/advisory-board` and 4 other reference processes.
--- name: take-in-what-the-event-must-deliver description: The agent works out who the event is for, what it has to accomplish and by when, and records that as the thing the whole run is measured against. Use it when running `ref/mkt/advisory-board` and 4 other reference processes. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Take in what the event must deliver ## What it does The agent works out who the event is for, what it has to accomplish and by when, and records that as the thing the whole run is measured against. ## Where it happens The agent does this in five activities across five reference processes. Each one names the activity as that process words it. - **Take in the Audience and Date** - `ref/mkt/field-event`, activity 1 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Take in the Conference** - `ref/mkt/user-conference`, activity 1 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Take in the Cycle** - `ref/mkt/advisory-board`, activity 1 - [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md) - **Take in the Show** - `ref/mkt/trade-show`, activity 1 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - **Take in the Topic and Date** - `ref/mkt/webinar`, activity 1 - [Produce Webinar](../../../../processes/marketing/webinar.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/turn-the-event-into-a-deadline-list/SKILL.mdThe agent turns the plan and the organizer's rules into the dated list every other agent works to, saying what each one owes and when it is due. Use it when running `ref/mkt/trade-show`.
--- name: turn-the-event-into-a-deadline-list description: The agent turns the plan and the organizer's rules into the dated list every other agent works to, saying what each one owes and when it is due. Use it when running `ref/mkt/trade-show`. license: CC-BY-4.0 metadata: agent: event-manager agent-version: "1" --- # Turn the event into a deadline list ## What it does The agent turns the plan and the organizer's rules into the dated list every other agent works to, saying what each one owes and when it is due. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **List Every Deadline** - `ref/mkt/trade-show`, activity 2 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) ## What to record The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
mcp.jsonNot in the package.
Every server entry in an mcp.json needs either a command to run or a url to connect to, and the package cannot know either of those until somebody points it at their own systems. So the file is left out, the systems the agent needs are named by role in plugin.json, and you write the mcp.json when you set it up.
Setting it up
Point it at your systems
To run an agent built from this package, write an mcp.json that says which of your systems fills each role. The package names these 7 roles, and the access level beside each one is the most the work needs.
event-plan-and-its-schedule · writeinvitation-and-attendance-record · writeorders-placed-for-the-event · readcrm · readanalytics · readasset-store · readnotification-channel · write
mcp.json
You write this file. It is not part of the package.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/mcp.schema.json",
"mcpServers": {
"event-plan-and-its-schedule": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/event-plan-and-its-schedule"
},
"invitation-and-attendance-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/invitation-and-attendance-record"
},
"orders-placed-for-the-event": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/orders-placed-for-the-event"
},
"crm": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/crm"
},
"analytics": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/analytics"
},
"asset-store": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/asset-store"
},
"notification-channel": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/notification-channel"
}
}
}
The hostnames here are a placeholder for your own. Whichever product holds each of these systems, the agent you build is yours and nobody else has to be involved in running it.
Where it works
6 processes, 48 activities
The highlighted activities are the ones this abstract agent does. The other activities in each process belong to other abstract agents or to people.
Convene Customer Advisory Boardref/mkt/advisory-board · 16 activities
Take in the Cycle · Set the Agenda · Invite the Members · Make the Arrangements · Send the Pre-Read · Collect the Early Input · Run the Session · Sort the Feedback · Route the Feedback · Record What Was Learned
Host Field Eventref/mkt/field-event · 16 activities
Take in the Audience and Date · Settle the Format and Program · Book the Venue and Suppliers · Build the Invitation List · Work the Registration List · Prepare the Run of Show · Run the Event · Follow up with the People Who Came · Report How the Event Did · Record What Was Learned
Set Marketing Budgetref/mkt/set-marketing-budget · 15 activities
Collect What Each Function Asks For · Tell Every Function What It Has
Exhibit at Trade Showref/mkt/trade-show · 16 activities
Take in the Show · List Every Deadline · Plan the Presence · Settle the Booth Message · Brief the Booth Staff · Run the Show Days · Report the Show · Record What Was Learned
Host User Conferenceref/mkt/user-conference · 17 activities
Take in the Conference · Set the Conference Plan · Book the Venue and the Suppliers · Choose the Program · Open Registration · Watch the Registrations · Invite the Press and the Analysts · Set up the Venue · Run the Show · Report the Conference · Record What Was Learned
Produce Webinarref/mkt/webinar · 18 activities
Take in the Topic and Date · Settle the Format and the Presenters · Set up the Session in the Platform · Work the Registration List · Run the Session · Report How the Session Did · Record What Was Learned
The records it leaves
What it writes down
The event plan lands at a version and says what the event has to deliver, what each agent owes, and when each piece is due. The deadline list lands at a version, and a dated record goes in each time a piece lands or slips. The agent leaves the CONVENED and DONE records of the briefing, the roll-calls, the approvals and the debrief. The invitation and attendance record says who was invited, who registered and who came. Every call made on the day is recorded with the time it was made and the reason for it. The report after the event sets what happened beside what the event was asked to do, and it goes out on its date whether or not every source answered.
Where it stops
What it will not do
Does not place orders, sign contracts, book travel or run the load-in, which is the event-operations agent. Does not build the agenda, choose the talks or look after the speakers, which is the event-program agent. Does not write, design or cut anything the event needs, because the copywriter, designer, video-editor and creative-producer agents make that material. Does not promote the event: the campaign-manager agent runs the campaign around it, the email-producer agent sends the invitations to the list this agent defines, and the web-producer agent builds the registration page. Does not decide which customers are asked to speak, give a reference or take an advisory board place, and does not hold the record of what a customer agreed to, which is the advocacy-manager agent. Does not set the budget and does not sign anything. Does not own a product launch, which is the launch-coordinator agent, and an event inside a launch is a run of this agent reporting into it. Does not own the department's report for a reporting period, which is the reporting-manager agent, and this agent answers for one event.
These limits are written into the job on purpose, so that everyone adopting the process knows which decisions stay with a person.
Agents built from this plugin
Who has built one, and how far each one got
Nobody has built one yet. The catalog says so rather than leaving the section off, because an empty list is a fact about the document.
declare it
implements: event-manager v1
One line in your agent's manifest. The catalog checks it against the records your runs actually leave.
A guess, not a claim
The closest things in the catalog, by description
Nobody above has claimed any of these. This is the nearest match by wording between the job written above and what publishers wrote about their own listings, closest first, and wording is not evidence: some of these will be wrong, and a job with nothing suitable still gets whatever was nearest. The publishers have never heard of this abstract agent and have promised nothing about it. What a claim looks like is in the table above, and it is signed.
Might be reached for
Not workers. These are capability that whatever does the job would use, which is a different relationship and kept in its own column for that reason.
- events MCP server · yeehaw.bot · hosted · mirrored from the MCP registry Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.
- mcp MCP server · crisphive.com · hosted · run it yourself · mirrored from the MCP registry Agentic scheduling & booking for field service: availability, jobs, customers, crews, fleet.
- Joinways MCP server · joinways.app · hosted · mirrored from the MCP registry Event venue CRM — manage inquiries, quotes, events and availability from any AI agent