abstract agent · marketing · 10 processes · plugin 1.0.0

Advocacy manager

advocacy-manager v1

Runs the programs that ask customers to do something in public: a review on a public site, a reference call with a prospect, a named story, a place on an advisory board, or time on a stage. This agent works out which customer to ask and what to ask them for, makes the ask, and keeps the standing record of it. That record says which customer was asked, who asked them, what they agreed to, on what terms, until when, and who declined and for what reason. Every other agent that needs a customer to speak reads this record before it plans anything around one.

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.

Sits in the briefing that opens an announcement, an event or a campaign needing a customer in it, and brings which customers are available, for what, and on what terms. Requests the approval before an ask goes out where the process names a signer, and again before an agreed use of a customer's name and words is published. Answers roll-calls with where each ask stands. Runs collect-and-report on the program at the cadence the process sets, covering what was asked for, what was agreed and what was refused.

The plugin

What is in the package

12 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.

Download the package View on GitHub

advocacy-manager · 17 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 write the words, which the copywriter agent does, and does not
approve them; the brand-check agent scores the material and named people
sign it. Does not clear the legal right to use a customer's name,
likeness or logo, which is the rights approver (person). Does not judge
whether an account is healthy enough to be asked, which is the
account-monitor agent; this agent asks that agent and files the answer
with the ask. Does not pitch reporters or industry analysts, which is
the press-relations agent, and it tells that agent which customers
agreed to speak. Does not book or run an event, which are the
event-manager and event-operations agents, and does not build the
program or brief the speakers, which is the event-program agent; it
supplies the customers who agreed to take a stage. Does not file an
award entry or an evaluation response, which is the submissions-manager
agent, and it gets the customer's permission to be named in one. Does
not build a send list or send anything from the sending system, which is
the email-producer agent. Does not choose which messages a customer gets
inside a standing program, which is the lifecycle-manager agent. Does
not reply to the public or act on posts that break the community rules,
which are the community-manager and moderator agents.

## What always goes to a person

- an ask that would give the customer anything of value, including
  payment, a discount or a contract change, because a person decides
  that and several review sites forbid it outright
- a customer the account-monitor agent says should not be approached,
  when a run wants that customer anyway
- a customer who withdraws permission for something already published,
  immediately, because a person decides what comes down and by when
- a customer who wants to say something the organization has not
  approved, or who asks the material to carry a claim the claims
  register does not support
- a request to use a customer's name where no agreement covers that use

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 `advocacy-manager` leaves
the following behind, on every run.

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

An agent that leaves less than this does not implement
`advocacy-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

Five 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 advocacy record | write | Every ask, agreement and refusal lands dated. |
| the CRM | read |  |
| the account standing record | read | What the account-monitor agent found about the customer. |
| the rights and permissions record | read | What each customer has already agreed the organization may use. |
| the outreach channel | write | Cap: how often one customer may be asked, set by the adopting organization. |

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": "advocacy-manager",
  "version": "1.0.0",
  "description": "The advocacy-manager abstract agent. Runs the programs that ask customers to do something in public: a review on a public site, a reference call with a prospect, a named story, a place on an advisory board, or time on a stage.",
  "author": {
    "name": "AgentCatalog",
    "url": "https://agentcatalog.com"
  },
  "homepage": "https://agentcatalog.com/abstract-agents/advocacy-manager",
  "repository": "https://github.com/jeffrschneider/agentcatalog",
  "license": "CC-BY-4.0",
  "keywords": [
    "abstract-agent",
    "reference",
    "marketing",
    "customer-reviews",
    "customer-reference",
    "customer-case-study",
    "abstract"
  ],
  "extensions": {
    "com.agentcatalog.agent": {
      "agent": "advocacy-manager",
      "agentVersion": 1,
      "department": "marketing",
      "abstract": true,
      "works": "Sits in the briefing that opens an announcement, an event or a campaign needing a customer in it, and brings which customers are available, for what, and on what terms. Requests the approval before an ask goes out where the process names a signer, and again before an agreed use of a customer's name and words is published. Answers roll-calls with where each ask stands. Runs collect-and-report on the program at the cadence the process sets, covering what was asked for, what was agreed and what was refused.",
      "servers": [
        {
          "name": "the advocacy record",
          "role": "advocacy-record",
          "access": "write",
          "needs": "Every ask, agreement and refusal lands dated."
        },
        {
          "name": "the CRM",
          "role": "crm",
          "access": "read"
        },
        {
          "name": "the account standing record",
          "role": "account-standing-record",
          "access": "read",
          "needs": "What the account-monitor agent found about the customer."
        },
        {
          "name": "the rights and permissions record",
          "role": "rights-and-permissions-record",
          "access": "read",
          "needs": "What each customer has already agreed the organization may use."
        },
        {
          "name": "the outreach channel",
          "role": "outreach-channel",
          "access": "write",
          "needs": "Cap: how often one customer may be asked, set by the adopting organization."
        }
      ],
      "records": [
        "For each ask, it records the customer, what was asked for, who asked, the date, and the answer that came back.",
        "An agreement records its terms in the customer's own words: what may be used, in which channels, under which name and title, and until when, together with the approval the use rests on.",
        "A refusal records the reason the customer gave and the date they may be asked again.",
        "Beside those, it keeps a standing list of which customers are available for which kind of ask, current as of a date, so that no run plans around a customer who never agreed to it."
      ],
      "escalates": [
        "an ask that would give the customer anything of value, including payment, a discount or a contract change, because a person decides that and several review sites forbid it outright",
        "a customer the account-monitor agent says should not be approached, when a run wants that customer anyway",
        "a customer who withdraws permission for something already published, immediately, because a person decides what comes down and by when",
        "a customer who wants to say something the organization has not approved, or who asks the material to carry a claim the claims register does not support",
        "a request to use a customer's name where no agreement covers that use"
      ],
      "not": [
        "Does not write the words, which the copywriter agent does, and does not approve them; the brand-check agent scores the material and named people sign it.",
        "Does not clear the legal right to use a customer's name, likeness or logo, which is the rights approver (person).",
        "Does not judge whether an account is healthy enough to be asked, which is the account-monitor agent; this agent asks that agent and files the answer with the ask.",
        "Does not pitch reporters or industry analysts, which is the press-relations agent, and it tells that agent which customers agreed to speak.",
        "Does not book or run an event, which are the event-manager and event-operations agents, and does not build the program or brief the speakers, which is the event-program agent; it supplies the customers who agreed to take a stage.",
        "Does not file an award entry or an evaluation response, which is the submissions-manager agent, and it gets the customer's permission to be named in one.",
        "Does not build a send list or send anything from the sending system, which is the email-producer agent.",
        "Does not choose which messages a customer gets inside a standing program, which is the lifecycle-manager agent.",
        "Does not reply to the public or act on posts that break the community rules, which are the community-manager and moderator agents."
      ],
      "processes": [
        {
          "process": "ref/mkt/advisory-board",
          "activities": [
            "Settle the Membership",
            "Invite the Members",
            "Clear the Paperwork",
            "Follow up with the Members",
            "Record What Was Learned"
          ]
        },
        {
          "process": "ref/mkt/award-entry",
          "activities": [
            "Get the Customer's Agreement",
            "Get Sign-Offs"
          ]
        },
        {
          "process": "ref/mkt/brief-industry-analyst",
          "activities": [
            "Line up the Customer References"
          ]
        },
        {
          "process": "ref/mkt/customer-case-study",
          "activities": [
            "Take in the Candidate",
            "Make the Ask",
            "Agree What the Customer Will Do",
            "Brief the Story",
            "Get the Customer's Approval",
            "Hand the Story to Sales",
            "Record What Was Learned"
          ]
        },
        {
          "process": "ref/mkt/customer-newsletter",
          "activities": [
            "Clear the Customer Story"
          ]
        },
        {
          "process": "ref/mkt/customer-reference",
          "activities": [
            "Take in the Reference Request",
            "Set the Reference Profile",
            "Draw up the Candidate List",
            "Rank the Shortlist",
            "Clear the Ask",
            "Write the Request",
            "Agree What the Customer Will Do",
            "Get the Customer's Approvals",
            "Get the Internal Sign-Offs",
            "Record the Reference",
            "Hand the Reference Over",
            "Record What Was Learned"
          ]
        },
        {
          "process": "ref/mkt/customer-reviews",
          "activities": [
            "Take in the Review Goal",
            "Read the Site Rules",
            "Set the Rules for Asking",
            "Choose the Customers to Ask",
            "Clear the List with Account Owners",
            "Write the Ask",
            "Set up the Practical Side",
            "Send the Ask",
            "Send the Reminder",
            "Answer What Comes Back",
            "Reply to the Reviews",
            "Report against the Goal",
            "Record What Was Learned"
          ]
        },
        {
          "process": "ref/mkt/field-event",
          "activities": [
            "Line up the Speakers"
          ]
        },
        {
          "process": "ref/mkt/moderate-community",
          "activities": [
            "Name the Members Worth Recognizing"
          ]
        },
        {
          "process": "ref/mkt/user-conference",
          "activities": [
            "Open the Call for Sessions"
          ]
        }
      ]
    }
  }
}

README.mdWhat the package is, and why it carries no mcp.json.

# advocacy-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 twelve 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/award-entry`,
`ref/mkt/brief-industry-analyst`, `ref/mkt/customer-case-study`,
`ref/mkt/customer-newsletter`, `ref/mkt/customer-reference`, and 4 more.
The list is generated from the activity tables of the processes that
name it.

https://agentcatalog.com/abstract-agents/advocacy-manager

skills/agree-and-record-the-terms/SKILL.mdSettles what the customer has agreed to in their own words, which is what may be used, in which channels, under which name and title, and until when. Use it when running `ref/mkt/advisory-board`, `ref/mkt/customer-case-study` and `ref/mkt/customer-reference`.

---
name: agree-and-record-the-terms
description: Settles what the customer has agreed to in their own words, which is what may be used, in which channels, under which name and title, and until when. Use it when running `ref/mkt/advisory-board`, `ref/mkt/customer-case-study` and `ref/mkt/customer-reference`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Agree and record the terms

## What it does

Settles what the customer has agreed to in their own words, which is
what may be used, in which channels, under which name and title, and
until when. It clears whatever paperwork goes with that and records the
permission with the date it runs out.

## Where it happens

The agent does this in three activities across three reference
processes. Each one names the activity as that process words it.

- **Agree What the Customer Will Do**
  - `ref/mkt/customer-case-study`, activity 4 -
    [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md)
  - `ref/mkt/customer-reference`, activity 10 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
- **Clear the Paperwork**
  - `ref/mkt/advisory-board`, activity 5 -
    [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md)
- **Record the Reference**
  - `ref/mkt/customer-reference`, activity 13 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/clear-the-ask-with-the-account-owner/SKILL.mdPuts the shortlist in front of the people who own those relationships and gets their word on whether each customer may be asked now. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.

---
name: clear-the-ask-with-the-account-owner
description: Puts the shortlist in front of the people who own those relationships and gets their word on whether each customer may be asked now. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Clear the ask with the account owner

## What it does

Puts the shortlist in front of the people who own those relationships
and gets their word on whether each customer may be asked now. A name
comes off the list when the owner says so.

## Where it happens

The agent does this in two activities across two reference processes.
Each one names the activity as that process words it.

- **Clear the Ask**
  - `ref/mkt/customer-reference`, activity 7 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
- **Clear the List with Account Owners**
  - `ref/mkt/customer-reviews`, activity 5 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/close-the-run/SKILL.mdSets what the run actually landed beside what was asked for, and writes down what to repeat and what to change next cycle. Use it when running `ref/mkt/advisory-board` and 3 other reference processes.

---
name: close-the-run
description: Sets what the run actually landed beside what was asked for, and writes down what to repeat and what to change next cycle. Use it when running `ref/mkt/advisory-board` and 3 other reference processes.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Close the run

## What it does

Sets what the run actually landed beside what was asked for, and writes
down what to repeat and what to change next cycle.

## Where it happens

The agent does this in two activities across four 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/customer-case-study`, activity 21 -
    [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md)
  - `ref/mkt/customer-reference`, activity 15 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
  - `ref/mkt/customer-reviews`, activity 16 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)
- **Report against the Goal**
  - `ref/mkt/customer-reviews`, activity 15 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/get-the-customers-approval/SKILL.mdGoes back to the customer to have them clear the finished material at a version, including their own words and the sign-off of their own legal and communications people where the customer requires it. Use it when running `ref/mkt/award-entry`, `ref/mkt/customer-case-study` and `ref/mkt/customer-reference`.

---
name: get-the-customers-approval
description: Goes back to the customer to have them clear the finished material at a version, including their own words and the sign-off of their own legal and communications people where the customer requires it. Use it when running `ref/mkt/award-entry`, `ref/mkt/customer-case-study` and `ref/mkt/customer-reference`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Get the customers approval

## What it does

Goes back to the customer to have them clear the finished material at a
version, including their own words and the sign-off of their own legal
and communications people where the customer requires it.

## Where it happens

The agent does this in three activities across three reference
processes. Each one names the activity as that process words it.

- **Get the Customer's Agreement**
  - `ref/mkt/award-entry`, activity 7 -
    [Submit Award Entry](../../../../processes/marketing/award-entry.md)
- **Get the Customer's Approval**
  - `ref/mkt/customer-case-study`, activity 15 -
    [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md)
- **Get the Customer's Approvals**
  - `ref/mkt/customer-reference`, activity 11 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/get-the-internal-sign-offs/SKILL.mdRuns the material past the people inside the organization who have to clear it before a customer is named, which covers brand, legal and rights, and records what each of them cleared. Use it when running `ref/mkt/award-entry`, `ref/mkt/customer-newsletter` and `ref/mkt/customer-reference`.

---
name: get-the-internal-sign-offs
description: Runs the material past the people inside the organization who have to clear it before a customer is named, which covers brand, legal and rights, and records what each of them cleared. Use it when running `ref/mkt/award-entry`, `ref/mkt/customer-newsletter` and `ref/mkt/customer-reference`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Get the internal sign offs

## What it does

Runs the material past the people inside the organization who have to
clear it before a customer is named, which covers brand, legal and
rights, and records what each of them cleared.

## Where it happens

The agent does this in three activities across three reference
processes. Each one names the activity as that process words it.

- **Clear the Customer Story**
  - `ref/mkt/customer-newsletter`, activity 4 -
    [Publish Customer Newsletter](../../../../processes/marketing/customer-newsletter.md)
- **Get Sign-Offs**
  - `ref/mkt/award-entry`, activity 11 -
    [Submit Award Entry](../../../../processes/marketing/award-entry.md)
- **Get the Internal Sign-Offs**
  - `ref/mkt/customer-reference`, activity 12 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/hand-the-customer-to-whoever-asked/SKILL.mdHands a cleared and willing customer to whoever needs them, with what may be used and what may not, and briefs the agents that will build something around that customer. Use it when running `ref/mkt/brief-industry-analyst`, `ref/mkt/customer-case-study` and `ref/mkt/customer-reference`.

---
name: hand-the-customer-to-whoever-asked
description: Hands a cleared and willing customer to whoever needs them, with what may be used and what may not, and briefs the agents that will build something around that customer. Use it when running `ref/mkt/brief-industry-analyst`, `ref/mkt/customer-case-study` and `ref/mkt/customer-reference`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Hand the customer to whoever asked

## What it does

Hands a cleared and willing customer to whoever needs them, with what
may be used and what may not, and briefs the agents that will build
something around that customer.

## Where it happens

The agent does this in four activities across three reference processes.
Each one names the activity as that process words it.

- **Brief the Story**
  - `ref/mkt/customer-case-study`, activity 6 -
    [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md)
- **Hand the Reference Over**
  - `ref/mkt/customer-reference`, activity 14 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
- **Hand the Story to Sales**
  - `ref/mkt/customer-case-study`, activity 19 -
    [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md)
- **Line up the Customer References**
  - `ref/mkt/brief-industry-analyst`, activity 10 -
    [Brief Industry Analyst](../../../../processes/marketing/brief-industry-analyst.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/pick-the-customers-to-ask/SKILL.mdPulls the accounts that match the profile, orders them by how well they fit and how ready they are, and settles who actually gets asked this cycle. Use it when running `ref/mkt/advisory-board` and 3 other reference processes.

---
name: pick-the-customers-to-ask
description: Pulls the accounts that match the profile, orders them by how well they fit and how ready they are, and settles who actually gets asked this cycle. Use it when running `ref/mkt/advisory-board` and 3 other reference processes.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Pick the customers to ask

## What it does

Pulls the accounts that match the profile, orders them by how well they
fit and how ready they are, and settles who actually gets asked this
cycle.

## 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 Customers to Ask**
  - `ref/mkt/customer-reviews`, activity 4 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)
- **Draw up the Candidate List**
  - `ref/mkt/customer-reference`, activity 3 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
- **Rank the Shortlist**
  - `ref/mkt/customer-reference`, activity 6 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
- **Settle the Membership**
  - `ref/mkt/advisory-board`, activity 3 -
    [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md)
- **Take in the Candidate**
  - `ref/mkt/customer-case-study`, activity 1 -
    [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/put-the-ask-to-the-customers/SKILL.mdSends the ask to the cleared list on its schedule, sends one reminder to whoever has not answered, and records every reply. Use it when running `ref/mkt/advisory-board` and 4 other reference processes.

---
name: put-the-ask-to-the-customers
description: Sends the ask to the cleared list on its schedule, sends one reminder to whoever has not answered, and records every reply. Use it when running `ref/mkt/advisory-board` and 4 other reference processes.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Put the ask to the customers

## What it does

Sends the ask to the cleared list on its schedule, sends one reminder to
whoever has not answered, and records every reply. It sets up the
practical side first, which is the list, the dates and the link each
customer follows.

## Where it happens

The agent does this in seven activities across five reference processes.
Each one names the activity as that process words it.

- **Invite the Members**
  - `ref/mkt/advisory-board`, activity 4 -
    [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md)
- **Line up the Speakers**
  - `ref/mkt/field-event`, activity 4 -
    [Host Field Event](../../../../processes/marketing/field-event.md)
- **Make the Ask**
  - `ref/mkt/customer-case-study`, activity 3 -
    [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md)
- **Open the Call for Sessions**
  - `ref/mkt/user-conference`, activity 4 -
    [Host User Conference](../../../../processes/marketing/user-conference.md)
- **Send the Ask**
  - `ref/mkt/customer-reviews`, activity 10 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)
- **Send the Reminder**
  - `ref/mkt/customer-reviews`, activity 11 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)
- **Set up the Practical Side**
  - `ref/mkt/customer-reviews`, activity 9 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/set-the-profile-and-the-rules/SKILL.mdWrites down which customer would fit the ask, what the ask may offer, and what it has to disclose. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.

---
name: set-the-profile-and-the-rules
description: Writes down which customer would fit the ask, what the ask may offer, and what it has to disclose. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Set the profile and the rules

## What it does

Writes down which customer would fit the ask, what the ask may offer,
and what it has to disclose. It reads each site's own policy on asking
and on incentives first, because those policies differ and some forbid
an incentive outright.

## Where it happens

The agent does this in three activities across two reference processes.
Each one names the activity as that process words it.

- **Read the Site Rules**
  - `ref/mkt/customer-reviews`, activity 2 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)
- **Set the Reference Profile**
  - `ref/mkt/customer-reference`, activity 2 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
- **Set the Rules for Asking**
  - `ref/mkt/customer-reviews`, activity 3 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/stay-in-touch-with-the-customers/SKILL.mdAnswers what comes back after an ask, which is the questions, the complaints and the people asking to be left alone. Use it when running `ref/mkt/advisory-board`, `ref/mkt/customer-reviews` and `ref/mkt/moderate-community`.

---
name: stay-in-touch-with-the-customers
description: Answers what comes back after an ask, which is the questions, the complaints and the people asking to be left alone. Use it when running `ref/mkt/advisory-board`, `ref/mkt/customer-reviews` and `ref/mkt/moderate-community`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Stay in touch with the customers

## What it does

Answers what comes back after an ask, which is the questions, the
complaints and the people asking to be left alone. It replies on the
site where a customer wrote, tells participants what happened with what
they said, and passes on the names of the people worth recognizing.

## Where it happens

The agent does this in four activities across three 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)
- **Follow up with the Members**
  - `ref/mkt/advisory-board`, activity 15 -
    [Convene Customer Advisory Board](../../../../processes/marketing/advisory-board.md)
- **Name the Members Worth Recognizing**
  - `ref/mkt/moderate-community`, activity 12 -
    [Moderate User Community](../../../../processes/marketing/moderate-community.md)
- **Reply to the Reviews**
  - `ref/mkt/customer-reviews`, activity 14 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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-the-request/SKILL.mdReads a request for a customer to do something in public and works out what it is for and by when, whether that is a reference somebody needs for a live deal or a goal for how many reviews on which sites. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.

---
name: take-in-the-request
description: Reads a request for a customer to do something in public and works out what it is for and by when, whether that is a reference somebody needs for a live deal or a goal for how many reviews on which sites. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Take in the request

## What it does

Reads a request for a customer to do something in public and works out
what it is for and by when, whether that is a reference somebody needs
for a live deal or a goal for how many reviews on which sites.

## Where it happens

The agent does this in two activities across two reference processes.
Each one names the activity as that process words it.

- **Take in the Reference Request**
  - `ref/mkt/customer-reference`, activity 1 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)
- **Take in the Review Goal**
  - `ref/mkt/customer-reviews`, activity 1 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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/write-the-ask/SKILL.mdPuts the ask in writing so the customer can read exactly what is being requested, together with the reminder that follows it and any line the rules require it to carry. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.

---
name: write-the-ask
description: Puts the ask in writing so the customer can read exactly what is being requested, together with the reminder that follows it and any line the rules require it to carry. Use it when running `ref/mkt/customer-reference` and `ref/mkt/customer-reviews`.
license: CC-BY-4.0
metadata:
  agent: advocacy-manager
  agent-version: "1"
---

# Write the ask

## What it does

Puts the ask in writing so the customer can read exactly what is being
requested, together with the reminder that follows it and any line the
rules require it to carry.

## Where it happens

The agent does this in two activities across two reference processes.
Each one names the activity as that process words it.

- **Write the Ask**
  - `ref/mkt/customer-reviews`, activity 6 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)
- **Write the Request**
  - `ref/mkt/customer-reference`, activity 8 -
    [Recruit Customer Reference](../../../../processes/marketing/customer-reference.md)

## What to record

For each ask, it records the customer, what was asked for, who asked,
the date, and the answer that came back. An agreement records its terms
in the customer's own words: what may be used, in which channels, under
which name and title, and until when, together with the approval the use
rests on. A refusal records the reason the customer gave and the date
they may be asked again. Beside those, it keeps a standing list of which
customers are available for which kind of ask, current as of a date, so
that no run plans around a customer who never agreed to it.

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 5 roles, and the access level beside each one is the most the work needs.

advocacy-record · writecrm · readaccount-standing-record · readrights-and-permissions-record · readoutreach-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": {
    "advocacy-record": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/advocacy-record"
    },
    "crm": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/crm"
    },
    "account-standing-record": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/account-standing-record"
    },
    "rights-and-permissions-record": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/rights-and-permissions-record"
    },
    "outreach-channel": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/outreach-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

10 processes, 44 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

Settle the Membership · Invite the Members · Clear the Paperwork · Follow up with the Members · Record What Was Learned

Submit Award Entryref/mkt/award-entry · 16 activities

Get the Customer's Agreement · Get Sign-Offs

Brief Industry Analystref/mkt/brief-industry-analyst · 17 activities

Line up the Customer References

Produce Customer Case Studyref/mkt/customer-case-study · 21 activities

Take in the Candidate · Make the Ask · Agree What the Customer Will Do · Brief the Story · Get the Customer's Approval · Hand the Story to Sales · Record What Was Learned

Publish Customer Newsletterref/mkt/customer-newsletter · 17 activities

Clear the Customer Story

Recruit Customer Referenceref/mkt/customer-reference · 15 activities

Take in the Reference Request · Set the Reference Profile · Draw up the Candidate List · Rank the Shortlist · Clear the Ask · Write the Request · Agree What the Customer Will Do · Get the Customer's Approvals · Get the Internal Sign-Offs · Record the Reference · Hand the Reference Over · Record What Was Learned

Solicit Customer Reviewsref/mkt/customer-reviews · 16 activities

Take in the Review Goal · Read the Site Rules · Set the Rules for Asking · Choose the Customers to Ask · Clear the List with Account Owners · Write the Ask · Set up the Practical Side · Send the Ask · Send the Reminder · Answer What Comes Back · Reply to the Reviews · Report against the Goal · Record What Was Learned

Host Field Eventref/mkt/field-event · 16 activities

Line up the Speakers

Moderate User Communityref/mkt/moderate-community · 15 activities

Name the Members Worth Recognizing

Host User Conferenceref/mkt/user-conference · 17 activities

Open the Call for Sessions

The records it leaves

What it writes down

For each ask, it records the customer, what was asked for, who asked, the date, and the answer that came back. An agreement records its terms in the customer's own words: what may be used, in which channels, under which name and title, and until when, together with the approval the use rests on. A refusal records the reason the customer gave and the date they may be asked again. Beside those, it keeps a standing list of which customers are available for which kind of ask, current as of a date, so that no run plans around a customer who never agreed to it.

Where it stops

What it will not do

Does not write the words, which the copywriter agent does, and does not approve them; the brand-check agent scores the material and named people sign it. Does not clear the legal right to use a customer's name, likeness or logo, which is the rights approver (person). Does not judge whether an account is healthy enough to be asked, which is the account-monitor agent; this agent asks that agent and files the answer with the ask. Does not pitch reporters or industry analysts, which is the press-relations agent, and it tells that agent which customers agreed to speak. Does not book or run an event, which are the event-manager and event-operations agents, and does not build the program or brief the speakers, which is the event-program agent; it supplies the customers who agreed to take a stage. Does not file an award entry or an evaluation response, which is the submissions-manager agent, and it gets the customer's permission to be named in one. Does not build a send list or send anything from the sending system, which is the email-producer agent. Does not choose which messages a customer gets inside a standing program, which is the lifecycle-manager agent. Does not reply to the public or act on posts that break the community rules, which are the community-manager and moderator agents.

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: advocacy-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.

AdvocateMCP MCP server · advocatemcp.com · hosted · mirrored from the MCP registry MCP layer for local businesses: discover, query, book, and transact with verified SMB AI agents.
agent-crm MCP server · khaoss85.github.io · hosted · mirrored from the MCP registry Read-only docs for the Accordo CRM framework: what it proves, and where it stops.
Social Perks MCP server · benzatkulak-collab.github.io · hosted · mirrored from the MCP registry Agent-native marketing platform: create campaigns, submit proofs, review submissions.