Create structured handoff documents between GTM functions — sales-to-CS, SDR-to-AE, AE-to-SE, sales-to-implementation. Captures deal context, customer expectations, success criteria, risk flags, and action items so nothing falls through the cracks. Use this skill whenever a deal is closing and needs to transition to CS or implementation, when an SDR qualifies a lead for an AE, when a rep needs SE support, or when someone says "hand off this deal", "create a CS transition doc", "pass this lead to [rep]", "implementation kickoff", or when building handoff templates for the team.
Creates structured transition documents between sales, CS, and implementation teams using integrated CRM and call data.
/plugin marketplace add https://www.claudepluginhub.com/api/plugins/jbalbu01-sales-enablement-2/marketplace.json/plugin install jbalbu01-sales-enablement-2@cpd-jbalbu01-sales-enablement-2This skill inherits all available tools. When active, it can use any tool Claude has access to.
Create seamless transitions between GTM functions. The handoff between sales and CS is where most customer relationships break — the customer repeats everything they already told sales, expectations get lost, and trust erodes. This skill prevents that.
Every GTM handoff is a moment of risk:
Bad handoffs cost deals, create churn, and destroy cross-functional trust.
┌─────────────────────────────────────────────────────────────────┐
│ HANDOFF BUILDER │
├─────────────────────────────────────────────────────────────────┤
│ HANDOFF TYPES │
│ 1. SDR → AE — Lead context and qualification notes │
│ 2. Sales → CS — Full deal context and customer expectations │
│ 3. AE → SE — Technical requirements for demo/POC │
│ 4. Sales → Implementation — Scope, timeline, requirements │
│ 5. CS → Sales — Expansion signals and customer context │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Full deal data, contacts, company, and notes │
│ + ~~CRM: Deal timeline and stage progression history │
│ + ~~CRM: Associated contacts with roles and titles │
│ + ~~conversation intelligence (Gong): Key call transcripts │
│ + ~~conversation intelligence (Gong): Discovery insights │
│ + ~~conversation intelligence (Gong): Objections raised │
│ + ~~data enrichment (ZoomInfo): Company and contact profiles │
│ + ~~data enrichment (LinkedIn): Stakeholder backgrounds │
│ + ~~chat: Internal deal discussions and context │
│ + ~~calendar/email: Meeting history and correspondence │
└─────────────────────────────────────────────────────────────────┘
CRITICAL: Before asking for deal context, auto-populate the handoff from connected tools. A data-rich handoff is dramatically better than a form the rep fills out from memory.
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
If CRM tools ARE available:
deals for the company/deal name the user mentioned.
dealname, amount, dealstage, closedate, createdate, pipeline, hubspot_owner_id, dealtype, description, closed_won_reason, notes_last_contacted, num_notesfirstname, lastname, jobtitle, email, phone, company, lifecyclestagename, domain, industry, numberofemployees, annualrevenue, description, about_us, founded_year, countrycreatedate to closedate, note stage progression.Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
gong_search_calls with the company name and deal date range.gong_get_transcript on:
gong_get_call_details for topic coverage across the deal.ZoomInfo (if available):
zoominfo_search_company for the customer company.
zoominfo_get_org_chart for the customer.
LinkedIn (if available):
linkedin_get_profile for key contacts.
If chat tools are available (slack_search_public, slack_search_public_and_private):
If calendar/email tools are available:
"I auto-populated the handoff for [Company]: $[X] deal closed [date]. Per CRM, [N] contacts mapped across [roles]. Per Gong, I pulled transcripts from [N] calls — customer's key expectations: [summary]. [If ZoomInfo:] Company profile and org chart loaded. [If Slack:] Found [N] relevant internal discussions. The handoff document is [X]% pre-filled — just need your qualitative input on a few sections..."
After the auto-pull, ask ONLY for what the tools couldn't provide:
Build using ALL evidence. Pre-fill every section possible from tool data. Cite sources: "Per CRM:", "Per Gong (discovery call):", "Per ZoomInfo:", "Per Slack:", "Per Email:". Flag any sections where data is missing and user input is needed.
memory/deal-patterns.mdmemory/changelog.md# Lead Handoff: [Company Name]
**SDR:** [Name] | **AE:** [Name] | **Date:** [Date]
## Prospect Summary
| Field | Detail |
|-------|--------|
| Company | [Name, size, industry] |
| Contact | [Name, title, email, phone] |
| Source | [How they came in — inbound, outbound, event, referral] |
## Why They Took the Meeting
[What pain or interest did they express? Use their words.]
## Qualification Notes
| Criterion | What We Know |
|-----------|-------------|
| Pain | [Specific problem they mentioned] |
| Budget | [Any signal — allocated, looking for budget, unknown] |
| Authority | [Is this the decision-maker? Who else is involved?] |
| Timeline | [Any urgency driver or target date?] |
## Conversation History
[Summary of all touchpoints — emails, calls, content engagement]
## Suggested Approach for First Call
[Based on what the SDR learned, what should the AE focus on?]
## Red Flags
[Anything concerning — competitor already in play, low urgency, tire-kicking signals]
# Customer Handoff: [Company Name]
**AE:** [Name] | **CSM:** [Name] | **Date:** [Date]
**Deal Size:** $[amount] | **Contract Start:** [Date] | **Term:** [Duration]
## Customer Overview
| Field | Detail |
|-------|--------|
| Company | [Name, size, industry, HQ] |
| Primary Contact | [Name, title, email] |
| Executive Sponsor | [Name, title] |
| Technical Lead | [Name, title] |
## What They Bought and Why
[Clear description of: what was sold, which use cases they're deploying for, and the business problem they're solving. Don't just list SKUs — explain the intent.]
## Customer Expectations
[What did the customer explicitly say they expect to achieve? Use their words. This is the most important section — it's the promise CS needs to deliver on.]
### Success Criteria (Agreed with Customer)
1. [Specific, measurable outcome they expect]
2. [Second outcome]
3. [Third outcome]
### Timeline Expectations
| Milestone | Customer's Expected Date |
|-----------|------------------------|
| Go-live / first value | [Date] |
| Full rollout | [Date] |
| First business review | [Date] |
## Sales Cycle Context
### Key Decisions and Why
[What were the pivotal moments in the sale? What almost killed the deal? What won it?]
### Competitors Evaluated
[Who else they looked at and why they chose you — this helps CS reinforce the decision]
### Concerns Raised During Sales
[Any objections, hesitations, or risks the customer expressed. CS needs to know these so they don't resurface as churn risk.]
### Internal Champion
[Who advocated for you internally? CS should nurture this relationship.]
### Potential Blocker
[Anyone who was skeptical or opposed? CS should be aware.]
## Technical Context
| Item | Detail |
|------|--------|
| Integration requirements | [What needs to connect] |
| Data migration | [Scope of migration] |
| Technical constraints | [Known limitations or requirements] |
| Security/compliance | [Any special requirements] |
## Expansion Opportunity
[What wasn't included in this deal but could be a future upsell? What signals to watch for.]
## Risk Flags
| Risk | Severity | Mitigation |
|------|----------|------------|
| [Risk] | 🔴🟡🟢 | [What CS should do] |
## Attachments / References
- [Link to proposal]
- [Link to SOW]
- [Link to call recordings]
- [Link to CRM opportunity]
Brief but precise — what the SE needs to prep a demo or POC.
Scope, timeline, technical requirements, customer expectations, and known risks.
Every handoff gets scored on completeness:
| Section | Weight | Score |
|---|---|---|
| Customer context | 20% | [Complete / Partial / Missing] |
| Expectations & success criteria | 25% | [Score] |
| Risk flags | 15% | [Score] |
| Technical requirements | 15% | [Score] |
| Relationship context | 15% | [Score] |
| Action items | 10% | [Score] |
Overall: [X/100] — handoffs below 70 get flagged for additional information.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.