Creator relations
creator-relations v1Keeps the record of the outside creators the organization pays to publish, and runs each deal from the first approach to the last delivery. The agent matches creators to an audience the organization wants to reach, checks that the audience is real before anybody is offered money, reads what the creator has already published and says whether the history is clean, makes the approach, and holds what was agreed: the deliverables, the dates, the usage rights and the fee. It keeps watching after the creator publishes, and when a check finds a problem with what was published it goes back to the creator and records what it asked for and what the creator did. Every other agent that plans work around a creator reads this record before it commits to one.
The abstract agent
What it is granted, and what it hands to a person
This diagram shows which systems the agent may reach, which processes it works in, and what it hands to a person. Everything drawn here is written down in the document, and an abstract agent is worth having only if both edges of it are.
Sits in the briefing that opens a campaign needing outside creators in it, and brings which creators fit the audience, what each of them charges, and what each of them has already agreed to. Holds the examiner role in an assessment when it scores candidate creators: the criteria are named and versioned before reading starts, every candidate gets a verdict, and every verdict cites the criterion behind it. Requests the approval before an offer goes out, and again before a deal is agreed, because the fee and the usage rights are what the organization commits to. Answers roll-calls with where each creator stands, which is approached, negotiating, agreed, delivered or declined. Reports into collect-and-report once the campaign is over, covering what each creator was paid for, what they published, and what the checks found in it.
The plugin
What is in the package
8 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.
creator-relations · 13 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 what a creator posts. Creators write their own words, and the copywriter agent writes the brief they are given and everything the organization publishes itself. Does not score published material against the disclosure rules, which is the disclosure-check agent; this agent writes the disclosure requirement into the deal and goes back to the creator when that agent reports a failure. Does not score material against the brand guidelines or the claims register, which is the brand-check agent. Does not decide which audience the campaign is trying to reach, which is the audience-manager agent, and this agent matches creators to the definition that agent holds. Does not run the campaign the creators sit inside, which is the campaign-manager agent. Does not buy placement and does not put money behind a creator's post, which is the media-buyer agent. Does not ask a customer to go public, which is the advocacy-manager agent. Does not approach reporters, editors or industry analysts, which is the press-relations agent. Does not hold a partner relationship that ends in the partner selling, which is the partner-manager agent. Does not keep the organization's record of licensed footage, music, images and appearance releases, which is the rights-register agent, and it hands that agent the usage rights each deal grants. Does not record what the outside world publishes about the organization in general, which is the coverage-monitor agent. Does not reply on the organization's own channels and does not act on posts that break the community rules, which are the community-manager and moderator agents. Does not pay anybody and does not sign anything. ## What always goes to a person - a fee, a contract, or anything else that has to be signed, always, because a person signs - a creator whose audience the checks say is bought or inflated, when a run wants that creator anyway - something in a creator's past publishing that the organization would not want to be associated with - a creator who publishes work that breaks what was agreed, such as a missing disclosure, a claim the register does not support, or a date that was not the agreed one, raised immediately, because a person decides whether the work is corrected, taken down or left alone - a creator who wants to say something the organization has not approved - a creator who will not grant the usage rights the campaign was planned around, before any other work is commissioned on the strength of that creator - a creator who becomes the subject of a public argument while their work for the organization is still running
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 `creator-relations` leaves
the following behind, on every run.
For each creator, the record holds the audience figures with the date
they were read and the source they came from, what the authenticity
check found, and what the history check found in the creator's past
publishing. For each deal, it keeps what was agreed at the version it
was agreed: every deliverable, the date each one is due, the channels
the work may run on, how long the organization may use it, what the
disclosure has to say, and the fee. Every approach lands with its date,
what was offered, and the answer that came back, including the creators
who declined and the reason they gave. When a creator publishes, the
agent records what went out, where it went out, and on what date. When a
check finds a problem, the agent records the finding, what it asked the
creator to do, the date it asked, and what the creator did.
An agent that leaves less than this does not implement
`creator-relations`, 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
Eleven 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 creator record | write | Every creator, their audience figures, their history and the terms they hold. |
| the deal record | write | What was agreed with each creator, at the version it was agreed. |
| the contact log | write | Every exchange with a creator lands here on the day it happened. |
| the outreach channel | write | Cap: how many creators it may approach without asking, set by the adopting organization. |
| audience measurement sources | read | The figures behind a creator's reach, and the checks on whether that reach is real. |
| the published work record | read | What each creator posted and what the checking agents found in it. |
| the audience definitions | read | The audience the campaign is trying to reach. |
| the claims register | read | |
| brand guidelines | read | |
| the disclosure rule record | read | What a paid partnership has to say in each market the work will run in. |
| the asset store | read | The material a creator is given, at the versions that were signed. |
There is deliberately no payment grant. This agent records the fee that
was agreed and the date it falls due, and a person releases the money.
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": "creator-relations",
"version": "1.0.0",
"description": "The creator-relations abstract agent. Keeps the record of the outside creators the organization pays to publish, and runs each deal from the first approach to the last delivery.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/creator-relations",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"marketing",
"influencer-campaign",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "creator-relations",
"agentVersion": 1,
"department": "marketing",
"abstract": true,
"works": "Sits in the briefing that opens a campaign needing outside creators in it, and brings which creators fit the audience, what each of them charges, and what each of them has already agreed to. Holds the examiner role in an assessment when it scores candidate creators: the criteria are named and versioned before reading starts, every candidate gets a verdict, and every verdict cites the criterion behind it. Requests the approval before an offer goes out, and again before a deal is agreed, because the fee and the usage rights are what the organization commits to. Answers roll-calls with where each creator stands, which is approached, negotiating, agreed, delivered or declined. Reports into collect-and-report once the campaign is over, covering what each creator was paid for, what they published, and what the checks found in it.",
"servers": [
{
"name": "the creator record",
"role": "creator-record",
"access": "write",
"needs": "Every creator, their audience figures, their history and the terms they hold."
},
{
"name": "the deal record",
"role": "deal-record",
"access": "write",
"needs": "What was agreed with each creator, at the version it was agreed."
},
{
"name": "the contact log",
"role": "contact-log",
"access": "write",
"needs": "Every exchange with a creator lands here on the day it happened."
},
{
"name": "the outreach channel",
"role": "outreach-channel",
"access": "write",
"needs": "Cap: how many creators it may approach without asking, set by the adopting organization."
},
{
"name": "audience measurement sources",
"role": "audience-measurement-sources",
"access": "read",
"needs": "The figures behind a creator's reach, and the checks on whether that reach is real."
},
{
"name": "the published work record",
"role": "published-work-record",
"access": "read",
"needs": "What each creator posted and what the checking agents found in it."
},
{
"name": "the audience definitions",
"role": "audience-definitions",
"access": "read",
"needs": "The audience the campaign is trying to reach."
},
{
"name": "the claims register",
"role": "claims-register",
"access": "read"
},
{
"name": "brand guidelines",
"role": "brand-guidelines",
"access": "read"
},
{
"name": "the disclosure rule record",
"role": "disclosure-rule-record",
"access": "read",
"needs": "What a paid partnership has to say in each market the work will run in."
},
{
"name": "the asset store",
"role": "asset-store",
"access": "read",
"needs": "The material a creator is given, at the versions that were signed."
}
],
"records": [
"For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing.",
"For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee.",
"Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave.",
"When a creator publishes, the agent records what went out, where it went out, and on what date.",
"When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator did."
],
"escalates": [
"a fee, a contract, or anything else that has to be signed, always, because a person signs",
"a creator whose audience the checks say is bought or inflated, when a run wants that creator anyway",
"something in a creator's past publishing that the organization would not want to be associated with",
"a creator who publishes work that breaks what was agreed, such as a missing disclosure, a claim the register does not support, or a date that was not the agreed one, raised immediately, because a person decides whether the work is corrected, taken down or left alone",
"a creator who wants to say something the organization has not approved",
"a creator who will not grant the usage rights the campaign was planned around, before any other work is commissioned on the strength of that creator",
"a creator who becomes the subject of a public argument while their work for the organization is still running"
],
"not": [
"Does not write what a creator posts.",
"Creators write their own words, and the copywriter agent writes the brief they are given and everything the organization publishes itself.",
"Does not score published material against the disclosure rules, which is the disclosure-check agent; this agent writes the disclosure requirement into the deal and goes back to the creator when that agent reports a failure.",
"Does not score material against the brand guidelines or the claims register, which is the brand-check agent.",
"Does not decide which audience the campaign is trying to reach, which is the audience-manager agent, and this agent matches creators to the definition that agent holds.",
"Does not run the campaign the creators sit inside, which is the campaign-manager agent.",
"Does not buy placement and does not put money behind a creator's post, which is the media-buyer agent.",
"Does not ask a customer to go public, which is the advocacy-manager agent.",
"Does not approach reporters, editors or industry analysts, which is the press-relations agent.",
"Does not hold a partner relationship that ends in the partner selling, which is the partner-manager agent.",
"Does not keep the organization's record of licensed footage, music, images and appearance releases, which is the rights-register agent, and it hands that agent the usage rights each deal grants.",
"Does not record what the outside world publishes about the organization in general, which is the coverage-monitor agent.",
"Does not reply on the organization's own channels and does not act on posts that break the community rules, which are the community-manager and moderator agents.",
"Does not pay anybody and does not sign anything."
],
"processes": [
{
"process": "ref/mkt/influencer-campaign",
"activities": [
"Draw up the Candidate List",
"Vet the Candidates",
"Clear the Shortlist",
"Approach the Creators",
"Settle the Terms",
"Brief the Creators",
"Collect the Drafts",
"Review the Drafts",
"Publish the Posts",
"Record the Live Posts",
"Correct What Failed"
]
}
]
}
}
}
README.mdWhat the package is, and why it carries no mcp.json.
# creator-relations 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 eight 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/influencer-campaign`. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/creator-relations
skills/agree-a-deal/SKILL.mdMakes the approach to a creator, finds out whether they are interested, and works through the terms until both sides hold the same deliverables, dates, usage rights, disclosure wording and fee. Use it when running `ref/mkt/influencer-campaign`.
--- name: agree-a-deal description: Makes the approach to a creator, finds out whether they are interested, and works through the terms until both sides hold the same deliverables, dates, usage rights, disclosure wording and fee. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # Agree a deal ## What it does Makes the approach to a creator, finds out whether they are interested, and works through the terms until both sides hold the same deliverables, dates, usage rights, disclosure wording and fee. Every exchange lands in the contact log on the day it happened. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Approach the Creators** - `ref/mkt/influencer-campaign`, activity 7 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) - **Settle the Terms** - `ref/mkt/influencer-campaign`, activity 8 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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-a-creator/SKILL.mdTells a creator what the campaign is for and what the work has to say, and hands over the material they are allowed to use. Use it when running `ref/mkt/influencer-campaign`.
--- name: brief-a-creator description: Tells a creator what the campaign is for and what the work has to say, and hands over the material they are allowed to use. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # Brief a creator ## What it does Tells a creator what the campaign is for and what the work has to say, and hands over the material they are allowed to use. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Brief the Creators** - `ref/mkt/influencer-campaign`, activity 10 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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/chase-what-the-deal-owes/SKILL.mdTracks what a creator still owes against the dates in the deal and goes back to them for it, whether that is a deliverable that has not arrived or a fix to something already published. Use it when running `ref/mkt/influencer-campaign`.
--- name: chase-what-the-deal-owes description: Tracks what a creator still owes against the dates in the deal and goes back to them for it, whether that is a deliverable that has not arrived or a fix to something already published. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # Chase what the deal owes ## What it does Tracks what a creator still owes against the dates in the deal and goes back to them for it, whether that is a deliverable that has not arrived or a fix to something already published. It records the date it asked, what it asked for, and what the creator did. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Collect the Drafts** - `ref/mkt/influencer-campaign`, activity 11 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) - **Correct What Failed** - `ref/mkt/influencer-campaign`, activity 16 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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/get-the-shortlist-cleared/SKILL.mdTakes the creators who survived the checks to the people who have to accept who the organization pays, and records the answer against each name. Use it when running `ref/mkt/influencer-campaign`.
--- name: get-the-shortlist-cleared description: Takes the creators who survived the checks to the people who have to accept who the organization pays, and records the answer against each name. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # Get the shortlist cleared ## What it does Takes the creators who survived the checks to the people who have to accept who the organization pays, and records the answer against each name. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Clear the Shortlist** - `ref/mkt/influencer-campaign`, activity 6 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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/match-creators-to-an-audience/SKILL.mdSearches the creator record for people whose following matches the audience a campaign wants to reach, and returns a candidate list with the audience figures that put each name on it. Use it when running `ref/mkt/influencer-campaign`.
--- name: match-creators-to-an-audience description: Searches the creator record for people whose following matches the audience a campaign wants to reach, and returns a candidate list with the audience figures that put each name on it. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # Match creators to an audience ## What it does Searches the creator record for people whose following matches the audience a campaign wants to reach, and returns a candidate list with the audience figures that put each name on 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. - **Draw up the Candidate List** - `ref/mkt/influencer-campaign`, activity 4 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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/review-a-draft/SKILL.mdReads a creator's draft against the rules the deal set and says whether it can run as it is or what has to change first. Use it when running `ref/mkt/influencer-campaign`.
--- name: review-a-draft description: Reads a creator's draft against the rules the deal set and says whether it can run as it is or what has to change first. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # Review a draft ## What it does Reads a creator's draft against the rules the deal set and says whether it can run as it is or what has to change first. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Review the Drafts** - `ref/mkt/influencer-campaign`, activity 12 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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/see-the-posts-go-live/SKILL.mdConfirms each agreed post goes out on the date it was promised, and keeps a copy of what actually ran, where it ran and when. Use it when running `ref/mkt/influencer-campaign`.
--- name: see-the-posts-go-live description: Confirms each agreed post goes out on the date it was promised, and keeps a copy of what actually ran, where it ran and when. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # See the posts go live ## What it does Confirms each agreed post goes out on the date it was promised, and keeps a copy of what actually ran, where it ran and when. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Publish the Posts** - `ref/mkt/influencer-campaign`, activity 13 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) - **Record the Live Posts** - `ref/mkt/influencer-campaign`, activity 14 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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/vet-a-creator/SKILL.mdChecks a named creator before anybody is offered money. Use it when running `ref/mkt/influencer-campaign`.
--- name: vet-a-creator description: Checks a named creator before anybody is offered money. Use it when running `ref/mkt/influencer-campaign`. license: CC-BY-4.0 metadata: agent: creator-relations agent-version: "1" --- # Vet a creator ## What it does Checks a named creator before anybody is offered money. It reads the audience figures against the measurement sources to see whether the reach is real, reads what the creator has already published, and records what each check found and the date it was run. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Vet the Candidates** - `ref/mkt/influencer-campaign`, activity 5 - [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md) ## What to record For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator 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 11 roles, and the access level beside each one is the most the work needs.
creator-record · writedeal-record · writecontact-log · writeoutreach-channel · writeaudience-measurement-sources · readpublished-work-record · readaudience-definitions · readclaims-register · readbrand-guidelines · readdisclosure-rule-record · readasset-store · read
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": {
"creator-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/creator-record"
},
"deal-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/deal-record"
},
"contact-log": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/contact-log"
},
"outreach-channel": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/outreach-channel"
},
"audience-measurement-sources": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/audience-measurement-sources"
},
"published-work-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/published-work-record"
},
"audience-definitions": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/audience-definitions"
},
"claims-register": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/claims-register"
},
"brand-guidelines": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/brand-guidelines"
},
"disclosure-rule-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/disclosure-rule-record"
},
"asset-store": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/asset-store"
}
}
}
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
One process, 11 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 Influencer Campaignref/mkt/influencer-campaign · 16 activities
Draw up the Candidate List · Vet the Candidates · Clear the Shortlist · Approach the Creators · Settle the Terms · Brief the Creators · Collect the Drafts · Review the Drafts · Publish the Posts · Record the Live Posts · Correct What Failed
The records it leaves
What it writes down
For each creator, the record holds the audience figures with the date they were read and the source they came from, what the authenticity check found, and what the history check found in the creator's past publishing. For each deal, it keeps what was agreed at the version it was agreed: every deliverable, the date each one is due, the channels the work may run on, how long the organization may use it, what the disclosure has to say, and the fee. Every approach lands with its date, what was offered, and the answer that came back, including the creators who declined and the reason they gave. When a creator publishes, the agent records what went out, where it went out, and on what date. When a check finds a problem, the agent records the finding, what it asked the creator to do, the date it asked, and what the creator did.
Where it stops
What it will not do
Does not write what a creator posts. Creators write their own words, and the copywriter agent writes the brief they are given and everything the organization publishes itself. Does not score published material against the disclosure rules, which is the disclosure-check agent; this agent writes the disclosure requirement into the deal and goes back to the creator when that agent reports a failure. Does not score material against the brand guidelines or the claims register, which is the brand-check agent. Does not decide which audience the campaign is trying to reach, which is the audience-manager agent, and this agent matches creators to the definition that agent holds. Does not run the campaign the creators sit inside, which is the campaign-manager agent. Does not buy placement and does not put money behind a creator's post, which is the media-buyer agent. Does not ask a customer to go public, which is the advocacy-manager agent. Does not approach reporters, editors or industry analysts, which is the press-relations agent. Does not hold a partner relationship that ends in the partner selling, which is the partner-manager agent. Does not keep the organization's record of licensed footage, music, images and appearance releases, which is the rights-register agent, and it hands that agent the usage rights each deal grants. Does not record what the outside world publishes about the organization in general, which is the coverage-monitor agent. Does not reply on the organization's own channels and does not act on posts that break the community rules, which are the community-manager and moderator agents. Does not pay anybody and 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: creator-relations 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.
- Historis MCP server · svenlc.github.io · hosted · mirrored from the MCP registry The memory of your business: an event-based CRM your assistant reads and writes, dated and signed.
- CHAP Coordinator MCP server · brightbeamai.github.io · run it yourself · mirrored from the MCP registry Auditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.
- Runlog MCP server · runlog.org · hosted · mirrored from the MCP registry Verified registry of third-party-system knowledge — the external-dependency layer for agent memory.