Partner manager
partner-manager v1Answers for one outside partner relationship, from the day the agreement is signed through to the day the partner is selling. The agent holds what each side owes under the agreement and when each obligation comes due. It says what the partner may be shown, records what they were given and at which version, and keeps the list of who from the partner has been trained and on what. It holds the tier the partner sits in and what that tier entitles them to, and it records what the partner delivered back, such as the leads they registered, the deals they closed and the marketing they ran with the organization. One run of this agent covers one partner, and the agent keeps answering for that partner for as long as the agreement is in force.
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 a channel program or a campaign run with a partner, and brings the list of partners under agreement, the tier each one holds, and what each one has already agreed to do. Convenes the briefing that starts one partner's onboarding, so the agents producing the material that partner needs hear the same requirement at once. Runs decide-and-announce when the program terms or the tier rules change, because every partner has to hear the same change on the same day. Requests the approval before anything is released to a partner, and again before a partner moves between tiers. Answers roll-calls with where each partner stands against what they owe. Runs collect-and-report at the cadence the process sets on what each partner delivered, and convenes the debrief that closes a program cycle.
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.
partner-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 sign the agreement or agree its terms, which are the legal reviewer (person) and the people who sign contracts. Does not write or design the material a partner is given, which are the copywriter, the designer and the creative-producer agents, and does not score it, which are the brand-check and disclosure-check agents running their own passes. Does not own the material the sales team uses inside a live deal, which is the sales-enablement-manager agent, and this agent says which of that material a partner tier may be shown. Does not send a list of contacts or leads to a partner's system, which is the audience-handover agent, and this agent tells that agent what the agreement allows. Does not run the campaign a partner appears in, which is the campaign-manager agent, and a campaign run with a partner is a run of that agent with this agent holding what the partner agreed to. Does not book or run an event a partner attends or sponsors, which are the event-manager and event-operations agents. Does not hold the record of what a customer agreed to say in public, which is the advocacy-manager agent. Does not run the outside creators the organization pays to publish, which is the creator-relations agent. Does not pay a partner or settle what a partner invoices, which is finance (person). Does not sign anything. ## What always goes to a person - a change to the signed agreement, always. This agent records terms and never agrees them. - anything the organization owes the partner and has missed, on the day it is missed - a partner asking for material their tier does not cover - a tier change that changes what a partner is paid or discounted, because a person decides what a partner is paid - a partner publishing something about the organization that the claims register does not support, on the day it is found - a partner asking to be given contacts or an audience, sent to a person with the consent-manager agent's finding attached - ending the relationship, always
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 `partner-manager` leaves the
following behind, on every run.
The partner record at a version, naming the agreement it rests on, the
tier the partner holds, the date that tier was set and who set it. For
everything the partner was given, the version it was at and the date it
went to them. For every person the partner put through training, what
they were trained on and the date they finished. A dated line for each
obligation as it comes due, saying whether it was met and by whom. What
the partner delivered back, counted against what the agreement asked
for, at the cadence the process sets. The CONVENED and DONE records of
everything it convenes, and the approval record behind every release and
every tier change.
An agent that leaves less than this does not implement
`partner-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 partner record | write | Each partner's contacts, tier, dates and standing land here. |
| the agreement record | read | What each side owes, at the version that was signed. |
| the partner portal | write | Cap: which material each tier may be given, set by the adopting organization. |
| the asset store | read | |
| the training record | write | Who from the partner was trained, on what, and when they finished. |
| the CRM | read | The deals a partner registered and what became of them. |
| the notification channel | write | A partner hears a change to the terms or to their tier on the day it is decided. |
There is deliberately no grant over the agreement itself. This agent
records what was signed and tracks what each side owes under it, and the
people who sign contracts change the terms.
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": "partner-manager",
"version": "1.0.0",
"description": "The partner-manager abstract agent. Answers for one outside partner relationship, from the day the agreement is signed through to the day the partner is selling.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/partner-manager",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"marketing",
"channel-program",
"co-marketing-campaign",
"enable-channel-partner",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "partner-manager",
"agentVersion": 1,
"department": "marketing",
"abstract": true,
"works": "Sits in the briefing that opens a channel program or a campaign run with a partner, and brings the list of partners under agreement, the tier each one holds, and what each one has already agreed to do. Convenes the briefing that starts one partner's onboarding, so the agents producing the material that partner needs hear the same requirement at once. Runs decide-and-announce when the program terms or the tier rules change, because every partner has to hear the same change on the same day. Requests the approval before anything is released to a partner, and again before a partner moves between tiers. Answers roll-calls with where each partner stands against what they owe. Runs collect-and-report at the cadence the process sets on what each partner delivered, and convenes the debrief that closes a program cycle.",
"servers": [
{
"name": "the partner record",
"role": "partner-record",
"access": "write",
"needs": "Each partner's contacts, tier, dates and standing land here."
},
{
"name": "the agreement record",
"role": "agreement-record",
"access": "read",
"needs": "What each side owes, at the version that was signed."
},
{
"name": "the partner portal",
"role": "partner-portal",
"access": "write",
"needs": "Cap: which material each tier may be given, set by the adopting organization."
},
{
"name": "the asset store",
"role": "asset-store",
"access": "read"
},
{
"name": "the training record",
"role": "training-record",
"access": "write",
"needs": "Who from the partner was trained, on what, and when they finished."
},
{
"name": "the CRM",
"role": "crm",
"access": "read",
"needs": "The deals a partner registered and what became of them."
},
{
"name": "the notification channel",
"role": "notification-channel",
"access": "write",
"needs": "A partner hears a change to the terms or to their tier on the day it is decided."
}
],
"records": [
"The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it.",
"For everything the partner was given, the version it was at and the date it went to them.",
"For every person the partner put through training, what they were trained on and the date they finished.",
"A dated line for each obligation as it comes due, saying whether it was met and by whom.",
"What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets.",
"The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change."
],
"escalates": [
"a change to the signed agreement, always. This agent records terms and never agrees them.",
"anything the organization owes the partner and has missed, on the day it is missed",
"a partner asking for material their tier does not cover",
"a tier change that changes what a partner is paid or discounted, because a person decides what a partner is paid",
"a partner publishing something about the organization that the claims register does not support, on the day it is found",
"a partner asking to be given contacts or an audience, sent to a person with the consent-manager agent's finding attached",
"ending the relationship, always"
],
"not": [
"Does not sign the agreement or agree its terms, which are the legal reviewer (person) and the people who sign contracts.",
"Does not write or design the material a partner is given, which are the copywriter, the designer and the creative-producer agents, and does not score it, which are the brand-check and disclosure-check agents running their own passes.",
"Does not own the material the sales team uses inside a live deal, which is the sales-enablement-manager agent, and this agent says which of that material a partner tier may be shown.",
"Does not send a list of contacts or leads to a partner's system, which is the audience-handover agent, and this agent tells that agent what the agreement allows.",
"Does not run the campaign a partner appears in, which is the campaign-manager agent, and a campaign run with a partner is a run of that agent with this agent holding what the partner agreed to.",
"Does not book or run an event a partner attends or sponsors, which are the event-manager and event-operations agents.",
"Does not hold the record of what a customer agreed to say in public, which is the advocacy-manager agent.",
"Does not run the outside creators the organization pays to publish, which is the creator-relations agent.",
"Does not pay a partner or settle what a partner invoices, which is finance (person).",
"Does not sign anything."
],
"processes": [
{
"process": "ref/mkt/channel-program",
"activities": [
"Take in the Program Design",
"Settle the Tiers and the Terms",
"Price the Incentives",
"Draw up the Partner Agreement",
"Draw up the Candidate List",
"Build the Partner Portal",
"Set up the Partner Systems",
"Open Recruitment",
"Assess the Applicants",
"Sign the Partners",
"Hand Each Partner to Enablement",
"Watch the First Partners",
"Report the Program Launch",
"Record What Was Learned"
]
},
{
"process": "ref/mkt/co-marketing-campaign",
"activities": [
"Take in the Partner Agreement",
"Settle the Lead Terms",
"Plan the Joint Campaign",
"Brief the Makers",
"Settle the Joint Direction",
"Score against Both Rule Sets",
"Get Sign-Offs on Both Sides",
"Build the Registration Page",
"Set up Each Side's Distribution",
"Launch the Joint Campaign",
"Watch the Joint Campaign",
"Split and Hand over the Leads",
"Agree the Joint Numbers",
"Record What Was Learned"
]
},
{
"process": "ref/mkt/competitive-battlecard",
"activities": [
"Say What Partners May See"
]
},
{
"process": "ref/mkt/enable-channel-partner",
"activities": [
"Take in the Partner",
"Check What the Partner Holds",
"List What the Partner Must Demonstrate",
"Agree the Partner's Plan",
"Decide What the Partner May See",
"Brief the Makers",
"Publish the Material",
"Run the Session",
"Answer the Partner's Questions",
"Check the Partner Can Pitch",
"Hand over the Selling Kit",
"Watch What the Partner Does",
"Report against the Plan",
"Record What Was Learned"
]
}
]
}
}
}
README.mdWhat the package is, and why it carries no mcp.json.
# partner-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/channel-program`, `ref/mkt/co-marketing-campaign`, `ref/mkt/competitive-battlecard`, `ref/mkt/enable-channel-partner`. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/partner-manager
skills/enablement-plan/SKILL.mdAgrees what one partner will do to get ready and what they will have to show for it, which covers who from the partner takes part, how much time they give, the dates, and the things they have to demonstrate they can do. Use it when running `ref/mkt/enable-channel-partner`.
--- name: enablement-plan description: Agrees what one partner will do to get ready and what they will have to show for it, which covers who from the partner takes part, how much time they give, the dates, and the things they have to demonstrate they can do. Use it when running `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Enablement plan ## What it does Agrees what one partner will do to get ready and what they will have to show for it, which covers who from the partner takes part, how much time they give, the dates, and the things they have to demonstrate they can do. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Agree the Partner's Plan** - `ref/mkt/enable-channel-partner`, activity 4 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **List What the Partner Must Demonstrate** - `ref/mkt/enable-channel-partner`, activity 3 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/enablement-sessions/SKILL.mdRuns the live sessions that train a partner, records them for whoever could not attend, and answers and files the questions that come back afterwards. Use it when running `ref/mkt/enable-channel-partner`.
--- name: enablement-sessions description: Runs the live sessions that train a partner, records them for whoever could not attend, and answers and files the questions that come back afterwards. Use it when running `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Enablement sessions ## What it does Runs the live sessions that train a partner, records them for whoever could not attend, and answers and files the questions that come back afterwards. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Answer the Partner's Questions** - `ref/mkt/enable-channel-partner`, activity 11 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Run the Session** - `ref/mkt/enable-channel-partner`, activity 10 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/joint-approvals/SKILL.mdClears work through both organizations, scoring it item by item against each side's standards and getting every signer on both sides onto the same version. Use it when running `ref/mkt/co-marketing-campaign`.
--- name: joint-approvals description: Clears work through both organizations, scoring it item by item against each side's standards and getting every signer on both sides onto the same version. Use it when running `ref/mkt/co-marketing-campaign`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Joint approvals ## What it does Clears work through both organizations, scoring it item by item against each side's standards and getting every signer on both sides onto the same version. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Get Sign-Offs on Both Sides** - `ref/mkt/co-marketing-campaign`, activity 8 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Score against Both Rule Sets** - `ref/mkt/co-marketing-campaign`, activity 7 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/joint-campaign-planning/SKILL.mdSettles what two organizations will run together, which means the one concept both will put their name on, the channels, the dates, the cost share and what each side owes, and puts the same request to the makers on both sides at the same time. Use it when running `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`.
--- name: joint-campaign-planning description: Settles what two organizations will run together, which means the one concept both will put their name on, the channels, the dates, the cost share and what each side owes, and puts the same request to the makers on both sides at the same time. Use it when running `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Joint campaign planning ## What it does Settles what two organizations will run together, which means the one concept both will put their name on, the channels, the dates, the cost share and what each side owes, and puts the same request to the makers on both sides at the same time. ## Where it happens The agent does this in three activities across two reference processes. Each one names the activity as that process words it. - **Brief the Makers** - `ref/mkt/co-marketing-campaign`, activity 4 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - `ref/mkt/enable-channel-partner`, activity 6 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Plan the Joint Campaign** - `ref/mkt/co-marketing-campaign`, activity 3 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Settle the Joint Direction** - `ref/mkt/co-marketing-campaign`, activity 5 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/joint-launch/SKILL.mdGets both sides ready to go out together, each with its own list, ads and posts, and takes the campaign live on the date they agreed. Use it when running `ref/mkt/co-marketing-campaign`.
--- name: joint-launch description: Gets both sides ready to go out together, each with its own list, ads and posts, and takes the campaign live on the date they agreed. Use it when running `ref/mkt/co-marketing-campaign`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Joint launch ## What it does Gets both sides ready to go out together, each with its own list, ads and posts, and takes the campaign live on the date they agreed. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Launch the Joint Campaign** - `ref/mkt/co-marketing-campaign`, activity 12 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Set up Each Side's Distribution** - `ref/mkt/co-marketing-campaign`, activity 11 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/lead-sharing/SKILL.mdSettles who gets which leads, which fields travel with them and on what basis, then applies that rule when the leads arrive and delivers each side its share. Use it when running `ref/mkt/co-marketing-campaign`.
--- name: lead-sharing description: Settles who gets which leads, which fields travel with them and on what basis, then applies that rule when the leads arrive and delivers each side its share. Use it when running `ref/mkt/co-marketing-campaign`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Lead sharing ## What it does Settles who gets which leads, which fields travel with them and on what basis, then applies that rule when the leads arrive and delivers each side its share. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Settle the Lead Terms** - `ref/mkt/co-marketing-campaign`, activity 2 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Split and Hand over the Leads** - `ref/mkt/co-marketing-campaign`, activity 14 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/material-delivery/SKILL.mdPuts the approved material where the partner can get at it and hands over the working set they sell with, such as the campaign kit, the deal registration route and the leads that come with it. Use it when running `ref/mkt/enable-channel-partner`.
--- name: material-delivery description: Puts the approved material where the partner can get at it and hands over the working set they sell with, such as the campaign kit, the deal registration route and the leads that come with it. Use it when running `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Material delivery ## What it does Puts the approved material where the partner can get at it and hands over the working set they sell with, such as the campaign kit, the deal registration route and the leads 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. - **Hand over the Selling Kit** - `ref/mkt/enable-channel-partner`, activity 13 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Publish the Material** - `ref/mkt/enable-channel-partner`, activity 9 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/material-entitlements/SKILL.mdSays which material a partner is allowed to see, working from the tier they sit in and the terms of their agreement, and records which version each tier is given. Use it when running `ref/mkt/competitive-battlecard` and `ref/mkt/enable-channel-partner`.
--- name: material-entitlements description: Says which material a partner is allowed to see, working from the tier they sit in and the terms of their agreement, and records which version each tier is given. Use it when running `ref/mkt/competitive-battlecard` and `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Material entitlements ## What it does Says which material a partner is allowed to see, working from the tier they sit in and the terms of their agreement, and records which version each tier is given. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Decide What the Partner May See** - `ref/mkt/enable-channel-partner`, activity 5 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Say What Partners May See** - `ref/mkt/competitive-battlecard`, activity 16 - [Refresh Competitive Battlecard](../../../../processes/marketing/competitive-battlecard.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/partner-activity-watch/SKILL.mdReads what partners actually did after something went live, such as the material they used, the deals they registered, the ones that stalled and what they asked for, and sets it against what each side promised. Use it when running `ref/mkt/channel-program`, `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`.
--- name: partner-activity-watch description: Reads what partners actually did after something went live, such as the material they used, the deals they registered, the ones that stalled and what they asked for, and sets it against what each side promised. Use it when running `ref/mkt/channel-program`, `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Partner activity watch ## What it does Reads what partners actually did after something went live, such as the material they used, the deals they registered, the ones that stalled and what they asked for, and sets it against what each side promised. ## Where it happens The agent does this in three activities across three reference processes. Each one names the activity as that process words it. - **Watch What the Partner Does** - `ref/mkt/enable-channel-partner`, activity 14 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Watch the First Partners** - `ref/mkt/channel-program`, activity 15 - [Launch Channel Program](../../../../processes/marketing/channel-program.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 The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/partner-intake/SKILL.mdReads what is already settled about a partner or a program before any work starts, which means who the partner is and what they sell, what each side owes under the agreement, what the program has to deliver and by when, and what the partner was certified on and what has changed since. Use it when running `ref/mkt/channel-program`, `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`.
--- name: partner-intake description: Reads what is already settled about a partner or a program before any work starts, which means who the partner is and what they sell, what each side owes under the agreement, what the program has to deliver and by when, and what the partner was certified on and what has changed since. Use it when running `ref/mkt/channel-program`, `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Partner intake ## What it does Reads what is already settled about a partner or a program before any work starts, which means who the partner is and what they sell, what each side owes under the agreement, what the program has to deliver and by when, and what the partner was certified on and what has changed since. ## Where it happens The agent does this in four activities across three reference processes. Each one names the activity as that process words it. - **Check What the Partner Holds** - `ref/mkt/enable-channel-partner`, activity 2 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Take in the Partner** - `ref/mkt/enable-channel-partner`, activity 1 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Take in the Partner Agreement** - `ref/mkt/co-marketing-campaign`, activity 1 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Take in the Program Design** - `ref/mkt/channel-program`, activity 1 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/partner-recruitment/SKILL.mdBrings partners into the program from end to end, which means setting the profile a partner has to meet, finding who meets it, putting the approach out, reading each applicant back against the profile and the terms, signing the ones that pass, and starting each signed partner on its own enablement run. Use it when running `ref/mkt/channel-program`.
--- name: partner-recruitment description: Brings partners into the program from end to end, which means setting the profile a partner has to meet, finding who meets it, putting the approach out, reading each applicant back against the profile and the terms, signing the ones that pass, and starting each signed partner on its own enablement run. Use it when running `ref/mkt/channel-program`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Partner recruitment ## What it does Brings partners into the program from end to end, which means setting the profile a partner has to meet, finding who meets it, putting the approach out, reading each applicant back against the profile and the terms, signing the ones that pass, and starting each signed partner on its own enablement run. ## Where it happens The agent does this in five activities across one reference process. Each one names the activity as that process words it. - **Assess the Applicants** - `ref/mkt/channel-program`, activity 12 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Draw up the Candidate List** - `ref/mkt/channel-program`, activity 5 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Hand Each Partner to Enablement** - `ref/mkt/channel-program`, activity 14 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Open Recruitment** - `ref/mkt/channel-program`, activity 11 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Sign the Partners** - `ref/mkt/channel-program`, activity 13 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/partner-systems/SKILL.mdStands up the places the program runs through, which means the portal where partners get material and register deals, the records and tiers behind it, and the page and form a joint campaign points people at. Use it when running `ref/mkt/channel-program` and `ref/mkt/co-marketing-campaign`.
--- name: partner-systems description: Stands up the places the program runs through, which means the portal where partners get material and register deals, the records and tiers behind it, and the page and form a joint campaign points people at. Use it when running `ref/mkt/channel-program` and `ref/mkt/co-marketing-campaign`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Partner systems ## What it does Stands up the places the program runs through, which means the portal where partners get material and register deals, the records and tiers behind it, and the page and form a joint campaign points people at. ## Where it happens The agent does this in three activities across two reference processes. Each one names the activity as that process words it. - **Build the Partner Portal** - `ref/mkt/channel-program`, activity 8 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Build the Registration Page** - `ref/mkt/co-marketing-campaign`, activity 9 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Set up the Partner Systems** - `ref/mkt/channel-program`, activity 9 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/program-reporting/SKILL.mdReports what the program or a joint campaign returned against what was promised, matches both sides' counts and costs into one set of figures they agree on, and files what to repeat and what to avoid next time. Use it when running `ref/mkt/channel-program`, `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`.
--- name: program-reporting description: Reports what the program or a joint campaign returned against what was promised, matches both sides' counts and costs into one set of figures they agree on, and files what to repeat and what to avoid next time. Use it when running `ref/mkt/channel-program`, `ref/mkt/co-marketing-campaign` and `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Program reporting ## What it does Reports what the program or a joint campaign returned against what was promised, matches both sides' counts and costs into one set of figures they agree on, and files what to repeat and what to avoid next time. ## 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 the Joint Numbers** - `ref/mkt/co-marketing-campaign`, activity 15 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - **Record What Was Learned** - `ref/mkt/channel-program`, activity 17 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - `ref/mkt/co-marketing-campaign`, activity 16 - [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md) - `ref/mkt/enable-channel-partner`, activity 16 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Report the Program Launch** - `ref/mkt/channel-program`, activity 16 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/program-terms/SKILL.mdSettles what the program asks of a partner and what it gives back, covering the tiers and the conditions on each, the margins and rebates and what they will cost, and the contract a partner signs together with how it ends. Use it when running `ref/mkt/channel-program`.
--- name: program-terms description: Settles what the program asks of a partner and what it gives back, covering the tiers and the conditions on each, the margins and rebates and what they will cost, and the contract a partner signs together with how it ends. Use it when running `ref/mkt/channel-program`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Program terms ## What it does Settles what the program asks of a partner and what it gives back, covering the tiers and the conditions on each, the margins and rebates and what they will cost, and the contract a partner signs together with how it ends. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **Draw up the Partner Agreement** - `ref/mkt/channel-program`, activity 4 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Price the Incentives** - `ref/mkt/channel-program`, activity 3 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Settle the Tiers and the Terms** - `ref/mkt/channel-program`, activity 2 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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/readiness-assessment/SKILL.mdHas the partner demonstrate what they claim they can do, scores it against the criteria that were set beforehand, and reports what the partner can actually do against what was agreed. Use it when running `ref/mkt/enable-channel-partner`.
--- name: readiness-assessment description: Has the partner demonstrate what they claim they can do, scores it against the criteria that were set beforehand, and reports what the partner can actually do against what was agreed. Use it when running `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: partner-manager agent-version: "1" --- # Readiness assessment ## What it does Has the partner demonstrate what they claim they can do, scores it against the criteria that were set beforehand, and reports what the partner can actually do against what was agreed. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Check the Partner Can Pitch** - `ref/mkt/enable-channel-partner`, activity 12 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Report against the Plan** - `ref/mkt/enable-channel-partner`, activity 15 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) ## What to record The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change. 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.
partner-record · writeagreement-record · readpartner-portal · writeasset-store · readtraining-record · writecrm · 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": {
"partner-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/partner-record"
},
"agreement-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/agreement-record"
},
"partner-portal": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/partner-portal"
},
"asset-store": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/asset-store"
},
"training-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/training-record"
},
"crm": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/crm"
},
"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
25 processes, 172 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.
Launch Channel Programref/mkt/channel-program · 17 activities
Take in the Program Design · Settle the Tiers and the Terms · Price the Incentives · Draw up the Partner Agreement · Draw up the Candidate List · Build the Partner Portal · Set up the Partner Systems · Open Recruitment · Assess the Applicants · Sign the Partners · Hand Each Partner to Enablement · Watch the First Partners · Report the Program Launch · Record What Was Learned
Run Co-Marketing Campaignref/mkt/co-marketing-campaign · 16 activities
Take in the Partner Agreement · Settle the Lead Terms · Plan the Joint Campaign · Brief the Makers · Settle the Joint Direction · Score against Both Rule Sets · Get Sign-Offs on Both Sides · Build the Registration Page · Set up Each Side's Distribution · Launch the Joint Campaign · Watch the Joint Campaign · Split and Hand over the Leads · Agree the Joint Numbers · Record What Was Learned
Refresh Competitive Battlecardref/mkt/competitive-battlecard · 16 activities
Say What Partners May See
Enable Channel Partnerref/mkt/enable-channel-partner · 16 activities
Take in the Partner · Check What the Partner Holds · List What the Partner Must Demonstrate · Agree the Partner's Plan · Decide What the Partner May See · Brief the Makers · Publish the Material · Run the Session · Answer the Partner's Questions · Check the Partner Can Pitch · Hand over the Selling Kit · Watch What the Partner Does · Report against the Plan · Record What Was Learned
Allocate the Fundref/prt/allocate-the-fund · 17 activities
Check Each Partner Is Entitled · Publish the Rules Partners Can Read · Tell Each Partner What They Have
Approve a Fund Requestref/prt/approve-a-fund-request · 17 activities
Take in the Request · Check the Request Is Complete · Check the Partner Is Entitled · Ask Marketing Whether It Fits · Agree What Counts as Proof · Ask for What Is Missing · Answer the Partner · Hand the Activity to Marketing
Certify a Partnerref/prt/certify-a-partner · 16 activities
Take in the Named People · Set What Each Role Must Prove · Publish Who Is Certified · Watch for Expiry and Drift
Check and Pay a Claimref/prt/check-and-pay-a-claim · 17 activities
Take in the Claim · Ask the Partner for What Is Missing · Tell the Partner What Was Paid · Record What Was Learned
End a Partner Relationshipref/prt/end-a-partner-relationship · 17 activities
Take in the Reason to End It · Read the Exit Terms · Get the Legal Position · Decide Whether to End It · List the Work in Flight · Write the Wind-Down Plan · Serve the Notice · Agree the Handover with the Partner · Move the Customers · Finish or Transfer the Work in Flight · Close Off the Access · Confirm the Exit Is Complete · Record What the Ending Taught
Explore an Allianceref/prt/explore-an-alliance · 16 activities
Score the Fit
Find a Partnerref/prt/find-a-partner · 16 activities
Take in the Gap · State the Gap in One Line · Set the Test for Closing It · Decide the Kind of Partner · Set the Search Bounds · Look at Who We Already Know · Cut to a Short List · Check for Channel Conflict · Confirm the Short List · Hand the Short List On
Onboard a Partnerref/prt/onboard-a-partner · 16 activities
Name the People on Both Sides · Set What the Partner Can See · Hold the Kick-Off · Set up How Deals Get Registered · Set the Cadence
Plan the Integrationref/prt/plan-the-integration · 16 activities
Take in the Signed Terms · Name the Owners on Both Sides · Set Support and Escalation · Build the Sales Material · Train Both Sales Teams · Agree the Launch Plan · Launch and Watch the First Deals · Hand On to Partner Management
Qualify a Partnerref/prt/qualify-a-partner · 17 activities
Decide Qualified or Not · Tell the Candidate · Hand On the Qualified Candidate
Register a Dealref/prt/register-a-deal · 16 activities
Check the Partner Stands · Ask the Partner for What Is Missing · Set the Protection Period · Tell Both Sides · Warn Before It Lapses
Resolve a Channel Conflictref/prt/resolve-a-channel-conflict · 15 activities
Read the Rule as It Stood · Tell Both Sides the Same Thing · Send the Rule Back When It Fails
Review a Joint Planref/prt/review-a-joint-plan · 17 activities
Open the Review · Settle the Differences · Send the Pack Before the Meeting · Hold the Review · Name the Gaps Out Loud · Set the Next Review
Review Partner Performanceref/prt/review-partner-performance · 16 activities
Open the Review Round · Pull Each Partner's Plan · Read the Obligations Beyond Selling · Check What the Company Owed · Explain Every Gap · Draft the Finding per Partner · Hold the Review · Decide What Happens to Each Partner · Agree the Actions with the Partner · Tell the Partner Where They Stand · Refer the Tier Changes · Record What the Round Taught
Run a Co-Sellref/prt/run-a-co-sell · 17 activities
Check the Claim and the Terms · Agree What Each Side Is Paid · Agree What May Be Shared · Record the Outcome against the Partner
Run a First Deal Togetherref/prt/run-a-first-deal-together · 16 activities
Take in the First Opportunity · Agree This Is the Deal to Walk · Name Who Walks Alongside · Register the Deal · Agree Who Faces the Customer · Plan the Deal or the Delivery Together · Rehearse Before the Customer Sees It · Run the Customer Meetings Together · Price and Quote It Together · Review What Goes to the Customer · Do the Work with the Partner Leading · Step In When It Slips · Confirm the Customer Got What Was Sold · Debrief with the Partner · Hand the Partner to Their Ongoing Manager
Run Alliance Diligenceref/prt/run-alliance-diligence · 17 activities
Ask Their Customers
Set a Partner Tierref/prt/set-a-partner-tier · 16 activities
Open the Tiering Round · Check the Support Can Be Given · Set the Dates and the Notice · Tell Each Partner Their Tier · Change the Systems · Check the Partner Sees the Right Thing · Record What the Rules Got Wrong
Sign a Partner Agreementref/prt/sign-a-partner-agreement · 17 activities
Take in the Qualified Candidate · Set What the Agreement Must Do · Set the Terms and the Floor · Review It Before It Goes Out · Send the Draft and Take the Markup · Negotiate the Open Terms · Settle the Schedules · Record It and Hand It On
Structure an Allianceref/prt/structure-an-alliance · 16 activities
Set the Governance · Hand On the Obligations
Write a Joint Planref/prt/write-a-joint-plan · 17 activities
Take in the Planning Ask · Agree Who Is in the Room · Agree What Each Side Puts In · Name the Plays · Review with Both Sides · Publish the Plan · Set the Review Cadence
The records it leaves
What it writes down
The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change.
Where it stops
What it will not do
Does not sign the agreement or agree its terms, which are the legal reviewer (person) and the people who sign contracts. Does not write or design the material a partner is given, which are the copywriter, the designer and the creative-producer agents, and does not score it, which are the brand-check and disclosure-check agents running their own passes. Does not own the material the sales team uses inside a live deal, which is the sales-enablement-manager agent, and this agent says which of that material a partner tier may be shown. Does not send a list of contacts or leads to a partner's system, which is the audience-handover agent, and this agent tells that agent what the agreement allows. Does not run the campaign a partner appears in, which is the campaign-manager agent, and a campaign run with a partner is a run of that agent with this agent holding what the partner agreed to. Does not book or run an event a partner attends or sponsors, which are the event-manager and event-operations agents. Does not hold the record of what a customer agreed to say in public, which is the advocacy-manager agent. Does not run the outside creators the organization pays to publish, which is the creator-relations agent. Does not pay a partner or settle what a partner invoices, which is finance (person). Does not sign anything.
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: partner-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 do the job
Things that could be the worker: an agent, a packaged product, a plugin.
- The Website Specification — A2A agent Agent · specification.website Read-only A2A agent that answers natural-language questions about The Website Specification and returns matching topics with status, canonical URL,…
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.
- 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.
- A202 MCP server · a202-protocol.github.io · run it yourself · mirrored from the MCP registry Verifiable agreements for agent-led commerce: mandates, obligations, evidence, transaction records.
- mcp MCP server · astrofabric.ai · hosted · mirrored from the MCP registry Agentic growth platform: a mission agent plus metered SEO, ads, outbound and CRM ops tools.