Community manager
community-manager v1Answers the people: replies to comments and messages while a campaign is live, keeps the tone of the brand, and knows exactly which conversations it must not have and who needs to hear about them right away.
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.
Sits in the campaign briefing so its answers match what was published. Reports into collect-and-report - reply volumes, sentiment, and the questions that keep recurring, which are content ideas wearing a different hat.
What is in the package
14 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.
# Where this abstract agent stops Does not argue, does not delete criticism, does not make product promises, and does not answer questions the published material cannot support. ## What always goes to a person - legal threats, press inquiries, and anything that smells like a crisis - immediately, before replying - sentiment past the threshold the process sets - any factual dispute it cannot settle from published material
# The records this abstract agent must leave
This is the contract. An agent implementing `community-manager` leaves
the following behind, on every run.
Every reply logged, every escalation with the reason it was flagged, and
a recurring-questions summary at the cadence the process sets.
An agent that leaves less than this does not implement
`community-manager`, whatever else it does well.
# The systems this abstract agent needs
Three 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 |
|---|---|
| the social inboxes | write |
| the published campaign material and its FAQ | read |
| the escalation channel | write |
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.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json",
"name": "community-manager",
"version": "1.0.0",
"description": "The community-manager abstract agent. Answers the people: replies to comments and messages while a campaign is live, keeps the tone of the brand, and knows exactly which conversations it must not have and who needs to hear about them right away.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/community-manager",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"marketing",
"moderate-community",
"crisis-communication",
"annual-marketing-plan",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "community-manager",
"agentVersion": 1,
"department": "marketing",
"abstract": true,
"works": "Sits in the campaign briefing so its answers match what was published. Reports into collect-and-report - reply volumes, sentiment, and the questions that keep recurring, which are content ideas wearing a different hat.",
"servers": [
{
"name": "the social inboxes",
"role": "social-inboxes",
"access": "write"
},
{
"name": "the published campaign material and its FAQ",
"role": "published-campaign-material-and-its-faq",
"access": "read"
},
{
"name": "the escalation channel",
"role": "escalation-channel",
"access": "write"
}
],
"records": [
"Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets."
],
"escalates": [
"legal threats, press inquiries, and anything that smells like a crisis - immediately, before replying",
"sentiment past the threshold the process sets",
"any factual dispute it cannot settle from published material"
],
"not": [
"Does not argue, does not delete criticism, does not make product promises, and does not answer questions the published material cannot support."
],
"processes": [
{
"process": "ref/mkt/announce-company-news",
"activities": [
"Publish It on the Owned Channels"
]
},
{
"process": "ref/mkt/annual-marketing-plan",
"activities": [
"Gather the Outside Evidence",
"Brief the Department"
]
},
{
"process": "ref/mkt/brand-positioning",
"activities": [
"Read the Current Numbers"
]
},
{
"process": "ref/mkt/brand-refresh",
"activities": [
"Change the Profiles Held Elsewhere"
]
},
{
"process": "ref/mkt/co-marketing-campaign",
"activities": [
"Watch the Joint Campaign"
]
},
{
"process": "ref/mkt/content-calendar",
"activities": [
"Collect the Topic Candidates"
]
},
{
"process": "ref/mkt/crisis-communication",
"activities": [
"Take in the Incident",
"Tailor for Each Audience",
"Brief the Speakers",
"Issue the Response",
"Answer the Questions",
"Track the Coverage"
]
},
{
"process": "ref/mkt/customer-newsletter",
"activities": [
"Answer the Replies"
]
},
{
"process": "ref/mkt/customer-reviews",
"activities": [
"Answer What Comes Back",
"Reply to the Reviews"
]
},
{
"process": "ref/mkt/feature-release",
"activities": [
"Post It Publicly",
"Watch the First Days"
]
},
{
"process": "ref/mkt/field-event",
"activities": [
"Promote the Event"
]
},
{
"process": "ref/mkt/long-form-content",
"activities": [
"Promote the Piece"
]
},
{
"process": "ref/mkt/marketing-performance-report",
"activities": [
"Account for What the Audience Asked"
]
},
{
"process": "ref/mkt/moderate-community",
"activities": [
"Open the Cycle",
"Gather What Came In",
"Sort the Queue",
"Welcome the New Members",
"Answer the Questions",
"Find the Missing Answers",
"Route the Escalations",
"Group the Recurring Questions",
"Name the Members Worth Recognizing",
"Measure the Community",
"Report the Cycle",
"Close the Cycle"
]
},
{
"process": "ref/mkt/pricing-change",
"activities": [
"Answer What Comes Back"
]
},
{
"process": "ref/mkt/product-launch",
"activities": [
"Watch the First Week"
]
},
{
"process": "ref/mkt/social-campaign",
"activities": [
"Engage"
]
},
{
"process": "ref/mkt/speaking-engagement",
"activities": [
"Publish the Material"
]
},
{
"process": "ref/mkt/trade-show",
"activities": [
"Promote the Presence",
"Run the Show Days"
]
},
{
"process": "ref/mkt/user-conference",
"activities": [
"Promote the Conference",
"Run the Show"
]
},
{
"process": "ref/mkt/webinar",
"activities": [
"Promote the Session"
]
},
{
"process": "ref/mkt/win-back-campaign",
"activities": [
"Answer What Comes Back"
]
}
]
}
}
}
# community-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 fourteen 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/announce-company-news`, `ref/mkt/annual-marketing-plan`, `ref/mkt/brand-positioning`, `ref/mkt/brand-refresh`, `ref/mkt/co-marketing-campaign`, `ref/mkt/content-calendar`, and 16 more. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/community-manager
--- name: brief-everyone-who-may-be-asked description: Makes sure everyone who might be asked a question has the same answers in front of them, whether that is the department hearing a plan and what it owes, or the people who may be quoted while something is going on. Use it when running `ref/mkt/annual-marketing-plan` and `ref/mkt/crisis-communication`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Brief everyone who may be asked ## What it does Makes sure everyone who might be asked a question has the same answers in front of them, whether that is the department hearing a plan and what it owes, or the people who may be quoted while something is going on. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Brief the Department** - `ref/mkt/annual-marketing-plan`, activity 15 - [Build Annual Marketing Plan](../../../../processes/marketing/annual-marketing-plan.md) - **Brief the Speakers** - `ref/mkt/crisis-communication`, activity 9 - [Manage Crisis Communication](../../../../processes/marketing/crisis-communication.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: keep-the-profiles-current description: Updates the profiles, listings and pages the organization holds on sites other people run, so that what those show matches what the organization now says about itself. Use it when running `ref/mkt/brand-refresh`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Keep the profiles current ## What it does Updates the profiles, listings and pages the organization holds on sites other people run, so that what those show matches what the organization now says about itself. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Change the Profiles Held Elsewhere** - `ref/mkt/brand-refresh`, activity 20 - [Roll Out Brand Refresh](../../../../processes/marketing/brand-refresh.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: look-after-the-members description: Greets people who have just arrived and gives them the rules and the basics, and passes on the names of members who are helping other members. Use it when running `ref/mkt/moderate-community`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Look after the members ## What it does Greets people who have just arrived and gives them the rules and the basics, and passes on the names of members who are helping other members. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Name the Members Worth Recognizing** - `ref/mkt/moderate-community`, activity 12 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) - **Welcome the New Members** - `ref/mkt/moderate-community`, activity 4 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: pass-on-what-the-audience-is-asking description: Takes what people keep asking in public and puts it in front of whoever can act on it, whether that is a topic worth making, evidence for a plan, or a question the published material cannot answer and a person has to. Use it when running `ref/mkt/annual-marketing-plan`, `ref/mkt/content-calendar` and `ref/mkt/moderate-community`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Pass on what the audience is asking ## What it does Takes what people keep asking in public and puts it in front of whoever can act on it, whether that is a topic worth making, evidence for a plan, or a question the published material cannot answer and a person has to. ## Where it happens The agent does this in four activities across three reference processes. Each one names the activity as that process words it. - **Collect the Topic Candidates** - `ref/mkt/content-calendar`, activity 4 - [Plan Content Calendar](../../../../processes/marketing/content-calendar.md) - **Find the Missing Answers** - `ref/mkt/moderate-community`, activity 6 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) - **Gather the Outside Evidence** - `ref/mkt/annual-marketing-plan`, activity 4 - [Build Annual Marketing Plan](../../../../processes/marketing/annual-marketing-plan.md) - **Group the Recurring Questions** - `ref/mkt/moderate-community`, activity 11 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: promote-what-is-coming-up description: Puts the word out ahead of something so that people turn up, whether that is a session, an event, a conference, a stand or a published piece. Use it when running `ref/mkt/field-event` and 4 other reference processes. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Promote what is coming up ## What it does Puts the word out ahead of something so that people turn up, whether that is a session, an event, a conference, a stand or a published piece. It says what is happening and where to go, and answers what comes back. ## Where it happens The agent does this in five activities across five reference processes. Each one names the activity as that process words it. - **Promote the Conference** - `ref/mkt/user-conference`, activity 8 - [Host User Conference](../../../../processes/marketing/user-conference.md) - **Promote the Event** - `ref/mkt/field-event`, activity 9 - [Host Field Event](../../../../processes/marketing/field-event.md) - **Promote the Piece** - `ref/mkt/long-form-content`, activity 15 - [Produce Long-Form Content](../../../../processes/marketing/long-form-content.md) - **Promote the Presence** - `ref/mkt/trade-show`, activity 10 - [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md) - **Promote the Session** - `ref/mkt/webinar`, activity 8 - [Produce Webinar](../../../../processes/marketing/webinar.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: publish-on-the-owned-channels description: Puts the organization's own message out on the channels it controls, which can be the blog post, the social posts, the community thread, the email, the recording and slides from a talk, or a statement that has to appear everywhere at once. Use it when running `ref/mkt/announce-company-news` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Publish on the owned channels ## What it does Puts the organization's own message out on the channels it controls, which can be the blog post, the social posts, the community thread, the email, the recording and slides from a talk, or a statement that has to appear everywhere at once. ## Where it happens The agent does this in four activities across four reference processes. Each one names the activity as that process words it. - **Issue the Response** - `ref/mkt/crisis-communication`, activity 11 - [Manage Crisis Communication](../../../../processes/marketing/crisis-communication.md) - **Post It Publicly** - `ref/mkt/feature-release`, activity 9 - [Announce Feature Release](../../../../processes/marketing/feature-release.md) - **Publish It on the Owned Channels** - `ref/mkt/announce-company-news`, activity 14 - [Announce Company News](../../../../processes/marketing/announce-company-news.md) - **Publish the Material** - `ref/mkt/speaking-engagement`, activity 14 - [Secure Speaking Engagement](../../../../processes/marketing/speaking-engagement.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: reply-to-what-people-say description: Answers the comments, messages, replies and public reviews that come in, in the tone the brand uses and only from what the published material can support. Use it when running `ref/mkt/crisis-communication` and 6 other reference processes. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Reply to what people say ## What it does Answers the comments, messages, replies and public reviews that come in, in the tone the brand uses and only from what the published material can support. Every reply is logged. ## Where it happens The agent does this in five activities across seven reference processes. Each one names the activity as that process words it. - **Answer What Comes Back** - `ref/mkt/customer-reviews`, activity 12 - [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md) - `ref/mkt/pricing-change`, activity 11 - [Launch Pricing Change](../../../../processes/marketing/pricing-change.md) - `ref/mkt/win-back-campaign`, activity 15 - [Run Win-Back Campaign](../../../../processes/marketing/win-back-campaign.md) - **Answer the Questions** - `ref/mkt/crisis-communication`, activity 12 - [Manage Crisis Communication](../../../../processes/marketing/crisis-communication.md) - `ref/mkt/moderate-community`, activity 5 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) - **Answer the Replies** - `ref/mkt/customer-newsletter`, activity 15 - [Publish Customer Newsletter](../../../../processes/marketing/customer-newsletter.md) - **Engage** - `ref/mkt/social-campaign`, activity 10 - [Run Social Media Campaign](../../../../processes/marketing/social-campaign.md) - **Reply to the Reviews** - `ref/mkt/customer-reviews`, activity 14 - [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: report-on-the-community description: Reports what the audience did over a period, which is how much came in, how it read, how long replies took, what went unanswered, and what people asked about most. Use it when running `ref/mkt/brand-positioning`, `ref/mkt/marketing-performance-report` and `ref/mkt/moderate-community`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Report on the community ## What it does Reports what the audience did over a period, which is how much came in, how it read, how long replies took, what went unanswered, and what people asked about most. ## Where it happens The agent does this in four activities across three reference processes. Each one names the activity as that process words it. - **Account for What the Audience Asked** - `ref/mkt/marketing-performance-report`, activity 7 - [Report Marketing Performance](../../../../processes/marketing/marketing-performance-report.md) - **Measure the Community** - `ref/mkt/moderate-community`, activity 13 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) - **Read the Current Numbers** - `ref/mkt/brand-positioning`, activity 3 - [Define Brand Positioning](../../../../processes/marketing/brand-positioning.md) - **Report the Cycle** - `ref/mkt/moderate-community`, activity 14 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: route-the-escalations description: Sends anything it must not handle itself to the owner who has to see it, which covers legal, press and product matters, and records why each item was flagged. Use it when running `ref/mkt/moderate-community`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Route the escalations ## What it does Sends anything it must not handle itself to the owner who has to see it, which covers legal, press and product matters, and records why each item was flagged. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Route the Escalations** - `ref/mkt/moderate-community`, activity 10 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: run-the-duty-cycle description: Opens a period of duty by carrying in whatever was left open last time, and closes it by naming what is still open and handing that to the next period. Use it when running `ref/mkt/moderate-community`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Run the duty cycle ## What it does Opens a period of duty by carrying in whatever was left open last time, and closes it by naming what is still open and handing that to the next period. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Close the Cycle** - `ref/mkt/moderate-community`, activity 15 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) - **Open the Cycle** - `ref/mkt/moderate-community`, activity 1 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: staff-an-event-in-person description: Covers a live event while it is running, which means the sessions actually happening, the stand being staffed, every visitor being recorded, and somebody fixing what breaks. Use it when running `ref/mkt/trade-show` and `ref/mkt/user-conference`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Staff an event in person ## What it does Covers a live event while it is running, which means the sessions actually happening, the stand being staffed, every visitor being recorded, and somebody fixing what breaks. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **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 Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: take-in-an-incident-and-shape-the-answers description: Records what happened and who already knows, then works out the version of the answer each audience needs, because the press, customers, staff and partners each need something different. Use it when running `ref/mkt/crisis-communication`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Take in an incident and shape the answers ## What it does Records what happened and who already knows, then works out the version of the answer each audience needs, because the press, customers, staff and partners each need something different. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Tailor for Each Audience** - `ref/mkt/crisis-communication`, activity 7 - [Manage Crisis Communication](../../../../processes/marketing/crisis-communication.md) - **Take in the Incident** - `ref/mkt/crisis-communication`, activity 1 - [Manage Crisis Communication](../../../../processes/marketing/crisis-communication.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: take-in-and-sort-the-queue description: Collects everything that arrived, which is the new posts, the questions and the reports, then types each item and puts it in order of urgency so the most pressing gets answered first. Use it when running `ref/mkt/moderate-community`. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Take in and sort the queue ## What it does Collects everything that arrived, which is the new posts, the questions and the reports, then types each item and puts it in order of urgency so the most pressing gets answered first. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Gather What Came In** - `ref/mkt/moderate-community`, activity 2 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) - **Sort the Queue** - `ref/mkt/moderate-community`, activity 3 - [Moderate User Community](../../../../processes/marketing/moderate-community.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
--- name: watch-what-happens-after-it-goes-out description: Watches the days after something goes live and reports what actually happened, which is what people took up, what they asked, what was reported wrong, and what other people published about it. Use it when running `ref/mkt/co-marketing-campaign` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: community-manager agent-version: "1" --- # Watch what happens after it goes out ## What it does Watches the days after something goes live and reports what actually happened, which is what people took up, what they asked, what was reported wrong, and what other people published about it. ## Where it happens The agent does this in four activities across four reference processes. Each one names the activity as that process words it. - **Track the Coverage** - `ref/mkt/crisis-communication`, activity 13 - [Manage Crisis Communication](../../../../processes/marketing/crisis-communication.md) - **Watch the First Days** - `ref/mkt/feature-release`, activity 10 - [Announce Feature Release](../../../../processes/marketing/feature-release.md) - **Watch the First Week** - `ref/mkt/product-launch`, activity 9 - [Launch Product](../../../../processes/marketing/product-launch.md) - **Watch the Joint Campaign** - `ref/mkt/co-marketing-campaign`, activity 13 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) ## What to record Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets. 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`.
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.
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 3 roles, and the access level beside each one is the most the work needs.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/mcp.schema.json",
"mcpServers": {
"social-inboxes": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/social-inboxes"
},
"published-campaign-material-and-its-faq": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/published-campaign-material-and-its-faq"
},
"escalation-channel": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/escalation-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.
22 processes, 43 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.
Publish It on the Owned Channels
Gather the Outside Evidence · Brief the Department
Read the Current Numbers
Change the Profiles Held Elsewhere
Watch the Joint Campaign
Collect the Topic Candidates
Take in the Incident · Tailor for Each Audience · Brief the Speakers · Issue the Response · Answer the Questions · Track the Coverage
Answer the Replies
Answer What Comes Back · Reply to the Reviews
Post It Publicly · Watch the First Days
Promote the Event
Promote the Piece
Account for What the Audience Asked
Open the Cycle · Gather What Came In · Sort the Queue · Welcome the New Members · Answer the Questions · Find the Missing Answers · Route the Escalations · Group the Recurring Questions · Name the Members Worth Recognizing · Measure the Community · Report the Cycle · Close the Cycle
Answer What Comes Back
Watch the First Week
Engage
Publish the Material
Promote the Presence · Run the Show Days
Promote the Conference · Run the Show
Promote the Session
Answer What Comes Back
What it writes down
Every reply logged, every escalation with the reason it was flagged, and a recurring-questions summary at the cadence the process sets.
What it will not do
Does not argue, does not delete criticism, does not make product promises, and does not answer questions the published material cannot support.
These limits are written into the job on purpose, so that everyone adopting the process knows which decisions stay with a person.
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.
implements: community-manager v1
One line in your agent's manifest. The catalog checks it against the records your runs actually leave.
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.
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.
- social-media-manager-mcp MCP server · closermethod.github.io · run it yourself · mirrored from the MCP registry Operational layer for running accounts: calendars, cadence, captions, hashtags, reporting.
- socialapi MCP server · social-api.ai · run it yourself · mirrored from the MCP registry MCP server for SocialAPI — manage social media comments, DMs, reviews, and mentions across platforms
- Posthell MCP server · rohan27s.github.io · hosted · mirrored from the MCP registry Social media scheduler for AI agents: draft posts into a human-approved queue for 15 networks.