@gonzih/skills-sales 1.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 gonzih
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,56 @@
+# skills-sales
+
+Claude Code skills for sales reps, account executives, and business development professionals.
+
+## Install
+
+```bash
+npx @gonzih/skills-sales
+```
+
+Then restart Claude Code.
+
+## Skills
+
+### `/discovery-call-prep`
+Prepare for a discovery call with research questions, pain hypothesis, competitor differentiators, and a talk track outline.
+
+```
+/discovery-call-prep Sarah Chen at Acme Corp — VP of Engineering
+```
+
+### `/proposal-writer`
+Write a professional sales proposal with executive summary, solution fit, pricing table, ROI estimate, and next steps.
+
+```
+/proposal-writer Acme Corp — slow deployment pipeline, manual QA — CI/CD platform — $50k budget
+```
+
+### `/objection-handler`
+Generate structured responses to sales objections — price, timing, competitor, need — with reframe scripts and follow-up questions.
+
+```
+/objection-handler "We're already using Jenkins and it works fine"
+```
+
+### `/deal-review`
+Analyze a deal's health with MEDDIC scoring, risk flags, stakeholder gaps, and prioritized next actions.
+
+```
+/deal-review Acme Corp — Proposal — Champion is a senior engineer, no EB access, close date Q2
+```
+
+## What you get
+
+Each skill produces a structured markdown output you can paste directly into your CRM, Google Docs, Notion, or email — no reformatting needed.
+
+| Skill | Output |
+|---|---|
+| `discovery-call-prep` | Research summary, pain hypotheses, discovery questions, competitor differentiators, talk track |
+| `proposal-writer` | Exec summary, problem statement, solution fit table, pricing table, ROI model, next steps |
+| `objection-handler` | Objection classification, acknowledge opener, reframe script, proof point, follow-up questions |
+| `deal-review` | MEDDIC scorecard, risk flags, stakeholder map, momentum assessment, next actions |
+
+## License
+
+MIT

package/install.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { copyFileSync, mkdirSync, existsSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+
+const skillsDir = join(homedir(), '.claude', 'skills');
+const skills = ['discovery-call-prep', 'proposal-writer', 'objection-handler', 'deal-review'];
+
+for (const skill of skills) {
+  const dest = join(skillsDir, skill);
+  if (!existsSync(dest)) mkdirSync(dest, { recursive: true });
+  copyFileSync(new URL(`./skills/${skill}/SKILL.md`, import.meta.url).pathname, join(dest, 'SKILL.md'));
+  console.log(`✓ Installed /${skill}`);
+}
+console.log('\nSkills installed! Restart Claude Code to use them.');

package/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "@gonzih/skills-sales",
+  "version": "1.0.0",
+  "description": "Claude Code skills for sales reps, account executives, and business development professionals.",
+  "type": "module",
+  "bin": {
+    "skills-sales": "./install.js"
+  },
+  "scripts": {
+    "postinstall": "node install.js"
+  },
+  "files": [
+    "skills/",
+    "install.js",
+    "README.md",
+    "LICENSE"
+  ],
+  "keywords": [
+    "claude-code",
+    "claude-code-skills",
+    "sales",
+    "discovery-call",
+    "proposal",
+    "objection-handling",
+    "meddic",
+    "deal-review",
+    "account-executive",
+    "business-development"
+  ],
+  "author": "gonzih",
+  "license": "MIT",
+  "engines": {
+    "node": ">=18.0.0"
+  }
+}

package/skills/deal-review/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: deal-review
+description: Analyze a deal's health with MEDDIC scoring, risk flags, missing stakeholders, and recommended next actions.
+triggers: ["review deal", "deal review", "deal health", "MEDDIC", "analyze deal", "deal score"]
+---
+
+# Deal Review
+
+## What this skill does
+Given a deal summary — stage, stakeholders, use case, timeline, and budget signals — this skill produces a structured deal health assessment. It scores the deal against the MEDDIC framework, surfaces risk flags, identifies stakeholder gaps, and recommends prioritized next actions to advance or save the deal.
+
+## How to invoke
+/deal-review [deal name or company] — [current stage] — [deal summary or CRM notes]
+
+## Workflow steps
+
+### Step 1 — MEDDIC Scorecard
+Score each MEDDIC dimension on a 0–2 scale (0 = unknown/missing, 1 = partially confirmed, 2 = fully confirmed). Provide a brief justification for each score based on the deal inputs.
+
+| Dimension | Score (0–2) | Status | Evidence / Gap |
+|---|---|---|---|
+| **M** — Metrics | | | |
+| **E** — Economic Buyer | | | |
+| **D** — Decision Criteria | | | |
+| **D** — Decision Process | | | |
+| **I** — Identify Pain | | | |
+| **C** — Champion | | | |
+
+Compute a total MEDDIC score (out of 12) and a deal health label: **Strong** (10–12), **Developing** (6–9), **At Risk** (0–5).
+
+### Step 2 — Risk Flags
+Identify the top 3–5 risk signals in the deal. Common risk categories:
+- **Stakeholder risk** — No access to economic buyer; single-threaded into one contact
+- **Timeline risk** — No triggering event; artificial or vague close date
+- **Competitive risk** — Incumbent entrenched; evaluation started with a competitor
+- **Champion risk** — Champion lacks authority or internal credibility
+- **Budget risk** — No confirmed budget; deal size misaligned with company profile
+- **Process risk** — Procurement or legal involvement not scoped; unknown approval steps
+
+For each flag, note severity (High / Medium / Low) and the specific signal from the deal that triggered it.
+
+### Step 3 — Stakeholder Map
+List all known stakeholders with their role, level of engagement (Champion / Supporter / Neutral / Blocker / Unknown), and last touch date if available. Then identify the critical missing stakeholders that should be engaged before the deal closes: typically the economic buyer, a technical validator, and a procurement/legal contact.
+
+### Step 4 — Deal Momentum Assessment
+Assess whether the deal has forward momentum or is stalling. Look for: time since last meaningful touchpoint, whether the prospect has completed their agreed next steps, whether the close date has slipped, and whether the champion is actively selling internally. Classify as **Advancing**, **Stalled**, or **At Risk of Going Dark**.
+
+### Step 5 — Recommended Next Actions
+Provide 3–5 prioritized next actions ranked by impact on deal health. For each action include: what to do, who owns it (rep, champion, AE), and the goal it addresses (MEDDIC gap, risk mitigation, or momentum). Format as a short action table with a suggested completion date.
+
+## Example outputs
+A structured deal review document with a completed MEDDIC scorecard and total score, a ranked risk flag list with severity labels, a stakeholder map with engagement status, a momentum classification, and a prioritized next-actions table. Suitable for pipeline reviews, forecasting calls, or deal strategy sessions with a manager.

package/skills/discovery-call-prep/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: discovery-call-prep
+description: Prepare for a discovery call with research questions, pain hypothesis, competitor differentiators, and a talk track outline.
+triggers: ["prep discovery call", "discovery call prep", "prepare for discovery", "discovery prep", "call prep"]
+---
+
+# Discovery Call Prep
+
+## What this skill does
+Given a prospect name, company, and deal context, this skill generates a comprehensive discovery call preparation kit. It produces targeted research questions, a pain hypothesis based on industry and role signals, competitor differentiators, and a structured talk track outline to guide the conversation.
+
+## How to invoke
+/discovery-call-prep [prospect name] at [company] — [role/context]
+
+## Workflow steps
+
+### Step 1 — Prospect & Company Research Summary
+Summarize what is known or inferable about the prospect's company: industry, size, likely tech stack, recent news signals (funding, hiring, product launches), and business priorities. Identify the prospect's role and typical pain points for that persona.
+
+### Step 2 — Pain Hypothesis
+Formulate 3–5 pain hypotheses ranked by likelihood. Each hypothesis should follow the format: "We believe [company] is experiencing [pain] because [signal], which is causing [business impact]." These guide the questions you'll ask to confirm or disconfirm.
+
+### Step 3 — Discovery Questions
+Generate 10–15 open-ended discovery questions organized by category:
+- **Situation** — understand current state and context
+- **Problem** — surface pain and urgency
+- **Implication** — expand impact of the problem
+- **Need-payoff** — connect solution value to their goals
+
+### Step 4 — Competitor Differentiators
+List the top 2–3 likely competitors the prospect may be evaluating or currently using. For each, provide 2–3 crisp differentiators that favor your solution, framed as discovery questions or statements you can weave naturally into conversation.
+
+### Step 5 — Talk Track Outline
+Produce a time-boxed talk track for a 45-minute discovery call:
+- **0–5 min** — Rapport, agenda setting, confirm time
+- **5–15 min** — Situation questions, company/role context
+- **15–30 min** — Problem and implication questions, pain confirmation
+- **30–40 min** — Solution positioning, differentiator moments
+- **40–45 min** — Next steps, mutual action plan
+
+## Example outputs
+A structured markdown document with five labeled sections: company summary, ranked pain hypotheses, categorized discovery questions, competitor comparison table, and a time-boxed talk track. Ready to paste into a call notes doc or CRM.

package/skills/objection-handler/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: objection-handler
+description: Generate responses to common sales objections — price, timing, competitor, need — with reframe scripts and follow-up questions.
+triggers: ["handle objection", "objection response", "deal objection", "they said too expensive", "overcome objection"]
+---
+
+# Objection Handler
+
+## What this skill does
+Given a specific objection raised by a prospect, this skill generates a structured response playbook. For each objection type it produces an acknowledgment opener, a reframe that shifts the conversation, a proof point or bridge, and a follow-up question to re-engage and advance the deal. Covers price, timing, competitor, and need objections.
+
+## How to invoke
+/objection-handler [objection text or type] — [deal context (optional)]
+
+## Workflow steps
+
+### Step 1 — Classify the Objection
+Identify the objection category and root cause:
+- **Price** — "Too expensive," "Not in budget," "Need a discount"
+- **Timing** — "Not now," "Bad timing," "Maybe next quarter"
+- **Competitor** — "We're evaluating X," "We already use Y," "X is cheaper"
+- **Need** — "We don't need this," "We can do it ourselves," "Status quo works fine"
+- **Stakeholder** — "Need to get buy-in," "My boss won't approve," "Procurement is slow"
+
+State the classification and the most likely underlying concern (cost pressure, risk aversion, relationship with incumbent, etc.).
+
+### Step 2 — Acknowledge & Validate
+Write a 1–2 sentence opener that acknowledges the objection without arguing or immediately pivoting. This builds credibility and trust. Example pattern: "I hear that — [restate their concern]. A lot of [role/company type] we talk to share the same concern at this stage."
+
+### Step 3 — Reframe Script
+Write a reframe that repositions the objection. For each objection type:
+- **Price** → Shift from cost to cost of inaction or ROI; anchor to value delivered
+- **Timing** → Surface the hidden cost of delay; tie to a triggering event or deadline
+- **Competitor** → Acknowledge competitor strengths, then sharpen the differentiated wedge
+- **Need** → Revisit confirmed pain; use their own words from discovery
+- **Stakeholder** → Enable the champion; provide content to sell internally
+
+### Step 4 — Proof Point or Bridge
+Provide one relevant proof point: a customer story, benchmark, statistic, or analogy that reinforces the reframe. Keep it brief (2–3 sentences) and directly tied to their concern.
+
+### Step 5 — Follow-up Question
+Write 2–3 follow-up questions that re-engage the prospect and move the conversation forward. Questions should be open-ended and designed to either confirm the reframe landed or surface the real underlying objection if this one was a smokescreen.
+
+## Example outputs
+A response playbook with five labeled sections per objection: classification and root cause, acknowledge opener, reframe script, proof point, and follow-up questions. Can handle one objection in depth or generate a comparison table for multiple objections at once.

package/skills/proposal-writer/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: proposal-writer
+description: Write a professional sales proposal with executive summary, solution fit, pricing table, ROI estimate, and next steps.
+triggers: ["write proposal", "create proposal", "draft proposal", "sales proposal", "write a proposal"]
+---
+
+# Proposal Writer
+
+## What this skill does
+Given deal context — prospect name, company, pain points, solution fit, and pricing inputs — this skill generates a complete, professional sales proposal document. The output is structured for executive audiences, covers value justification and ROI, and closes with a clear call to action and mutual next steps.
+
+## How to invoke
+/proposal-writer [prospect/company] — [pain points] — [solution] — [pricing tier or budget]
+
+## Workflow steps
+
+### Step 1 — Executive Summary
+Write a 2–3 paragraph executive summary addressed to the economic buyer. Lead with the prospect's business challenge, connect it to strategic impact, and state clearly how the proposed solution resolves it. Avoid feature-speak; focus on business outcomes.
+
+### Step 2 — Current State & Problem Statement
+Describe the prospect's current state, the inefficiencies or risks they face, and the cost of inaction. Use inputs from discovery to make this specific and credible. Frame around the pain hypothesis confirmed during qualification.
+
+### Step 3 — Proposed Solution & Fit
+Map specific capabilities to each identified pain point in a clear solution-fit section. Use a two-column table format: **Their Challenge** | **How We Solve It**. Include any implementation notes, onboarding timeline, or integration considerations relevant to the deal.
+
+### Step 4 — Pricing Table
+Generate a clean pricing table with the proposed package(s). Include line items for licenses/seats, implementation, support tier, and any add-ons discussed. Show one-time vs. recurring costs. If multiple tiers were discussed, present a recommended option and one alternative with a brief rationale for each.
+
+### Step 5 — ROI Estimate
+Build a simple ROI model with clearly stated assumptions. Include: estimated time savings, efficiency gains, revenue impact or cost avoidance, and a payback period. Present as a narrative summary plus a simple table. Flag assumptions explicitly so the prospect can adjust them.
+
+### Step 6 — Next Steps & Call to Action
+Close with a mutual action plan: 3–5 numbered next steps with owners (prospect and vendor), suggested timeline, and a signature/approval block. Make the CTA specific — a date for a follow-up, a pilot kick-off, or a procurement submission deadline.
+
+## Example outputs
+A complete proposal document (6–10 sections) in clean markdown, ready to paste into Google Docs, Notion, or a PDF template. Includes exec summary, problem statement, solution fit table, pricing table, ROI model, and next steps with owners and dates.