gtm-skills

Plugin gtm-skills from marketplace zime-gtm-skills in zime-ai/zime-gtm-skills. Commands read from the repo's manifest — 22 days ago.

Skills (71)

• account-plan-generator

  Writes a plan for one account from its call transcripts, listing the account's state, the people and their roles, what the customer wants, the open items and who owns each, and the gaps to close in the next 30 days, each tied to a quote. Use when a rep or manager asks to build an account plan, plan

• adoption-leaderboard

  Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibrat

• bant

  Audits a B2B sales call transcript against the BANT qualification framework (Budget, Authority, Need, Timeline) and credits only what the buyer said, or sweeps a CRM export for deals missing BANT fields. Use when the user asks to qualify a lead, run a BANT check, decide whether to advance a deal pas

• call-prep

  Writes a one-page prep for the next call on a deal, built only from the prior call transcripts, with where things left off, open commitments, what is still unknown, risks to raise, and a proposed agenda and ask. Use when a rep asks to prep for a call, wants a pre-call brief, or needs to know what to

• challenger

  Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when the user asks whether a rep brought a point of view or only asked discovery quest

• champion-tracker

  Tracks champion strength across a deal's call(s) — builds an action ledger, one row per named contact per cited quote, tagging each as either an act of internal selling (looping in a stakeholder, pushing back for the rep in a room the rep wasn't in) or mere positive sentiment (encouraging words, no

• channel-partner-engagement

  Audits a call with a channel partner to see whether the partner's real level of engagement was learned, with figures from the partner, their capacity, the customers they could reach, their last real activity, training status, and a dated joint plan. Use when the user asks how engaged a partner is, w

• churn-prevention

  Audits a renewal-risk or check-in call transcript against an eight-dimension churn and retention-signal rubric, crediting only what the customer said, or sweeps a CRM export for at-risk accounts missing renewal-risk data. Use when the user asks whether an account is at risk of churning, wants a cust

• client-testimonial-finder

  Finds quotable customer lines in a call transcript, keeping only specific lines that the customer said and that are fit to use, and sorts out the lines that are not usable, the lines that need the customer's permission, and the best three. Use when a rep or marketer asks to find testimonials, quotab

• coaching-plan

  Writes a short coaching plan for one rep from two or more of their call transcripts or audit outputs, naming the pattern that repeats, the question to practice, a drill, and how to check progress. Use when a manager asks for a coaching plan, wants to turn call reviews into one thing a rep can work o

• competitive-loss-digest

  Reads an export of lost deals and writes a digest of which rivals took deals and why, with counts, the amount lost to each rival, and whether each reason came from the buyer or from the rep. Use when a manager asks which competitors are winning, why deals are lost to a rival, or what the loss reason

• competitive-positioning

  Audits how a rep positioned the product against a named rival on a sales call, to see whether the difference was tied to the buyer's own criteria, backed by proof, honest about gaps, and tested by the buyer. Use when the user asks how well a rep handled a competitor, whether a rep differentiated or

• competitor-battlecard

  Reads a single sales call transcript and writes a battlecard for whichever competitor (or status quo) the buyer actually named on that call, covering how they framed it, what they said it does better or differently, what the rep countered with, and what went unanswered, citing every line to the tran

• crm-export

  Pulls open deals from the user's own connected CRM (HubSpot, Salesforce, Pipedrive, Close, Attio, Zoho, Dynamics) through a read-only connector, writes a local CSV with the column names the pipeline skills expect, then names the skill to run on it. Use when someone wants to run deal-risk-digest, for

• customer-success

  Audits a periodic QBR or account health-review call transcript against an eight-dimension rubric (value delivered, usage breadth, open issues, enablement gaps, stakeholder breadth, strategic alignment, forward fit, next check-in) and credits only what the customer said, or sweeps a CRM export for ac

• deal-desk-approval-brief

  Reads a pipeline export with discounts and writes an approval brief for the deal desk, listing the deals with a discount well above the export's own norm, what each approver still needs to see, and which approvals are open, with the cells behind each call. Use when a deal desk, finance partner, or m

• deal-highlights

  Writes a short highlights digest of one sales call — the moments that actually matter (a commitment, an objection, a buying signal, a competitive mention, a risk, a number that matters), each citing the quote it came from. Use when a rep needs something to skim or forward to a manager right after a

• deal-risk-digest

  Reads a pipeline export (a whole book of business, not one call) and ranks deals by risk (a past-due close date paired with low probability, stage age, a blank or vague next step, and a single-threaded contact, with deal value breaking ties), citing the column values behind each call. Use when a sal

• deep-discovery

  Audits an early-stage B2B sales discovery call transcript against a nine-dimension discovery rubric and credits only what the buyer actually said, or sweeps a CRM deal export for missing discovery fields. Use when the user asks to review a discovery call, score discovery quality, coach a rep on disc

• discount-pattern-digest

  Reads a pipeline export with discounts and finds the patterns, by owner and by outlier, naming an owner only when at least three deals support it, with the cells behind each call. Use when a sales leader or RevOps asks which reps discount the most, whether discounting is concentrated in a few deals,

• end-client-registration

  Audits a partner/reseller's end-client deal registration for completeness — partner identity, end-client entity kept distinct from the partner, engagement scope, conflict check against the direct pipeline, confirmed permission to engage the end-client contact, commercial terms, and an expiry window.

• evaluation-pipeline-check

  Sweeps a deal/pipeline export for technical evaluations running without defined success criteria, a technical champion, or an evaluation end date, and flags evaluations running long, stalled, or missing a security/procurement review relative to the export's own norms. Use when reviewing deals sittin

• executive-briefing

  Writes the short brief a rep sends upward out of one deal, to their own exec or the buyer's exec sponsor, covering deal snapshot, status, what is at risk, and the ask, each claim cited to a quote or a CSV column and cell. Use when someone who will never read the transcript needs to act on one deal,

• faint

  Audits a B2B sales call transcript against the FAINT qualification framework (Funds, Authority, Interest, Need, Timing) and credits only what the buyer said, or sweeps a CRM export for deals missing FAINT fields. Use when the user asks to qualify a demand-driven lead, or a prospect has not named a c

• first-call-rampup

  Audits a new rep's early sales call transcript against a six-technique foundational rubric (opening, open-ended questioning, pain uncovered, trigger surfaced, pitch clarity, rapport) and credits only what the buyer's replies show, as a coaching read. Use when the user asks to coach a newly ramped re

• follow-up-email-drafter

  Drafts the customer-facing follow-up email a rep sends after a sales call, grounding every recap, next step, and date in what the buyer actually said or agreed, plus a separate grounding-notes section flagging which lines are heard versus a proposal the rep should confirm before sending. Use right a

• forecast-review

  Reads a pipeline export with a forecast category and tests the commit list, naming the committed deals that do not hold up and why, with the cells behind each call and the value at risk. Use when a manager asks to review the forecast, sanity-check commit deals, or find deals in commit that should no

• handover-to-customer-success

  Writes the handover note that moves a signed deal from sales to Customer Success, built only from the sales calls, with why they bought, the success measure, the people, what was promised, gaps and open items, and key dates. Use when a deal is signed and CS needs the story, or when a rep asks for a

• ideal-channel-partner-profile

  Audits a first partner call to see whether it gathered the evidence to judge fit against an ideal partner profile, with the partner's relationship to buyers, current engagement with vendors, capacity, customer reach and technology habits, and marks missing evidence as insufficient and not as low. Us

• improve-demo

  Audits a product demo call transcript against a seven-dimension rubric (tailoring to stated priorities, stakeholders present, engagement, differentiation, fit with current tooling, success criteria, next step), or sweeps a CRM export for demos with no documented next step. Use when the user asks to

• loss-review

  Audits a debrief call with a buyer who chose another option or no option, to see whether the rep learned the real reason the deal was lost in the buyer's own words, and what would reopen it. Use when the user asks to review a loss debrief or a lost-deal interview, wants to know why a deal was really

• meddicc

  Audits a B2B sales call transcript against the MEDDICC qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition) and credits only what the buyer said, or sweeps a CRM export for deals missing MEDDICC fields. Use when the user asks to

• meddpicc

  Audits a B2B sales call transcript against the MEDDPICC qualification framework (Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition) and credits only what the buyer said, or sweeps a CRM export for deals missing MEDDPICC fields. Use when

• meeting-to-qualify

  Audits a qualification call transcript to assess whether a deal is real (problem urgency, authority, budget plausibility, timeline, fit, competition, engagement, next step) and credits only what the buyer said, or sweeps a CRM export for deals never properly qualified. Use when the user asks whether

• multi-threading

  Audits how widely a rep has engaged the buying group in a deal, to see whether the approver, a technical evaluator and daily users are known, reached and moving, or whether one contact carries the deal. Use when the user asks whether a deal is single-threaded, who else the rep should reach, or how t

• mutual-action-plan

  Writes a mutual action plan out of what was actually said on a call, with milestones from today to signature, each with an owner on both sides and a date, or fills date and stage gaps from a CRM export row. Use when a rep asks for a mutual action plan, a close plan, or a signature path to send a pro

• negotiation-closing

  Audits a late-stage negotiation call transcript against a six-dimension rubric (pricing reaction, procurement momentum, contracting awareness, closure timeline, budget confirmed, path to signature) and credits only what the buyer said and did, or sweeps a CRM export for late-stage deals with no docu

• negotiation-pipeline-check

  Sweeps a deal/pipeline export for deals in negotiation with no paper process started, no named approver on a discount, no credible close date, or no named signature path. Use when reviewing forecast-stage negotiation deals for whether they have a real mechanical path to signature, not just a stated

• new-business-registration

  Audits a new-logo deal-registration record, or the call/checkpoint where a rep registers a brand-new opportunity into pipeline, against general deal-registration practice covering entity identification, duplicate/conflict checking, source attribution, and ICP fit. Use when reviewing a fresh deal reg

• next-step-commitment

  Checks whether a sales call ended with a real, dated, mutually-owned next step versus a vague "we'll circle back." Use when the user asks whether a call moved a deal forward, wants to review how a call ended, coach a rep on closing a call out properly, or sweep a CRM export for deals stuck without a

• objection-pattern-digest

  Reads several call transcripts and lists the objections that repeat, grouped by theme, with the number of calls, a quote from each call, whether each was resolved on the call, and what the calls that resolved it did. Use when a manager asks what objections come up most, wants an objection digest acr

• onboarding-journey

  Audits a new-customer onboarding call transcript against a five-dimension rubric (onboarding experience, sentiment, early engagement, milestone clarity, early expansion signal) and credits only what the customer said or did, or sweeps a CRM export for onboarding accounts with no documented health si

• pain-finder

  Ranks the pain points surfaced in a sales call transcript by confidence and evidence, tagged by category, and keeps only pains the buyer owned in their own words. Use when a rep or manager asks what the prospect's real pain points are, which pain to lead with in a follow-up, or how pains changed acr

• partner-business-review

  Audits a partner business review call to see whether results against goals, pipeline with named customers, registration status, blockers with owners, support needs, next-period goals and a review date were pinned down in the partner's words. Use when the user asks to review a partner QBR, wants to k

• partner-competition-landscape

  Audits a call with a channel partner to see whether it learned which rival vendors the partner carries, how much of their business each is, what the rivals offer that the vendor does not, how terms compare in the partner's words, what would make the partner switch a customer, and any conflict rules.

• partner-decision-authority

  Audits a call with a channel partner to see whether it learned who decides on the partner side, how the decision is made, what the decider looks at, what the partner will commit, what competes for attention, and when the decision lands. Use when the user asks who decides at a partner, wants a partne

• partner-pain-points

  Audits a call with a channel partner to see whether the partner's own business problems were drawn out, with the problem in their words, its cost, who feels it, the root cause, what they already tried, and what would help. Use when the user asks what a partner's real problems are, wants a partner di

• partner-potential

  Audits a call about a deal a partner wants to bring, to see whether it is a real partner deal, with a named end customer, a fit that the partner and the customer both state, a purchase or registration step, a timeline, who sells and what terms apply. Use when the user asks whether a partner deal is

• partner-sentiment

  Audits a call with a channel or reseller partner to see whether the partner's real stance toward the vendor was learned, with their words, the action behind them, the rivals they favor, friction, long-term intent and a dated next step. Use when the user asks how a partner really feels, wants a partn

• persona-based-discovery

  Audits whether a discovery call's questions and framing were tailored to the specific buyer persona in the room (technical evaluator, economic buyer, end user, and so on), or sweeps a CRM export for deals with no persona or role data on contacts. Use when the user asks whether a rep adapted to who t

• pilot-to-conversion

  Audits a pilot or POC check-in call transcript against an eight-dimension rubric (plan, technical readiness, admin and security, setup, user engagement, feature feedback, results against criteria, conversion path) and credits only what the buyer said, or sweeps a CRM export for pilots at risk of sta

• pipeline-review

  Reads a pipeline export and writes the weekly review brief, with a snapshot by stage, what changed since a previous export, the deals that need attention, data gaps, and questions for the review. Use when a manager asks for a pipeline review, a pipeline snapshot, or a brief for a weekly pipeline mee

• poc-pilot-pipeline-check

  Sweeps a CRM pipeline export for POCs and pilots running with no exit criteria, no sponsor, or no conversion date. Use when RevOps or a manager wants a pipeline-wide read on which POCs/pilots can actually convert versus which are drifting with nothing written down. Also use when the user asks which

• poc-success

  Audits a POC or pilot exit review (did the pilot meet its agreed success criteria, and is the decision documented with evidence and sign-off), or sweeps a CRM export for deals past their POC end date with no recorded outcome. Use when a pilot has just wrapped and the user asks whether it genuinely p

• prospect-pipeline-check

  Sweeps a CRM pipeline export for prospect-stage deals with no real two-way engagement from the prospect side — the earliest "is this even a deal" gate, before budget, buyer, or pain are even in scope. Use when auditing a prospect-stage pipeline for zombie deals a rep is carrying forward on outbound

• qualify-pipeline-check

  Sweeps a CRM/pipeline export for deals that advanced past the Qualify stage without the facts that stage is supposed to establish — economic buyer, pain, budget signal, a close date consistent with the procurement cycle, a next step, and a qualification-framework record. Use when RevOps or a manager

• qualify-to-poc

  Audits the call or checkpoint that moves a qualified deal into POC or pilot kickoff (the go or no-go gate before pilot work starts) against five dimensions (success criteria, technical scope, stakeholder commitment, timeline and exit criteria, and resourcing). Or sweeps a CRM export for deals enteri

• reference-case-study-drafter

  Drafts a short customer case study from a customer call transcript, built only from what the customer said, with every sentence tied to a quote, the figures that need the customer's approval, what is missing, and the permission still needed. Use when a rep or marketer asks to draft a case study or r

• renewal-prep

  Writes the prep for an upcoming renewal from recent customer calls, with value in the customer's words, who uses it, risks to the renewal, open issues with owners, real expansion signals, and what to ask. Use when a CSM or account manager asks to prep a renewal, wants a renewal brief, or needs to kn

• rep-ramp-status-digest

  Reads a new rep's calls over several weeks and writes a ramp status by technique (opening, questioning, pain, trigger, pitch, rapport), marking each as improving, flat, regressing, or not enough evidence, with a quote from each call. Use when a manager asks how a new rep is ramping, wants a ramp sta

• sandler

  Audits a B2B sales call transcript against the Sandler Selling System submarine (Bonding and Rapport, Up-Front Contract, Pain, Budget, Decision, Fulfillment, Post-Sell), or sweeps a CRM export for deals missing Sandler-relevant fields. Use when the user asks whether a rep pitched before earning the

• security-legal-review

  Audits a call about a buyer's security review, questionnaire, data-protection terms or legal redlines, to see whether the process is mapped, owned and dated before it stalls the deal. Use when the user asks to review a security or legal call, wants to know whether a deal's paper steps are under cont

• sell-the-dream

  Audits a B2B sales call transcript for future-state vision selling, meaning whether the rep names the world change and the stakes before pitching product, or leads with features and bolts a vision on afterward. It scores against Andy Raskin's publicly published 5 Elements of a Great Sales Narrative,

• sql-to-qualify

  Audits the first call after a sales-qualified lead (SQL) hand-off to see whether there is a real opportunity worth a rep's time (right contact, pain in the buyer's own words, rough budget and urgency fit, competitive awareness, and a concrete next meeting) and credits only what the buyer said, or sw

• stuck-deal-digest

  Reads a pipeline export and lists the deals that have stopped moving, grouped by how they are stuck (silent, aged in stage, or an overdue next step), with the cell values behind each call and one question per deal. Use when a manager asks which deals are stuck, wants a list of stalled deals before a

• technical-discovery

  Audits a technical or solution-fit call transcript against a seven-dimension rubric (current stack, future-state vision, POC scope, technical stakeholders, success metrics, resourcing, next step) and credits only what the buyer said, or sweeps a CRM export for deals missing technical-fit data. Use w

• territory-summary

  Reads an account export with territory, owner, open deals, and last activity, and summarizes coverage by territory, how concentrated the open amount is in one account, and which accounts have gone quiet, with the cells behind each call. Use when a sales leader or RevOps asks to review territories, c

• upsell-expansion

  Audits an expansion or upsell call transcript against an eight-dimension rubric (account health, a concrete ask, champion strength, confidence, strategic alignment, open risks, enablement, next step) and credits only what the customer said, or sweeps a CRM export for expansion opportunities missing

• wbr-report-generator

  Reads a pipeline export, and a previous one when given, and writes the numbers section of a weekly business review, with headline numbers, movement, risks to next period, and what the export cannot tell. Use when a leader asks for a WBR, a weekly sales report, or the numbers for a weekly business re

• win-loss-brief

  Writes a structured brief on why one specific deal was won or lost, with the outcome, 3-5 cited drivers (competitive displacement, champion strength or loss, pricing/procurement friction, timing, technical fit), and forward-looking notes for a similar deal. Use when the user asks why a deal was won

• won-pipeline-check

  Sweeps a closed-won deal export for missing handoff and record data the post-sale team needs — CS owner, kickoff date, signed value/term, contract reference, and date/stage consistency. Use when a deal desk or RevOps person wants to check closed-won deals before they hand off to onboarding/CS, or au

Similar plugins