agentleFS
nnasrallnnasrall/uncommon-sales-skills/skills/sales-plays/SKILL.md

sales-plays

Skill2 starsChanged 25 days agoMITView on GitHub

The front door to the Uncommon Sales Skills toolbox. Use this skill when a seller describes a deal situation but has not named a specific play, or asks which play they need: "help me with this deal", "what should I do next on [account]", "I'm stuck, not sure what I need here", "coach me through this deal", "which play fits", "where is this deal and what's my move". It reads the situation, names the deal moment, and routes to the right skill in the toolbox. Prefer a specific skill (call-prep, multithread, deal-advancement, etc.) when the seller clearly names that need; use this router only when the need is ambiguous or the seller wants to be pointed to the right play.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the seller has clearly named a specific need (for example "prep me for my call" or "why is this deal stuck"), let that skill fire …

    line 24
  2. Distinctive:

    When more than one fits, name the two most likely and let the seller pick.

    line 46
  3. Distinctive:

    Every play in this toolbox runs the same way, so set the expectation up front:

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Sales Plays (the front door)

What this does

This is the router for the Uncommon Sales Skills toolbox. When a seller describes a deal but has not picked a play, it figures out where the deal actually is and points to the right skill. It exists so a rep never has to memorize ten skill names. Describe the situation, and this gets you to the move.

If the seller has clearly named a specific need (for example "prep me for my call" or "why is this deal stuck"), let that skill fire instead. This router is for the ambiguous case.

How to route

First, get just enough context to place the deal. Ask one or two questions if the moment is unclear: what account, what just happened or is about to happen, and what the seller is trying to get to next. Then match to the play.

The seller's situationRoute to
New account, or a live deal riding on one contact that needs more coveragemultithread
Needs a POV, an account plan, or wants to find expansion whitespaceaccount-planning
Has a call, demo, or discovery coming up and wants to walk in readycall-prep
Just had a call or group demo and needs to follow up and lock the problemcall-follow-up
Needs to arm a champion to sell internally, or handle a skeptic or blockerchampion-enablement
Up against an incumbent or competitor and needs to change the gamecompetitive-displacement
Ready to make the executive case for the dealone-page-business-case
Deal has stalled, or needs a mutual action plan to drive to closedeal-advancement
Prepping a customer quarterly review or renewal conversationqbr-prep
Prepping a forecast call or deal review with their own leadershipmanage-up

When more than one fits, name the two most likely and let the seller pick. A deal often needs a sequence (for example: multithread now, then call-prep for the exec meeting, then one-page-business-case). Say so, and start with the one that unblocks the rest.

The through-line

Every play in this toolbox runs the same way, so set the expectation up front:

  • It pulls the deal context (Loop first, then CRM, calls, and email).
  • It writes in the buyer's own language, built to be forwarded. Camouflage, not a billboard.
  • It flags what is missing and names the one move to close the gap.
  • It ends in a deliverable, plus an operator's read: the judgment a summary hides.

Operating principles

  • Place the deal first. A play run on the wrong moment wastes the run. One or two questions beats a confident guess.
  • Point, do not lecture. Name the play and hand off. The chosen skill does the work.
  • Name the sequence. Deals move through moments. Say what comes after the play you start with.

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.