Sales enablement manager
sales-enablement-manager v1Owns the material the sales team uses inside a live deal: the deck, the one-pager, the answers to the objections that keep coming up, and the battlecards. The agent takes in the gap that sales names, settles what the material has to answer and by when, briefs the agents that write and design it, drives it through its sign-offs, and puts the finished version where a rep can find it while a deal is open. It keeps answering for that material afterwards, because a claim that was true when the piece was signed stops being true when the product, the price or a competitor changes, and somebody has to notice and either fix the piece or take it out of the reps' hands.
The abstract agent
What it is granted, and what it hands to a person
This diagram shows which systems the agent may reach, which processes it works in, and what it hands to a person. Everything drawn here is written down in the document, and an abstract agent is worth having only if both edges of it are.
Convenes the briefing that starts a piece of enablement material, so the researcher, the copywriter and the designer hear the same gap at once and a person from sales says in that room what a rep needs to be able to answer. Commissions build-by-talent for the production. Declares the order of the checking passes in layered-passes, so each scoring agent knows when its turn comes. Requests the approval that has to pass before material reaches reps, and takes a changes-requested back to the agent the signers named. Runs decide-and-announce when a new version replaces one reps are already carrying, because every rep has to be working from the same version on the same day. Runs collect-and-report on what reps used and what they reported as wrong, and convenes the debrief that closes the run.
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.
sales-enablement-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 or design the pages, which are the copywriter and designer agents, and does not edit the structure and the argument, which is the editor agent. Does not score the material against the brand guidelines or the claims register, which is the brand-check agent running its own pass, and does not score it against the disclosure rules in a market, which is the disclosure-check agent. Does not hold the standards it is scored against, which is the standards-keeper agent, and this agent asks that agent what a rule means when the text does not settle it. Does not go and find the evidence behind a competitor claim, which is the researcher agent. Does not run one published piece from topic to live, which is the content-manager agent, and does not answer for everything already on the site, which is the content-librarian agent, because the material this agent owns goes to reps rather than to the public. Does not sit in a deal, talk to a prospect or answer an objection in front of a customer, because the sales team does that and this agent gives them what to say. Does not set the price or the discount. Does not own a product launch and its deadline math, which is the launch-coordinator agent, and a kit built for a launch is a run of this agent reporting into it. Does not run the partner relationship or decide what a partner tier may be shown, which is the partner-manager agent, and this agent says which of its material is fit to leave the organization at all. Does not own the department's report for a reporting period, which is the reporting-manager agent. Does not sign anything. ## What always goes to a person - a claim it cannot find a citation for, because it never invents one - a piece already in the reps' hands that rests on a claim the register no longer supports, on the day it is found - a comparison that names another organization, always, because a person decides what may be said about somebody else - pricing, discount and contract wording, always - a gap sales names that the product does not cover, because the answer is a change to the product or the price rather than a change to the material - anything a sign-off flags as legal
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 `sales-enablement-manager`
leaves the following behind, on every run.
Each piece at a numbered version, naming the gap it answers, the date it
was issued and the date it stopped being current. Every claim in the
material carries the register entry it rests on, with the version of
that entry. The approval record behind each version, and a dated record
of who was told the version changed. The standing readout at the cadence
the process sets, saying which pieces reps opened, which they left
alone, and what they reported as wrong. A retirement record for material
taken out of the reps' hands, naming what replaced it or saying that
nothing did.
An agent that leaves less than this does not implement
`sales-enablement-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
Eight 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 enablement library | write | Each piece lands at a numbered version, and the version reps hold is the one recorded here. |
| the claims register | read | At its version. |
| brand guidelines | read | |
| the asset store | read | |
| the competitive record | read | What has been established about each competitor, at its version. |
| the CRM | read | What deals were won and lost, and what they were lost to. |
| the usage record for the material | read | Which pieces reps opened and in which deals. |
| the notification channel | write | Reps hear which version is current and from when. |
There is deliberately no write into the CRM. This agent reads what deals
were won and lost to work out what the material has to answer, and it
changes nothing there.
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": "sales-enablement-manager",
"version": "1.0.0",
"description": "The sales-enablement-manager abstract agent. Owns the material the sales team uses inside a live deal: the deck, the one-pager, the answers to the objections that keep coming up, and the battlecards.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/sales-enablement-manager",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"marketing",
"sales-enablement-kit",
"competitive-battlecard",
"enable-channel-partner",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "sales-enablement-manager",
"agentVersion": 1,
"department": "marketing",
"abstract": true,
"works": "Convenes the briefing that starts a piece of enablement material, so the researcher, the copywriter and the designer hear the same gap at once and a person from sales says in that room what a rep needs to be able to answer. Commissions build-by-talent for the production. Declares the order of the checking passes in layered-passes, so each scoring agent knows when its turn comes. Requests the approval that has to pass before material reaches reps, and takes a changes-requested back to the agent the signers named. Runs decide-and-announce when a new version replaces one reps are already carrying, because every rep has to be working from the same version on the same day. Runs collect-and-report on what reps used and what they reported as wrong, and convenes the debrief that closes the run.",
"servers": [
{
"name": "the enablement library",
"role": "enablement-library",
"access": "write",
"needs": "Each piece lands at a numbered version, and the version reps hold is the one recorded here."
},
{
"name": "the claims register",
"role": "claims-register",
"access": "read",
"needs": "At its version."
},
{
"name": "brand guidelines",
"role": "brand-guidelines",
"access": "read"
},
{
"name": "the asset store",
"role": "asset-store",
"access": "read"
},
{
"name": "the competitive record",
"role": "competitive-record",
"access": "read",
"needs": "What has been established about each competitor, at its version."
},
{
"name": "the CRM",
"role": "crm",
"access": "read",
"needs": "What deals were won and lost, and what they were lost to."
},
{
"name": "the usage record for the material",
"role": "usage-record-for-the-material",
"access": "read",
"needs": "Which pieces reps opened and in which deals."
},
{
"name": "the notification channel",
"role": "notification-channel",
"access": "write",
"needs": "Reps hear which version is current and from when."
}
],
"records": [
"Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current.",
"Every claim in the material carries the register entry it rests on, with the version of that entry.",
"The approval record behind each version, and a dated record of who was told the version changed.",
"The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong.",
"A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did."
],
"escalates": [
"a claim it cannot find a citation for, because it never invents one",
"a piece already in the reps' hands that rests on a claim the register no longer supports, on the day it is found",
"a comparison that names another organization, always, because a person decides what may be said about somebody else",
"pricing, discount and contract wording, always",
"a gap sales names that the product does not cover, because the answer is a change to the product or the price rather than a change to the material",
"anything a sign-off flags as legal"
],
"not": [
"Does not write the words or design the pages, which are the copywriter and designer agents, and does not edit the structure and the argument, which is the editor agent.",
"Does not score the material against the brand guidelines or the claims register, which is the brand-check agent running its own pass, and does not score it against the disclosure rules in a market, which is the disclosure-check agent.",
"Does not hold the standards it is scored against, which is the standards-keeper agent, and this agent asks that agent what a rule means when the text does not settle it.",
"Does not go and find the evidence behind a competitor claim, which is the researcher agent.",
"Does not run one published piece from topic to live, which is the content-manager agent, and does not answer for everything already on the site, which is the content-librarian agent, because the material this agent owns goes to reps rather than to the public.",
"Does not sit in a deal, talk to a prospect or answer an objection in front of a customer, because the sales team does that and this agent gives them what to say.",
"Does not set the price or the discount.",
"Does not own a product launch and its deadline math, which is the launch-coordinator agent, and a kit built for a launch is a run of this agent reporting into it.",
"Does not run the partner relationship or decide what a partner tier may be shown, which is the partner-manager agent, and this agent says which of its material is fit to leave the organization at all.",
"Does not own the department's report for a reporting period, which is the reporting-manager agent.",
"Does not sign anything."
],
"processes": [
{
"process": "ref/mkt/account-based-play",
"activities": [
"Brief the Makers",
"Make the Sales Material"
]
},
{
"process": "ref/mkt/channel-program",
"activities": [
"Build the Partner Selling Kit"
]
},
{
"process": "ref/mkt/competitive-battlecard",
"activities": [
"Take in the Move",
"Find the Cards It Touches",
"Hear What Reps Are Meeting",
"Write the Card",
"Issue the Version",
"Notify Sales"
]
},
{
"process": "ref/mkt/customer-case-study",
"activities": [
"Hand the Story to Sales"
]
},
{
"process": "ref/mkt/enable-channel-partner",
"activities": [
"List What the Partner Must Demonstrate",
"Brief the Makers",
"Produce the Partner Material",
"Answer the Partner's Questions"
]
},
{
"process": "ref/mkt/feature-release",
"activities": [
"Brief Support and Sales"
]
},
{
"process": "ref/mkt/pricing-change",
"activities": [
"Produce What Customers and Sellers Read"
]
},
{
"process": "ref/mkt/product-positioning",
"activities": [
"Read What Happens Inside Deals"
]
},
{
"process": "ref/mkt/sales-enablement-kit",
"activities": [
"Take in the Gap",
"Settle What Each Side Owes",
"Settle the Answers",
"Brief the Makers",
"Try the Kit on Reps",
"Hand the Kit to Sales",
"Watch What Sales Does with It",
"Report against the Gap",
"Record What Was Learned"
]
}
]
}
}
}
README.mdWhat the package is, and why it carries no mcp.json.
# sales-enablement-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/account-based-play`, `ref/mkt/channel-program`, `ref/mkt/competitive-battlecard`, `ref/mkt/customer-case-study`, `ref/mkt/enable-channel-partner`, `ref/mkt/feature-release`, and 3 more. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/sales-enablement-manager
skills/answer-the-questions-that-come-back/SKILL.mdAnswers what comes back after a session or a release, and files each answer with the material it belongs to. Use it when running `ref/mkt/enable-channel-partner`.
--- name: answer-the-questions-that-come-back description: Answers what comes back after a session or a release, and files each answer with the material it belongs to. Use it when running `ref/mkt/enable-channel-partner`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Answer the questions that come back ## What it does Answers what comes back after a session or a release, and files each answer with the material it belongs to. ## Where it happens The agent does this in one activity 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) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. 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/brief-the-agents-that-make-it/SKILL.mdGives every agent that has to write, design or check the material the same request at the same time. Use it when running `ref/mkt/account-based-play`, `ref/mkt/enable-channel-partner` and `ref/mkt/sales-enablement-kit`.
--- name: brief-the-agents-that-make-it description: Gives every agent that has to write, design or check the material the same request at the same time. Use it when running `ref/mkt/account-based-play`, `ref/mkt/enable-channel-partner` and `ref/mkt/sales-enablement-kit`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Brief the agents that make it ## What it does Gives every agent that has to write, design or check the material the same request at the same time. ## Where it happens The agent does this in one activity across three reference processes. Each one names the activity as that process words it. - **Brief the Makers** - `ref/mkt/account-based-play`, activity 7 - [Run Account-Based Play](../../../../processes/marketing/account-based-play.md) - `ref/mkt/enable-channel-partner`, activity 6 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - `ref/mkt/sales-enablement-kit`, activity 6 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. 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/find-the-material-a-change-touches/SKILL.mdSearches the material already in reps' hands for the pieces and the claims that a change puts in doubt, and lists what has to be revisited. Use it when running `ref/mkt/competitive-battlecard`.
--- name: find-the-material-a-change-touches description: Searches the material already in reps' hands for the pieces and the claims that a change puts in doubt, and lists what has to be revisited. Use it when running `ref/mkt/competitive-battlecard`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Find the material a change touches ## What it does Searches the material already in reps' hands for the pieces and the claims that a change puts in doubt, and lists what has to be revisited. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Find the Cards It Touches** - `ref/mkt/competitive-battlecard`, activity 3 - [Refresh Competitive Battlecard](../../../../processes/marketing/competitive-battlecard.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. 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/produce-the-selling-material/SKILL.mdAssembles what a seller or a partner uses in front of a customer, working from copy and design that have already been approved and keeping each claim tied to the proof behind it. Use it when running `ref/mkt/account-based-play` and 4 other reference processes.
--- name: produce-the-selling-material description: Assembles what a seller or a partner uses in front of a customer, working from copy and design that have already been approved and keeping each claim tied to the proof behind it. Use it when running `ref/mkt/account-based-play` and 4 other reference processes. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Produce the selling material ## What it does Assembles what a seller or a partner uses in front of a customer, working from copy and design that have already been approved and keeping each claim tied to the proof behind it. ## Where it happens The agent does this in five activities across five reference processes. Each one names the activity as that process words it. - **Build the Partner Selling Kit** - `ref/mkt/channel-program`, activity 7 - [Launch Channel Program](../../../../processes/marketing/channel-program.md) - **Make the Sales Material** - `ref/mkt/account-based-play`, activity 9 - [Run Account-Based Play](../../../../processes/marketing/account-based-play.md) - **Produce What Customers and Sellers Read** - `ref/mkt/pricing-change`, activity 6 - [Launch Pricing Change](../../../../processes/marketing/pricing-change.md) - **Produce the Partner Material** - `ref/mkt/enable-channel-partner`, activity 7 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Write the Card** - `ref/mkt/competitive-battlecard`, activity 7 - [Refresh Competitive Battlecard](../../../../processes/marketing/competitive-battlecard.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. 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/read-what-happens-in-deals/SKILL.mdGoes to the sellers for what they are running into inside live deals, including what the competitor is saying in front of a customer and what the won and lost deals turned on. Use it when running `ref/mkt/competitive-battlecard` and `ref/mkt/product-positioning`.
--- name: read-what-happens-in-deals description: Goes to the sellers for what they are running into inside live deals, including what the competitor is saying in front of a customer and what the won and lost deals turned on. Use it when running `ref/mkt/competitive-battlecard` and `ref/mkt/product-positioning`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Read what happens in deals ## What it does Goes to the sellers for what they are running into inside live deals, including what the competitor is saying in front of a customer and what the won and lost deals turned on. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Hear What Reps Are Meeting** - `ref/mkt/competitive-battlecard`, activity 4 - [Refresh Competitive Battlecard](../../../../processes/marketing/competitive-battlecard.md) - **Read What Happens Inside Deals** - `ref/mkt/product-positioning`, activity 5 - [Develop Product Positioning](../../../../processes/marketing/product-positioning.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/record-what-was-learned/SKILL.mdWrites down what is worth repeating next time and what to avoid, so the next run starts from it. Use it when running `ref/mkt/sales-enablement-kit`.
--- name: record-what-was-learned description: Writes down what is worth repeating next time and what to avoid, so the next run starts from it. Use it when running `ref/mkt/sales-enablement-kit`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Record what was learned ## What it does Writes down what is worth repeating next time and what to avoid, so the next run starts from it. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Record What Was Learned** - `ref/mkt/sales-enablement-kit`, activity 16 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. 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/release-the-material-to-sales/SKILL.mdPuts the signed version where a rep can find it while a deal is open, walks the people who will use it through what to say, and tells every one of them which version is current and from when. Use it when running `ref/mkt/competitive-battlecard` and 3 other reference processes.
--- name: release-the-material-to-sales description: Puts the signed version where a rep can find it while a deal is open, walks the people who will use it through what to say, and tells every one of them which version is current and from when. Use it when running `ref/mkt/competitive-battlecard` and 3 other reference processes. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Release the material to sales ## What it does Puts the signed version where a rep can find it while a deal is open, walks the people who will use it through what to say, and tells every one of them which version is current and from when. ## Where it happens The agent does this in five activities across four reference processes. Each one names the activity as that process words it. - **Brief Support and Sales** - `ref/mkt/feature-release`, activity 8 - [Announce Feature Release](../../../../processes/marketing/feature-release.md) - **Hand the Kit to Sales** - `ref/mkt/sales-enablement-kit`, activity 13 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) - **Hand the Story to Sales** - `ref/mkt/customer-case-study`, activity 19 - [Produce Customer Case Study](../../../../processes/marketing/customer-case-study.md) - **Issue the Version** - `ref/mkt/competitive-battlecard`, activity 13 - [Refresh Competitive Battlecard](../../../../processes/marketing/competitive-battlecard.md) - **Notify Sales** - `ref/mkt/competitive-battlecard`, activity 14 - [Refresh Competitive Battlecard](../../../../processes/marketing/competitive-battlecard.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/report-how-the-material-did/SKILL.mdReads who opened the material, who used it and which deals it touched, and reports that against the gap it was made to close. Use it when running `ref/mkt/sales-enablement-kit`.
--- name: report-how-the-material-did description: Reads who opened the material, who used it and which deals it touched, and reports that against the gap it was made to close. Use it when running `ref/mkt/sales-enablement-kit`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Report how the material did ## What it does Reads who opened the material, who used it and which deals it touched, and reports that against the gap it was made to close. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Report against the Gap** - `ref/mkt/sales-enablement-kit`, activity 15 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) - **Watch What Sales Does with It** - `ref/mkt/sales-enablement-kit`, activity 14 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/settle-the-objection-answers/SKILL.mdPairs each objection a seller meets with the answer it gets, and holds the proof that stands behind that answer. Use it when running `ref/mkt/sales-enablement-kit`.
--- name: settle-the-objection-answers description: Pairs each objection a seller meets with the answer it gets, and holds the proof that stands behind that answer. Use it when running `ref/mkt/sales-enablement-kit`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Settle the objection answers ## What it does Pairs each objection a seller meets with the answer it gets, and holds the proof that stands behind that answer. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Settle the Answers** - `ref/mkt/sales-enablement-kit`, activity 5 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/settle-the-obligations/SKILL.mdWrites down what each side has to deliver, which covers what this agent owes, what sales owes back, and what a partner has to be able to demonstrate before it sells. Use it when running `ref/mkt/enable-channel-partner` and `ref/mkt/sales-enablement-kit`.
--- name: settle-the-obligations description: Writes down what each side has to deliver, which covers what this agent owes, what sales owes back, and what a partner has to be able to demonstrate before it sells. Use it when running `ref/mkt/enable-channel-partner` and `ref/mkt/sales-enablement-kit`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Settle the obligations ## What it does Writes down what each side has to deliver, which covers what this agent owes, what sales owes back, and what a partner has to be able to demonstrate before it sells. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **List What the Partner Must Demonstrate** - `ref/mkt/enable-channel-partner`, activity 3 - [Enable Channel Partner](../../../../processes/marketing/enable-channel-partner.md) - **Settle What Each Side Owes** - `ref/mkt/sales-enablement-kit`, activity 2 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
skills/take-in-what-the-material-must-answer/SKILL.mdRecords what sellers cannot answer today and in which deals, or what a competitor has done and where it was seen, and settles what the material has to answer and by when. Use it when running `ref/mkt/competitive-battlecard` and `ref/mkt/sales-enablement-kit`.
--- name: take-in-what-the-material-must-answer description: Records what sellers cannot answer today and in which deals, or what a competitor has done and where it was seen, and settles what the material has to answer and by when. Use it when running `ref/mkt/competitive-battlecard` and `ref/mkt/sales-enablement-kit`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Take in what the material must answer ## What it does Records what sellers cannot answer today and in which deals, or what a competitor has done and where it was seen, and settles what the material has to answer and by when. ## 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 Gap** - `ref/mkt/sales-enablement-kit`, activity 1 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) - **Take in the Move** - `ref/mkt/competitive-battlecard`, activity 1 - [Refresh Competitive Battlecard](../../../../processes/marketing/competitive-battlecard.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. 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/try-the-material-on-reps/SKILL.mdPuts the finished material in the hands of a few reps to use in a real conversation, and records what held up and what did not. Use it when running `ref/mkt/sales-enablement-kit`.
--- name: try-the-material-on-reps description: Puts the finished material in the hands of a few reps to use in a real conversation, and records what held up and what did not. Use it when running `ref/mkt/sales-enablement-kit`. license: CC-BY-4.0 metadata: agent: sales-enablement-manager agent-version: "1" --- # Try the material on reps ## What it does Puts the finished material in the hands of a few reps to use in a real conversation, and records what held up and what did not. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Try the Kit on Reps** - `ref/mkt/sales-enablement-kit`, activity 12 - [Produce Sales Enablement Kit](../../../../processes/marketing/sales-enablement-kit.md) ## What to record Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did. 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 8 roles, and the access level beside each one is the most the work needs.
enablement-library · writeclaims-register · readbrand-guidelines · readasset-store · readcompetitive-record · readcrm · readusage-record-for-the-material · 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": {
"enablement-library": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/enablement-library"
},
"claims-register": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/claims-register"
},
"brand-guidelines": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/brand-guidelines"
},
"asset-store": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/asset-store"
},
"competitive-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/competitive-record"
},
"crm": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/crm"
},
"usage-record-for-the-material": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/usage-record-for-the-material"
},
"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
12 processes, 41 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.
Run Account-Based Playref/mkt/account-based-play · 19 activities
Brief the Makers · Make the Sales Material
Launch Channel Programref/mkt/channel-program · 17 activities
Build the Partner Selling Kit
Refresh Competitive Battlecardref/mkt/competitive-battlecard · 16 activities
Take in the Move · Find the Cards It Touches · Hear What Reps Are Meeting · Write the Card · Issue the Version · Notify Sales
Produce Customer Case Studyref/mkt/customer-case-study · 21 activities
Hand the Story to Sales
Enable Channel Partnerref/mkt/enable-channel-partner · 16 activities
List What the Partner Must Demonstrate · Brief the Makers · Produce the Partner Material · Answer the Partner's Questions
Announce Feature Releaseref/mkt/feature-release · 10 activities
Brief Support and Sales
Launch Pricing Changeref/mkt/pricing-change · 16 activities
Produce What Customers and Sellers Read
Develop Product Positioningref/mkt/product-positioning · 17 activities
Read What Happens Inside Deals
Produce Sales Enablement Kitref/mkt/sales-enablement-kit · 16 activities
Take in the Gap · Settle What Each Side Owes · Settle the Answers · Brief the Makers · Try the Kit on Reps · Hand the Kit to Sales · Watch What Sales Does with It · Report against the Gap · Record What Was Learned
Certify a Sellerref/rev/certify-a-seller · 17 activities
Build the Assessment · Run the Systems Check
Onboard a Sellerref/rev/onboard-a-seller · 17 activities
Teach the Product · Walk the Systems
Roll Out a Changeref/rev/roll-out-a-change · 17 activities
Take in the Change · Name Who Must Be Told · Name What Sellers Do Differently · Set the Date It Takes Effect · Check What Was Handed Over · Fill the Gaps in the Material · Build the Teaching · Tell the Managers First · Publish to One Address · Chase Who Is Missing · Report the Roll-Out
The records it leaves
What it writes down
Each piece at a numbered version, naming the gap it answers, the date it was issued and the date it stopped being current. Every claim in the material carries the register entry it rests on, with the version of that entry. The approval record behind each version, and a dated record of who was told the version changed. The standing readout at the cadence the process sets, saying which pieces reps opened, which they left alone, and what they reported as wrong. A retirement record for material taken out of the reps' hands, naming what replaced it or saying that nothing did.
Where it stops
What it will not do
Does not write the words or design the pages, which are the copywriter and designer agents, and does not edit the structure and the argument, which is the editor agent. Does not score the material against the brand guidelines or the claims register, which is the brand-check agent running its own pass, and does not score it against the disclosure rules in a market, which is the disclosure-check agent. Does not hold the standards it is scored against, which is the standards-keeper agent, and this agent asks that agent what a rule means when the text does not settle it. Does not go and find the evidence behind a competitor claim, which is the researcher agent. Does not run one published piece from topic to live, which is the content-manager agent, and does not answer for everything already on the site, which is the content-librarian agent, because the material this agent owns goes to reps rather than to the public. Does not sit in a deal, talk to a prospect or answer an objection in front of a customer, because the sales team does that and this agent gives them what to say. Does not set the price or the discount. Does not own a product launch and its deadline math, which is the launch-coordinator agent, and a kit built for a launch is a run of this agent reporting into it. Does not run the partner relationship or decide what a partner tier may be shown, which is the partner-manager agent, and this agent says which of its material is fit to leave the organization at all. Does not own the department's report for a reporting period, which is the reporting-manager agent. 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: sales-enablement-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.
- emplusx MCP server · emplusx.com · hosted · mirrored from the MCP registry Finished, on-brand .pptx and .docx from a brief - quality-gated by an agentic consulting team.
- Airtable Sales Ops Skill Skill · airtable.com Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender…
- eenable — a shop with no checkout MCP server · eenable.me · hosted · mirrored from the MCP registry Buy 15 minutes of Alex Finger's time, or an AI Repellent certificate. Agents only.