Communitygithub.com

cbrock84/sales-enablement

Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

sales-enablement란 무엇인가요?

sales-enablement is a Claude Code agent skill that builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

Sales enablement

Collateral gets used when it solves a problem the seller has in a live conversation. Everything else is filed and forgotten.

Know where deals actually stall

Before making anything, find where deals die: first call, after the demo, at pricing, at security review, at the champion's boss. Each stall has a different remedy, and building for the wrong one produces beautifully designed collateral nobody opens.

The core set

Pitch deck — a structure, not a script. Problem the buyer recognizes, why current approaches fail, what you do differently, proof, commercials, next step. Ten to fifteen slides, each with a takeaway headline.

One-pager — what the champion forwards internally to people you will never meet. It must survive being read with no context and no presenter. This is usually the highest-leverage asset and the most neglected.

Objection handling — the real objections, in the words prospects use, with responses that acknowledge the legitimate part first. A response that denies the objection reads as evasion and ends trust.

Battlecards — per competitor: where they genuinely win, where you do, the traps to avoid, and what to say when the prospect raises them. Cards claiming you win everywhere get ignored by sellers, who know better.

Case studies — situation, what changed, measurable result, in the buyer's language. One verifiable number beats a page of adjectives.

Demo

Demo the outcome, not the interface. Start where the value is visible, not at login and settings.

Tailor to the problem they told you about — a feature tour of everything demonstrates that you were not listening. Prepare for the three things that always go wrong, and know how to reach the value moment inside five minutes when time gets cut.

Maintaining

Collateral rots. Every asset needs an owner and a review date, and anything referencing pricing, competitors, or product capability needs checking every quarter. A battlecard describing a competitor's old product loses deals.

Never

  • Build collateral before you know where deals actually stall. Ask the reps and read the losses first.
  • Ship a deck or one-pager with no owner and no review date. Unmaintained collateral is worse than none.
  • Order a demo around the product's feature list instead of the order the buyer's problem unfolds in.
  • Count enablement as done at delivery. It is done when reps use it in live deals.

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

cbrock84/interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.

cbrock84/org-design

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

cbrock84/portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.

cbrock84/product-launch

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

cbrock84/program-management

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

cbrock84/project-delivery

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

cbrock84/retention

Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

cbrock84/tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.

cbrock84/unit-economics

Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

cbrock84/video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

cbrock84/visual-content

Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.

관련 스킬