Agent skill
sales-one-pager
Build the one-page document a champion forwards internally to sell your product when you are not in the room.
Filed under Calls, demos and discovery.
From vcxcvii/pipeline-skills · 10 skill entries · 0 · pushed 2026-09-25
What it does when it runs
Build the one-page document a champion forwards internally to sell your product when you are not in the room. Covers the stall point, the business case, objection handling, and the procurement questions. Use when deals stall after a good demo, when reps rebuild the pitch themselves, or when the user asks for a leave-behind, battlecard, or enablement asset.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/vcxcvii/pipeline-skills.git /tmp/pipeline-skills git -C /tmp/pipeline-skills sparse-checkout set "skills/sales-one-pager" mkdir -p ~/.claude/skills/sales-one-pager cp -R "/tmp/pipeline-skills/skills/sales-one-pager/." ~/.claude/skills/sales-one-pager/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 10 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add vcxcvii/pipeline-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from vcxcvii/pipeline-skills/blob/d284df833e7dd2f21ff15384461ea6fcd3f454c4/skills/sales-one-pager/SKILL.md, which is licensed MIT (repository). 451 words, 12 headings.
Sales One-Pager (B2B SaaS)
Most enablement assets answer the questions marketing finds interesting. This one answers the question the champion gets asked by their boss: "why are we spending money on this now?"
Setup
Ask for:
- The deal stage where things stall most often (post-demo, security review, pricing, procurement, no-decision)
- Two recent losses and what the buyer said in the last email
- Who the champion is, and who they have to convince
If the user cannot name the stall point, ask for two recent call recordings or transcripts and find it yourself. Do not proceed on a guess: an asset built for the wrong stall never gets opened twice.
Structure the page
1. The situation, in the buyer's words
Two sentences describing the problem using language from the calls. If the champion does not recognise their own situation in the first two lines, the document is dead.
2. What changes
The specific outcome, with the metric it moves and a realistic timeframe. Not "increase efficiency". Something like "cuts the weekly close from three days to one, measured on the finance team's own calendar".
3. The business case
Three lines: the cost of the status quo, the cost of the product, and what has to be true for the numbers to work. Include the assumption. A champion who presents a business case with a hidden assumption loses credibility when their CFO finds it.
4. Objection handling, for the objections that actually come up
Four objections maximum, taken from real calls. For each: the objection in the buyer's words, the honest answer, and the proof. Never write a defensive competitor comparison. State what the alternative is genuinely good at, then where it stops.
5. The procurement block
Security posture, data handling, contract length, and implementation effort. Boring, and the most-read section in any enterprise deal.
6. The next step
One action, with the owner and the timeframe. Not "let us know if you have questions".
Output
- The one-pager in markdown, ready to paste into a doc, under 500 words
- A three-line version for a Slack forward
- The list of evidence you had to invent or leave blank, so the user fills it in
Rules
- Never fabricate security certifications, customer names, or numbers.
- Write for the person who was not on the demo call.
- One page means one page. Cut the third adjective, not the procurement block.
- No em-dashes, no superlatives, no "trusted by leading companies" without names.
Related skills
positioning-canvas for the claim this document carries.
customer-story-extractor for the proof it needs.
landing-page-teardown when the same message has to work unattended.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- one-pager by octavehq · 11
- sales-enablement by coreyhaines31 · 53,460
- sales-pipeline by ericosiu · 3,608
- sales-playbook by ericosiu · 3,608
- sales by zubair-trabzada · 1,407
- sales-competitors by zubair-trabzada · 1,407
- sales-contacts by zubair-trabzada · 1,407
- sales-followup by zubair-trabzada · 1,407
Need help setting it up?
This page tells you what sales-one-pager does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.