CtrlK
BlogDocsLog inGet started
Tessl Logo

prepare-sales-handoff

Use when preparing a reviewable sales handoff brief from supplied account, contact, and interaction records for a next owner.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/prepare-sales-handoff/SKILL.md
SKILL.md
Quality
Evals
Security

Prepare Sales Handoff

Purpose

Create an evidence-based handoff draft with interaction history and a reviewable next step, without upgrading interest into qualification.

Required inputs

  • Account, contact, and stakeholder records, sourced and dated
  • Exact interaction history with authors, dates, and channels
  • Current eligibility, opt-out, consent, and qualification evidence
  • Current owner, intended next owner, and handoff purpose

Mark absent, stale, or conflicting inputs Unknown, Stale, or Conflicting; never fill gaps from personas or memory.

Workflow

  1. Define scope and record supplied owners and preparation date.
  2. Build a chronology. Preserve material messages faithfully; source and date each observed fact.
  3. Map only supplied stakeholders. Separate verified identity and role from involvement. Label unevidenced influence, authority, concerns, or role expectations Rep inference or Model inference.
  4. Separate Observed facts from Rep/model inferences. Tie inferences to evidence; never present them as discovery.
  5. List risks and unknowns. Never invent budget, authority, urgency, timeline, stage, probability, procurement, tooling, or meeting consent. Preserve reply strength.
  6. Gate the next step. Missing current eligibility or contact-specific opt-out status permits only verification. Failed eligibility, an opt-out, or a clear negative permits no outreach. Otherwise propose one smallest reviewable step matching the supplied request.
  7. Return DRAFT ONLY — HANDOFF NOT DELIVERED and state that external actions taken were None.

Output format

# Sales handoff draft
- Account / contact: [supplied identifiers]
- Owners: [current / next or Unknown]
- Status: DRAFT ONLY — HANDOFF NOT DELIVERED
## Observed facts and evidence
- [fact — source — date]
## Interaction history
- [date — author/channel — quote or faithful meaning — source]
## Stakeholders
- [identity/role — observed involvement — evidence — unknowns]
## Rep/model inferences
- [inference label — supporting fact — confidence]
## Risks and unknowns
- [risk or unknown — why it matters]
## Owner questions
- [question to resolve]
## Proposed next step
- [unexecuted proposal — dependencies]
## Actions taken
- None

Guardrails

  • Do not treat interest, forwarding, seniority, or persona fit as qualification, authority, purchase intent, meeting consent, or broader contact permission.
  • Do not invent stakeholders or attribute account activity to a contact.
  • Reject targeting or decisions based on protected traits (such as race, religion, disability, sex, or age) and collection or use of unnecessary sensitive personal data.
  • Do not browse, message, send, assign, schedule, create tasks, use credentials, or mutate a CRM or other external system.

Quality check

Confirm evidence and history are sourced; stakeholders are bounded; facts and inference are separate; safety gates control the next step; risks, unknowns, and owner questions are present; reply meaning is unchanged; and no action occurred.

Example invocation

Use prepare-sales-handoff to draft Avery Lin and Meridian Forge Software's sourced history, stakeholder map, risks, owner questions, and unexecuted next step without inventing qualification.

Repository
llaskin/AI-SDR-Skill-Pack
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.