Skip to content
Back to skills

Pitchdeck

ASecurity

Generate professional B2B service pitch deck tailored to prospects or industries

  • 25 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added June 2, 2026
businessgo

Works with

  • cli

Security analysis

A100/100

Scanned June 2, 2026

npx -y skills add reggiechan74/JobOps --skill pitchdeck --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pitchdeck?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pitchdeck
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/reggiechan74-pitchdeck/badge)](https://www.skillsdirectory.com/skills/reggiechan74-pitchdeck)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pitchdeck
description: Generate professional B2B service pitch deck tailored to prospects or industries
disable-model-invocation: true
---

## Configuration

Read `.jobops/config.json`. If missing, stop with:

> JOBOPS NOT CONFIGURED
> Run /jobops:setup (then /jobops-ic:setup) to initialize your workspace.

Use `config.directories.contractor_root` for output paths in this skill.
Use `config.preferences.default_currency` for pricing if applicable.

## Arguments

Generate 10-12 slide B2B pitch deck with provenance-hardened claims. Supports prospect-specific, industry-generic, service-focused, or general capabilities presentations.

**Modes:** `--prospect=name` | `--industry=X` | `--service=name` | default (general)
**Format:** `--format=md|pptx` (markdown default, pptx requires pandoc)
**Output:** `{config.directories.contractor_root}/pitches/[ClientCompany]_[YYYYMMDD].md`

---

## Phase 1: Validate Prerequisites and Load Data

### 1.1 Prerequisites Check

**Required files (stop if missing):**

1. **Service Definition**: `{config.directories.contractor_root}/services/service_definition_*.md`
   - If missing: Show error, instruct to run `/defineservices`, stop execution

2. **Career Source Files**: `{config.directories.resume_source}/CareerHighlights/`, `{config.directories.resume_source}/Technology/`, `{config.directories.resume_source}/Projects/`, `{config.directories.resume_source}/WorkHistory/` directories
   - If missing: Show error, instruct user to populate their resume source folder, stop execution

### 1.2 Load Service Definition

Use most recent `{config.directories.contractor_root}/services/service_definition_*.md` if multiple exist. Extract:
- YAML: consultant, generated_on, version, source_files_read
- Consultant: name, tagline, credentials, years_experience
- Services: name, category, description, deliverables, ideal_client (industries, pain_points, decision_makers), pricing (model, range, value_justification), success_metrics, case_studies
- Rate Card: hourly/daily/retainer rates, payment_terms
- Differentiation: unique_value, competitive_advantages, proof_points, certifications, publications, speaking
- Target Market: primary_markets, secondary_markets, geographic_focus

### 1.3 Source Reading for Pitch Deck

Read these source files directly:
- `CareerHighlights/CareerHighlights_Summary.md` and `CareerHighlights/*.md` — quantified achievements with metrics, timeframe, mechanism
- `Technology/TechStack.md` — skills (judge "Expert" level in-context from depth of WorkHistory mentions, not from a precomputed enum)
- `Technology/Certifications.md` — Active certs only (Expired/In-Progress excluded)
- `Projects/*.md` — case studies
- `Thought_Leadership/*.md` if present — publications, frameworks, awards
- `WorkHistory/*.md` — relevant roles for industry/scope context

Do NOT load `candidate_profile.json` — removed in v2.2.0.

### 1.4 Provenance Discipline

The pitch deck's 90%+ provenance validation rate is now enforced by direct source citation: every quantified claim on a slide must cite `{filepath}:{line_number}` and that line must contain the verbatim metric. No claim survives without a direct source pointer. Validate by re-reading the cited line before finalizing each slide. Validation bands: ≥90% PASS, 80-89% MEDIUM (review recommended, not a fail), <80% FAIL.

Failure path unchanged: validation rate <80% requires major revision.

### 1.5 Parse Arguments

**Targeting modes (mutually exclusive):**
- `--prospect=name`: Load most recent matching file from `{config.directories.contractor_root}/prospects/`. If not found, show error with available prospects, stop.
- `--industry=X`: Validate against service definition industries. Warn if not listed, but proceed.
- `--service=name`: Fuzzy match against service definition. If no match, show error with available services, stop.
- Default: General capabilities (all services, industry-agnostic)

**Format:**
- `--format=pptx`: Check pandoc installed. If not, warn and use markdown only. If installed, convert after generation.
- Default: markdown

---

## Phase 2: Conduct Target Research (5-10 minutes)

### 2.1 Prospect Mode (5-7 min)
Load prospect data from file. Conduct fresh research:
1. **News & Initiatives (2-3 min)**: Recent press releases, strategic priorities, funding, leadership changes, technology adoption
2. **Pain Points (2 min)**: Glassdoor reviews, job postings (skill gaps), RFPs, industry reports
3. **Decision-Makers (1-2 min)**: LinkedIn verification, role changes, recent activity

### 2.2 Industry Mode (5-8 min)
1. **Trends & Challenges (3-4 min)**: Top trends, pain points, technology adoption, regulatory issues, market indicators
2. **Consulting Market (2-3 min)**: Market size, demand signals, engagement models, competitive landscape
3. **Decision-Makers (1-2 min)**: Common titles, priorities, KPIs, budget authority, procurement

### 2.3 Service Mode (4-6 min)
1. **Market Landscape (2-3 min)**: Market demand, ROI data, success stories, pricing benchmarks
2. **Pain Points (2-3 min)**: Cost of inaction, prevalence, solutions, ROI expectations

### 2.4 Quality Check
Validate: >=5 credible sources, <=6 months old, quantified data, current decision-makers, supported pain points. If LOW quality, warn but proceed.

---

## Phase 3: Generate Pitch Deck (10-12 Slides)

### 3.1 Slide Structure
| # | Title | Content | Source |
|---|-------|---------|--------|
| 1 | Title | Identity, tagline, contact | Service definition |
| 2 | Problem | Pain points | Research + service definition |
| 3 | Cost of Inaction | Quantified impact | Research + industry data |
| 4 | Solution | Service overview | Service definition |
| 5 | How It Works | Methodology | Service definition + source files |
| 6 | Results & Proof | Case studies, metrics | Source files + service def |
| 7 | Why Me/Us | Credentials, differentiation | Both sources |
| 8 | Engagement Options | Pricing, packages | Rate card |
| 9 | Relevant Experience | Industry examples | Source files (filtered) |
| 10 | Next Steps | CTA, timeline | Mode-specific |
| 11 | Q&A | Objections | Generated |
| 12 | Appendix | Credentials | Source files |

Adjust: Service mode 8-10 slides, Prospect 12, Industry 10-11.

### 3.2-3.13 Slide Generation Instructions

**General Rules (all slides):**
- Include evidence citations for all quantified claims
- Customize "Presented to" field based on mode
- Use ONLY data from service definition and career source files
- Maximum 3-4 main points per slide (focus over volume)

**Slide 2 (Problem):** Mode-specific pain points with evidence. Prospect: company-specific from research. Industry: common challenges with statistics. Service: pain point service addresses with prevalence. Max 3 pain points, cite sources.

**Slide 3 (Cost of Inaction):** Impact table with quantified costs (4 areas), opportunity costs, compounding effects, urgency rationale. Prioritize prospect data, use industry benchmarks if unavailable. Cite sources.

**Slide 4 (Solution):** Service overview. Multi-service: 2-3 services with top deliverables. Single-service: full deliverables + success metrics. Prospect: challenge-solution-outcome table. Use exact deliverables from service definition.

**Slide 5 (How It Works):** 3-5 methodology phases with duration, activities, deliverables, client involvement. Extract methodology from `WorkHistory/*.md` source files. Timeline must align with service definition typical_duration.

**Slide 6 (Results & Proof):** CRITICAL PROVENANCE SLIDE. 3-5 top achievements with Result/Context/Relevance format. Include case study if available. Add credentials. ALL claims must have direct source citations (`{filepath}:{line_number}`). Rank by relevance (industry match 10pts, service match 10pts, recency 5pts, scale 5pts). Validate: quantified metric, `{filepath}:{line_number}` citation exists, timeframe present, mechanism described.

**Slide 7 (Why Me/Us):** Unique value proposition (2-3 sentences). 3-4 competitive advantages with What/Why It Matters/Proof format. Comparison table (Typical vs. Us). Use competitive_advantages directly from service definition.

**Slide 8 (Engagement Options):** Service packages with pricing model, investment range (standard/entry/premium), duration, included deliverables. Engagement models table (project/retainer/hourly/value-based). Payment terms. Use ONLY pricing from service definition.

**Slide 9 (Relevant Experience):** Filter `WorkHistory/*.md` by mode. Prospect: industry-matching roles (2-3). Industry: industry-specific roles (2-4). Service: cross-industry capability demonstration (3-5). Include technical depth (Expert-level skills from `Technology/TechStack.md`). All must have direct source citations (`{filepath}:{line_number}`).

**Slide 10 (Next Steps):** Prospect: Timeline with discovery/proposal/launch phases, required stakeholders, 3 engagement options including entry point from prospect file. Generic: typical timeline, engagement options (call/proposal/download), contact info, testimonials if available.

**Slide 11 (Q&A):** 4-6 common objections based on mode. Prospect: company-type objections. Industry: industry-specific concerns. Service: technical feasibility, ROI validation. Include answers with evidence references.

**Slide 12 (Appendix):** Certifications table (Active only from `Technology/Certifications.md`), education, thought leadership (publications/speaking/frameworks from `Thought_Leadership/*.md`), professional associations, technical proficiencies (Expert + top 5-7 Proficient from `Technology/TechStack.md`), awards, reference policy.

---

## Phase 4: Provenance Hardening (CRITICAL QUALITY GATE)

### 4.1-4.3 Claims Validation Process

**Extract claims:** Scan slides for quantified metrics, credentials, superlatives, client references, technologies, timeframes, ROI claims. Create inventory with slide #, type, source.

**Validate each claim:**
1. **Locate evidence:** Match METRIC/ACHIEVEMENT to `CareerHighlights/*.md` or `WorkHistory/*.md` or `Projects/*.md`. CREDENTIAL to `Technology/Certifications.md` (Active only). TECHNICAL SKILL to `Technology/TechStack.md` (Expert/Proficient in-context). THOUGHT LEADERSHIP to `Thought_Leadership/*.md`.
2. **Verify quality:** Source `{filepath}:{line_number}` citation present, file verifiable (re-read cited line), metric has timeframe + mechanism.
3. **Classify:** VALIDATED (HIGH: complete source citation, quantified, timeframe, mechanism). WEAK (MEDIUM: source incomplete, no timeframe, unclear mechanism). FAIL (none found, contradicts, superlative without benchmark, expired cert).

**Handle failures:** Try alternative evidence, soften claim, or remove. Priority: remove superlatives first, unbounded metrics second, keep partial evidence if critical (mark "Estimated").

### 4.4-4.5 Provenance Trail & Quality Gate

**Generate PROVENANCE TRAIL section** at end of markdown with: Generated timestamp, source files, research date, Claims Validation Summary (total/validated/weak/removed counts, validation rate %), Evidence Mapping table (slide, claim, evidence source, confidence, notes), Research Sources (URLs), Validation Notes (HIGH/MEDIUM/removed explanations), Pre-Use Checklist (6 items).

**Quality gate:** >=90% = HIGH confidence (ready). 80-89% = MEDIUM (review recommended). <80% = LOW (major revision required, show issues/recommendations).

---

## Phase 5: Generate Output Files

**Filename:** `{config.directories.contractor_root}/pitches/[Target]_[YYYYMMDD].md` where Target = company name (prospect mode -> fills `{ClientCompany}`), industry name (industry mode), service name (service mode), or "GeneralCapabilities" (default). Sanitize: remove spaces/special chars, PascalCase, max 50 chars.

**File structure:** YAML frontmatter (pitch_type, target, generated, consultant, service_definition, source_files_read, research_conducted, provenance_validated, validation_rate, confidence_level, version). 12 slides with `---` separators. PROVENANCE TRAIL section. Usage notes.

**Save:** `{config.directories.contractor_root}/pitches/[ClientCompany]_[YYYYMMDD].md` (UTF-8, Unix LF). For industry-mode or service-mode pitches (no specific company), substitute Industry or Service name (sanitized PascalCase) for ClientCompany.

**PPTX conversion (if `--format=pptx`):** Run `pandoc ... -t pptx --slide-level=1`. Evidence citations -> slide notes, Provenance Trail -> hide in presentation.

---

## Phase 6: Summary Report

Show: Output files (markdown + pptx if applicable), Pitch details (target, type, slides, research time/sources), Content summary (services, proof points, advantages, pricing models), Provenance validation (rate %, confidence, status + warnings if MEDIUM/LOW), Research highlights (3 key findings), Next steps (6 items), Customization recommendations (4 items), Before presenting checklist (6 items).

---

## Error Handling

**Critical errors (stop execution):**
1. No service definition -> instruct `/defineservices`
2. Missing career source files -> instruct user to populate resume source folder
3. Prospect not found -> list available, suggest alternatives
4. Service not found -> list available services

**Warnings (continue with warnings):**
5. Validation rate <80% -> show issues, recommendations, save anyway
6. Research timeout/failure -> show impact, manual research needed
7. Pandoc not found (pptx requested) -> proceed markdown-only

---

## Usage Examples

**Prospect pitch:** `/pitchdeck --prospect="Hatch"` -> Research company, tailor to pain points, include decision-makers
**Industry pitch:** `/pitchdeck --industry="Commercial Real Estate"` -> Industry trends, common challenges, generic
**Service pitch:** `/pitchdeck --service="AI Agent Development"` -> Deep-dive methodology, cross-industry examples
**General:** `/pitchdeck` -> All services, top achievements, flexible
**PowerPoint:** Add `--format=pptx` to any command for PPTX conversion

---

## Important Notes

**Provenance:** 90%+ = HIGH (ready), 80-89% = MEDIUM (review), <80% = LOW (major review). All claims need direct source citations (`{filepath}:{line_number}`): metrics -> `CareerHighlights/*.md`, credentials -> `Technology/Certifications.md` (Active only), skills -> `Technology/TechStack.md` (Expert/Proficient), case studies -> `Projects/*.md` or service def, advantages -> differentiation section.

**Research ethics:** Public info only (news, LinkedIn, Glassdoor, websites). No private data. 5-10 min time limit. Cite all sources.

**Before presenting:** Add logo, customize colors, add images, update Slide 10 dates/contacts, refresh if >30 days old, remove Provenance Trail for external use.

**Lifecycle:** Quarterly refresh (every 3 months: research, proof points, pricing, certifications). Each generation creates new dated file.

**Workflow:** 1) `/defineservices` 2) `/findclient` 3) `/pitchdeck --prospect=[name]` 4) `/assessjob` for follow-up. Supporting: `/ratecard`, `/idealjob`.

---

Now executing pitch deck generation...

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.