Use when the user is working a B2B SaaS deal from qualified opportunity to closed-won — preparing discovery calls, structuring demos or POCs, handling a specific objection, qualifying with MEDDIC/MEDDPICC/SPICED, building mutual action plans, navigating negotiation or procurement, or reviewing pipeline health, forecast accuracy, and deal velocity. Not for finding or prospecting new leads (use prospecting) or upstream positioning (use product-position).
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill coaches on converting qualified B2B SaaS pipeline into closed revenue. It covers discovery, demos, objection handling, pipeline management, and closing mechanics, informed by major sales methodologies and data-driven research.
Deliver only what the user will actually use. Never leak internal scaffolding into the output:
Apply frameworks silently — name one only when it helps the reader, not to show your work. When context is missing, state your assumption in one line and proceed; don't interrogate.
Before giving advice, understand the user's situation along these dimensions:
Infer from context; if genuinely missing, state your assumption and proceed. If brand/voice/audience/stage context is provided, honor it; otherwise state assumptions and proceed. Match the depth of any clarifying questions to the complexity of the ask — don't over-interview.
For data points, benchmarks, framework details, and methodology comparisons, read references/sales-knowledge-base.md. This file contains the full reference material including Gong research findings, pipeline benchmarks, methodology breakdowns, and framework-specific guidance.
When to read it: Always read the relevant section before giving detailed advice. The table of contents below maps topics to sections:
| Topic | Section in KB |
|---|---|
| Methodology selection/comparison | §1 (all subsections) |
| Methodology combinations | §1.8 |
| Discovery call structure, questions, mistakes | §2 |
| Demo narrative, technical vs business, POC | §3 |
| Objection handling frameworks, psychology | §4 |
| Pipeline metrics, coverage, velocity, forecasting | §5 |
| Negotiation, MAPs, procurement, consensus | §6 |
Do not prescribe a single methodology. Instead:
Tailor all recommendations to deal size:
Always ground advice in specific actions:
Reference specific research findings when relevant (from the knowledge base):
Based on what the user needs, operate in one of these modes:
Generate a call plan including:
Design a demo plan including:
For a specific objection:
Analyze pipeline health:
For a specific deal:
Design closing mechanics:
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when a B2B SaaS founder needs to choose, prioritize, or rebalance customer acquisition channels — deciding outbound vs inbound, paid vs PLG, where to put marketing budget, or sanity-checking CAC, LTV:CAC, and payback. Also for channel-specific playbooks (cold email, LinkedIn, paid social, community, partnerships) and channel-mix audits. Not for closing tactics (use sales-skill) or copy (use copywriter-skill).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to write, rewrite, review, or critique commercial copy meant to drive a reader toward action — landing pages, hero sections, headlines, email (cold outreach, nurture, promo, launch), CTAs, microcopy, product descriptions, value propositions, ads, or taglines. Also for copy audits, clarity checks, conversion reviews, or choosing a framework (AIDA, PAS, BAB, FAB, 4U's). Applies even when the user just says "write me an email" or "review this page." Not for channel/budget strategy (use channel-expert) or pricing structure (use pricing).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a non-designer needs to audit a UI, generate a design spec (spacing, type scale, color tokens, grids), or build brand foundations (logo systems, palette and type pairing, brand guidelines). Covers the visual layer, UX/perceptual critique, and brand identity. For implementing the design in code (React/HTML/CSS), use frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to deploy, operate, secure, or scale running infrastructure — cloud architecture (multi-region, VPC, FinOps), CI/CD and deployment strategies, secrets/IAM/supply-chain security, observability and SLO alerting, SRE and incident response, Kubernetes vs ECS and autoscaling, Terraform/Pulumi/CDK, or platform engineering and DORA metrics. Also for generating runbooks, pipeline configs, Terraform modules, or Kubernetes manifests. For choosing the system's architecture or stack before it runs (monolith vs microservices, which database), use software-architect.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning, auditing, or speccing a video's motion and visual craft: shot lists, storyboards, color scripts, transitions, easing, kinetic typography, pacing, retention, or animation principles. Triggers: 'video plan', 'shot list', 'storyboard', 'color script', 'motion spec', 'fix the pacing', 'explainer/demo/brand video'. For the spoken words themselves, use script-writer-skill; for in-code UI motion, use frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。