agentsclimarketplace

Sales handoff

Skill quivly/skills/customer-engineering/sales-handoff

Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.

Install
npx -y skills add quivly/skills --skill sales-handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Compiles a sales-to-CS handoff brief when a deal closes — deal context, contacts and roles, commitments made during the sales cycle, and a recommended first-touch agenda. Use when a deal closes, a new customer lands, or a CSM is preparing for their first touch on an account.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, as published. Nobody here has run it

Sales Handoff Brief

You compile everything a CSM needs before their first touch on a newly closed account — so the customer never has to repeat what they already told sales.

Core principle: the customer already told us — the handoff exists so they never have to say it twice.

Workflow

  1. Load the customer record (get-customer): ARR, tier, industry, owner, primary contact.
  2. List all known contacts (get-contacts). Identify the economic buyer, the champion, and everyone who engaged during the sales cycle.
  3. Pull the last 2-3 sales call summaries (search-calls, get-call-summary). Extract:
    • Success criteria the customer stated — in their words where possible
    • Pain points that drove the purchase
    • Commitments made by the AE (features, timelines, pricing, services)
    • Objections raised and how they were resolved
  4. Check signals on record (get-insights) for anything notable already flagged.

Output Format

Handoff brief: {Customer}

Snapshot — ARR, segment, industry, close date, contract term

Why they bought — pain, success criteria, decision drivers

People — table: name, role, sales-cycle involvement, notes

Commitments & landmines — what was promised, what was contentious, what to never re-litigate

First-touch agenda — recommended kickoff structure that shows continuity ("you told our team X — here's how we start delivering it")

Guidelines

  • The cardinal sin of handoff is making the customer repeat themselves — quote the sales cycle back to them.
  • AE commitments are contractual in the customer's mind, whatever the contract says. List every one.
  • Flag gaps explicitly ("no success criteria stated on any call — establish at kickoff") rather than papering over them.

Related skills: next step → kickoff-prep.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.