agentleFS
nnasrallnnasrall/uncommon-sales-skills/skills/champion-enablement/SKILL.md

champion-enablement

Skill2 starsChanged 25 days agoMITView on GitHub

Build the internal-selling kit your champion needs for the meetings you will not be in. Use this skill whenever a seller says "help me arm my champion", "champion enablement", "build a one-pager my champion can share internally", "prep my champion for their internal meeting", "how do I handle the skeptic on this deal", "the blocker I need to win over", "give me objection responses", "help my champion sell this up", or is trying to influence a buying decision that happens when they are not in the room. It pulls the deal from Loop first (falling back to CRM, call transcripts, and email), maps the internal buying group, writes a 30-second problem soundbite, builds objection reframes in the champion's own words, plans the skeptic, and drafts a forwardable one-pager. Prefer this over freehand internal-selling advice any time the deal depends on someone else carrying the message internally.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No champion, no deal. You are enabling a person to carry your message, not enabling a product.

    line 33
  2. Very specific:

    Loop first: If the Loop MCP (https://mcp.fluint.io/mcp) is connected, pull the deal, its stakeholders, and the recent meeting history.

    line 37
  3. Distinctive:

    No Loop? Detect what is live and fall back: Do not assume a vendor. In parallel:

    line 41
  4. Distinctive:

    Call transcripts (Salesloft, Gong, Clari, Chorus, Fathom, Fireflies.

    line 43
  5. Very specific:

    Read references/frameworks.md (Influence Map + buying-group roles).

    line 58
  6. Very specific:

    Read references/frameworks.md (4-Sentence Soundbite).

    line 66
  7. Distinctive:

    if we do, [the good outcomes],

    line 70
  8. Distinctive:

    if we do not, [the bad outcomes, getting worse].

    line 71
  9. Very specific:

    Read references/frameworks.md (Acknowledge-Diagnose-Redirect + the Urgency Equation).

    line 77
  10. Very specific:

    Read references/output-templates.md.

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Champion Enablement

What this does

Buyers close deals, not reps. The decision gets made in an internal meeting you are not invited to, and your champion is the one carrying your message into that room. If they carry it badly, you lose. So this skill builds the kit that lets them carry it well:

  1. A read on whether your contact is actually a champion, or just a friendly coach.
  2. A map of who they have to sell internally, and what each of those people cares about.
  3. A 30-second problem soundbite they can say to a skeptical exec.
  4. Objection reframes, in their words, for the pushback they will face.
  5. A plan for the specific skeptic or blocker on this deal.
  6. A forwardable one-pager: problem, cost of inaction, why now. Not a product pitch.

No champion, no deal. You are enabling a person to carry your message, not enabling a product.

Step 1: Lock the deal and qualify the champion

Loop first. If the Loop MCP (https://mcp.fluint.io/mcp) is connected, pull the deal, its stakeholders, and the recent meeting history. Loop already fuses the CRM, calls, and emails, so start there.

No Loop? Detect what is live and fall back. Do not assume a vendor. In parallel:

  • CRM (HubSpot, Salesforce, Attio, Pipedrive) = deal, stage, contact roles.
  • Call transcripts (Salesloft, Gong, Clari, Chorus, Fathom, Fireflies; or via Clay / Deepline) = who said what.
  • Email (Superhuman, Gmail, Outlook) = the working relationship and who is cc'd.

Then qualify your champion against the 3 I's (references/frameworks.md): Incentive, Influence, Information. A contact with Influence and Information but no Incentive is a coach, not a champion, and coaching you is not the same as spending capital for you. If the person is not a real champion, say so. The first move may be to develop or replace them, not to arm them.

Missing a source? Flag it, and make the gap a move. Mark it inline as [MISSING: ...] and continue. Every gap gets the single highest-leverage way to close it: the one question, to the one person, at the next touchpoint. Not "get more data."

Who can actually say yes? Name the people with the power to approve this, or to block it, and mark whether they are engaged yet. Power is often not in the room. If the deciders are absent or untouched, that is the headline, not a footnote.

Step 2: Map the internal meetings

Read references/frameworks.md (Influence Map + buying-group roles). Map who your champion has to win: the Economic Buyer, the Technical Evaluator, the Internal Skeptic, and any others. For each, note what outcome they care about and the proof point that lands. Same recommendation, different emphasis per person. That is respect for how different people decide, not manipulation.

Step 3: Write the 30-second problem soundbite

Read references/frameworks.md (4-Sentence Soundbite). Write the thing your champion can say in 30 seconds to a skeptical exec. Four sentences:

  • Because of [the change],
  • now is the time to [the approach] by [the date],
  • if we do, [the good outcomes],
  • if we do not, [the bad outcomes, getting worse].

Their language, not yours. Something they can actually say out loud without cringing.

Step 4: Build the objection reframes

Read references/frameworks.md (Acknowledge-Diagnose-Redirect + the Urgency Equation). Anticipate the top three objections your champion will face internally. For each, give them the reframe: acknowledge it, diagnose which urgency force is weak underneath it, and redirect to the real problem. Write the response in the champion's voice, not a rep's rebuttal.

Step 5: Plan the skeptic

There is usually one blocker who matters. Profile them: role, what they are protecting, the objections they will raise (spoken and unspoken). Give a reframe for each, and an engagement plan: do you go direct, or coach your champion to approach them. Convert the skeptic early and they become your best quality control and often your strongest advocate. They are not your enemy.

Step 6: Draft the forwardable one-pager

Read references/output-templates.md. Draft a one-pager the champion can forward internally. It is about the problem, the cost of inaction, and why now. It is not a product pitch, and it does not carry your logo. Camouflage. Put the champion's name on it, not yours. The best color scheme is their branding and their words, so it reads as internally authored.

Output format

Produce the kit using the skeleton in references/output-templates.md:

  1. Champion read (3 I's assessment + what to shore up)
  2. Internal meeting map (who to sell, what they care about, proof point)
  3. 30-second soundbite (the 4 sentences)
  4. Objection reframes (objection / diagnosis / the champion's response)
  5. The skeptic plan (profile, reframes, engagement)
  6. The forwardable one-pager

The operator's read

Before you hand it over, add the part a summary cannot: the one thing an experienced operator would notice that the data does not show on its own. The non-obvious risk. The stakeholder who matters more than their title. The deal that is not what it looks like. The strength that is quietly a trap. One or two sentences of judgment, called out plainly. Anyone can produce the map. This is the read.

Operating principles

  • No champion, no deal. Qualify the person before you arm them.
  • Enable a person, not a product. Everything is built for them to carry, not for you.
  • Camouflage, not a billboard. Their name, their words, no logo.
  • The skeptic is quality control, not the enemy. Convert them early.
  • Voice guard. Anything the buyer will read opens with their words, from the call or their own materials, in the first line. Banned openers: "Great connecting," "As discussed," "I wanted to follow up," "Hope this finds you well," "Circling back." If a sentence would survive being pasted into a different deal, it is too generic. Cut it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.