User / Buyer / Decider Map Agent Skill

Splits a buying situation into four distinct people — user (feels the pain, touches the product), buyer (owns the budget line)…

Context cost
9.5k tokensestimated from the bundle, loaded when it triggers
Bundle
13 files · 37.9 kBtext throughout, nothing executable
Licence
Apache-2.0the author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Splits a buying situation into four distinct people — user (feels the pain, touches the product), buyer (owns the budget line), decision-maker (final signature / veto), champion (spends internal capital to push it) — each pinned to ONE title, ONE budget (or an explicit none), ONE why-now. Fires on "who's the actual buyer", "who decides", "map the stakeholders", "map the buying committee", "the user loves it but who signs the cheque", "who's our champion and who can veto us". Output is a filled Stakeholder-Role Map that feeds the buyer-clarity row of problem-quality-scorecard.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

productivity

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md12.1 kB · preview
--- name: user-buyer-decider-map type: generator supersedes: none ---
18# User / Buyer / Decider Map
19
20## What it does
21Forces four names where the fellow wants one. Enterprise deals die because the fellow sold the user and never found the budget. This map separates the person who feels the pain from the person who pays, the person who signs, and the person who carries it inside the account — one title each, one budget each (users get an explicit "no budget," which is correct, not a gap), one why-now each. It also names the fifth face the happy-path map hides: whoever loses if the product ships. The output is a filled Stakeholder-Role Map ([template.md](template.md)). A buyer with no budget line and no why-now is not a buyer, and the map says so out loud, capping the buyer-clarity row of problem-quality-scorecard at 1.
22
23## The Icarus reframe
24A generic prompt hands back one portrait — a proto-persona with demographics and quotes, or an ideal-customer-profile with firmographics and LTV cohorts. Both describe "the customer" as a single person. Icarus asks the harder question: of the people around this purchase, exactly one owns the budget line the money leaves, and in a plant, a rig, or a data centre that person almost never feels the pain. The operator who suffers the workflow cannot sign a PO; the VP who signs never sees the workflow. So the artefact is not a cast list with attributes — it is a money-and-motion trace: who pays, from which line, and what makes each of them move *this quarter*. Miss the why-now and you have four people who nod and never act. Collapse user into buyer and you have a B2C fantasy pasted over an enterprise sale. The map exists to make both mistakes impossible to hide.
25
26## When to use / When NOT
27Use it when a fellow has a problem worth pursuing and needs to know who actually buys it, and how a deal through that account moves.
28
29| Situation | Use this? | Go to |
30|---|---|---|
31| "Who's the actual buyer? Who decides?" | Yes | user-buyer-decider-map |
32| "Map the stakeholders / the buying committee." | Yes | user-buyer-decider-map |
33| "The user loves it — but who signs the cheque?" | Yes | user-buyer-decider-map |
34| "Who's our champion, and who can quietly veto us?" | Yes | user-buyer-decider-map |
35| "Score the problem across 8 dimensions — go or no-go?" | No | problem-quality-scorecard |
36| "Which unmet need do we build for first?" | No | unserved-needs-finder |
37| "Write a demographic persona / a day-in-the-life." | No | proto-persona (absorbed — see Related) |
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md2,071 words
Files13
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈230
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
9,245
on trigger
The instruction body and 12 supporting files, read only when the skill fires.
4.7%
of a 200k window
Ten skills this size would take about 47% of the window before you open a file.
050k100k150k200k context window

9.5k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

13 files, 37.9 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md12.1 kB
  • template.md3.4 kB
  • examples/sample.md5.2 kB
  • tests/RESULTS.md4.7 kB
  • tests/rubric.json1.1 kB
  • tests/adversarial/01.md0.8 kB
  • tests/adversarial/02.md1.3 kB
  • tests/adversarial/03.md1.0 kB
  • tests/golden/01.md2.0 kB
  • tests/golden/02.md1.8 kB
  • tests/golden/03.md1.4 kB
  • tests/golden/04.md1.5 kB
  • tests/golden/05.md1.6 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 13 files you can review in full before installing. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# User / Buyer / Decider Map · 9.5k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/user-buyer-decider-map/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/user-buyer-decider-map" ] && { [ ! -e .claude/skills/user-buyer-decider-map ] || { mv .claude/skills/user-buyer-decider-map "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/user-buyer-decider-map" .claude/skills/ && echo "Installed .claude/skills/user-buyer-decider-map"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add the-utopia-studio/user-buyer-decider-map

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/user-buyer-decider-map/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/user-buyer-decider-map/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/user-buyer-decider-map" ] && { [ ! -e ~/.claude/skills/user-buyer-decider-map ] || { mv ~/.claude/skills/user-buyer-decider-map "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/user-buyer-decider-map" ~/.claude/skills/ && echo "Installed ~/.claude/skills/user-buyer-decider-map" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/user-buyer-decider-map/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencethe-utopia-studio/user-buyer-decider-map

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill