Comprehensive sales and revenue operations skill. Use when building a sales team, doing founder-led sales, hiring first sales reps, navigating enterprise deals, implementing product-led sales, designing sales compensation plans, defining ICP, mapping buyer personas, or optimizing the revenue engine (RevOps). Activates for: sales strategy, rev ops, revenue operations, sales enablement, sales compensation, ICP, ideal customer profile, buyer persona, sales process, deal execution, lead scoring, lead routing, lead lifecycle, MQL, SQL, pipeline management, CRM automation, sales qualification, BANT, MEDDIC, founder sales, enterprise sales, product-led sales, startup sales, SDR, AE, quota, ramp, commission plan.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.
This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.
Full-stack sales playbook: founder-led sales, team building, enterprise deals, RevOps, ICP definition, buyer personas, and compensation design.
┌─────────────────────────────┐
│ BUYING CENTER │ ← All decision stakeholders
├─────────────────────────────┤
│ USER PERSONA │ ← Daily user
├─────────────────────────────┤
│ BUYER PERSONA │ ← Signs the check
├─────────────────────────────┤
│ COMPANY PROFILE │ ← Firmographics
└─────────────────────────────┘
Company Profile: industry/vertical, size (employees/revenue), stage, geography, tech stack
Buyer Persona: title/role, seniority, goals & KPIs, decision authority, what they care about
User Persona: daily workflow, pain points, tech savviness
Buying Center Roles: Champion, Economic Buyer, Technical Evaluator, End User, Blocker
| Factor | Weight |
|---|---|
| Problem severity | 25% |
| Budget available | 20% |
| Champion identified | 15% |
| Technical fit | 15% |
| Decision timeline | 15% |
| Expansion potential | 10% |
List 50 specific companies that fit. Find the buyer's name at 20 of them. Reach out to 10. If you can't do this, your ICP isn't specific enough.
For full persona canvases, buying center maps, interview questions, and fit scoring: see references/full-guide.md
Core principles:
When to hire: Wait until ~$1M ARR and a repeatable process. Hire in pairs — you need an A/B test.
Hiring framework:
| Stage | Who to Hire | When |
|---|---|---|
| Founder-led | Nobody | Before $1M ARR |
| First AEs | 2 reps | After proven repeatability |
| SDRs | 1-2 | When inbound overflows |
| VP Sales | 1 | When 2+ reps hitting quota |
Buying committee roles: Champion (internal advocate), Economic Buyer (signs), Technical Buyer (evaluates), End User (uses daily), Blocker (can say no)
JOLT method for indecision:
Key tactics:
BANT: Budget · Authority · Need · Timeline
MEDDIC: Metrics · Economic Buyer · Decision Criteria · Decision Process · Identify Pain · Champion
Rule: Qualify ruthlessly. "No" is a successful outcome. Disqualify on the first call if fit isn't there.
Opening (2 min) → Discovery Recap (3 min) → Solution Walkthrough (15-20 min) → Interaction → Close (5 min)
| Category | Response Approach |
|---|---|
| Price | ROI angle, payment terms |
| Timing | Urgency, cost of delay |
| Competition | Differentiation, unique value |
| Authority | Arm the champion |
| Status quo | Cost of inaction |
| Stage | Owner | Entry Criteria |
|---|---|---|
| Subscriber | Marketing | Opts in to content |
| Lead | Marketing | Basic info provided |
| MQL | Marketing | Fit + engagement threshold |
| SQL | Sales | Accepted, qualified via call |
| Opportunity | Sales AE | BANT confirmed |
| Customer | CS | Closed-won |
MQL = Fit Score (who they are) + Engagement Score (what they do). Neither alone qualifies.
MQL-to-SQL SLA: Contact within 4 hours; qualify or reject within 48 hours.
Explicit (fit): Company size, industry, title, tech stack
Implicit (engagement): Pricing page visits, demo requests, email clicks, product usage
Negative: Competitor domains, student emails, unsubscribes
| Method | Best For |
|---|---|
| Round-robin | Equal territories |
| Territory-based | Regional/vertical teams |
| Account-based | Named accounts / ABM |
| Skill-based | Complex deals, multi-product |
Speed-to-lead: Contact within 5 minutes = 21x more likely to qualify. After 30 minutes, conversion drops 10x.
For routing decision trees and automation playbooks: see references/routing-rules.md, references/automation-playbooks.md
| Metric | Target |
|---|---|
| Lead-to-MQL rate | 5-15% |
| MQL-to-SQL rate | 30-50% |
| SQL-to-Opportunity | 50-70% |
| Win rate | 20-30% |
| Speed-to-lead | <5 minutes |
| LTV:CAC ratio | 3:1 to 5:1 |
For scoring models and lifecycle definitions: see references/scoring-models.md, references/lifecycle-definitions.md
Standard structure: 50% base / 50% variable (OTE). This is a starting point, not a law.
Modern comp plans align with customer outcomes, not just bookings. Reps who close churny deals should earn less than those who close sticky customers.
Ramp periods: 3-6 months for SMB, 6-12 months for enterprise. Provide guaranteed draw or reduced quotas during ramp.
Simplicity rule: If reps can't instantly calculate how an action affects their pay, the plan is too complex.
Common mistakes:
For detailed comp frameworks: see references/guest-insights.md
| Metric | What It Tells You |
|---|---|
| Win rate | Sales effectiveness |
| Sales cycle length | Process efficiency |
| Pipeline coverage | Forecast reliability (target 3-4x quota) |
| Lead-to-Opportunity | Qualification quality |
| CAC | Acquisition efficiency |
| Quota attainment | Rep performance |
outbound-email-strategy — Cold outreachpricing-strategy — Pricing decisionsgo-to-market-strategy — Full launch planningまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see data-and-funnel-analytics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, managing, or optimizing paid advertising campaigns across any platform. Covers ad copy generation, ad creative strategy, campaign management, and competitive intelligence. Triggers on: ad copy, ad creative, paid ads, paid advertising, Facebook ads, LinkedIn ads, Google ads, Meta ads, ad campaign, ad strategy, ad testing, competitive ads, competitor ads, ad library, ad analysis, ad creative generation, campaign management, ROAS, CPC, CTR. Use this skill whenever the user mentions ads, paid channels, ad campaigns, ad copy, ad performance, or wants to analyze competitor advertising.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content
日本語の概要は準備中です。原文の説明を表示しています。
Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Use this skill whenever the user wants to set up a new project, onboard a brand, start from scratch, configure their marketing context, or initialize their workspace. Trigger on: bootstrap, onboard, set up my project, get started, configure my brand, initialize, new project setup, brand onboarding, set up my brand, create project structure, onboard my company, set up content folders, prepare my workspace, start a new GTM project. Also use when the user seems to be starting fresh and hasn't set up strategy/brand.md or about/me.md yet.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive brand messaging, positioning, and value proposition development using proven frameworks including Peep Laja Message Layers, Osterwalder Value Proposition Canvas, Geoffrey Moore positioning, April Dunford's Five Components, StoryBrand SB7, Andy Raskin Strategic Narrative, and Messaging House. Use when developing brand identity, brand messaging architecture, positioning statements, value propositions, messaging hierarchies, brand pillars, taglines, one-liners, elevator pitches, brand guidelines, visual identity systems, or creating Positioning & Messaging Packs. Triggers include: messaging framework, brand positioning, value prop, messaging architecture, brand pillars, brand identity, StoryBrand, positioning statement, brand guidelines, design system, messaging house, corporate identity, brand voice, visual standards.
日本語の概要は準備中です。原文の説明を表示しています。