# Pg Product

> Generate FinVerge Payment Gateway (PG) product collateral — demo decks, one-pagers, FAQ documents, and feature matrices. Use whenever the user mentions creating, drafting, preparing, generating, or needing ANY kind of PG (Payment Gateway) product material — even when they don't explicitly name the output. Triggers on phrases like "PG demo deck", "Payment Gateway one-pager", "PG FAQ", "PG feature sheet", "make something on PG for a merchant", "PG pitch", "prepare PG collateral", "PG overview for [audience]", and similar. Pulls content from the shared PG knowledge base (features, positioning, compliance). Applies FinVerge branding (navy/orange/blue-sky, FinVerge logo, brand frame). Outputs in PPTX, DOCX, or XLSX depending on the requested deliverable type.

- Skill: `himanisharrma/pg-product` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add himanisharrma/pg-product`
- Raw SKILL.md: https://api.skillmd.com/api/skills/himanisharrma/pg-product/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: himanisharrma (https://skillmd.com/u/himanisharrma)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/himanisharrma/pg-product

---


# PG Product Skill

Generate FinVerge Payment Gateway (PG) product collateral using the shared PG knowledge base and FinVerge brand system.

## When to use

Whenever the user asks for any PG-related sales/marketing/technical artifact:
- "PG demo deck for BeYoung" → demo_deck output
- "One-pager on Payment Gateway" → one_pager output
- "FAQ sheet for the PG team" → faq output
- "Feature matrix of PG for IT team" → feature_matrix output
- "Make me something on PG" → ask which output type, then proceed

Do NOT use this skill for:
- Bank proposals (use `bank-proposal-generator` — it reads from this skill's KB)
- Other products (NACH, Collect, Orchestrate, etc. — each has its own skill)
- Internal-only DELTA4 intelligence (separate skill, later iteration)

## Inputs (asked step-by-step)

1. **Output type** — demo_deck | one_pager | faq | feature_matrix
2. **Target audience** — bank partner | enterprise merchant | mid-tier merchant | technical team | internal | generic
3. **Filename prefix** (optional) — defaults to "PG-{output}-{YYYYMMDD}"

## How it works

The skill dispatches to `scripts/generate.py` which routes to the right output module in `scripts/outputs/`. Each output module:

1. Loads content from the shared PG knowledge base via `kb_loader.load_public("pg", facet)`
2. Applies FinVerge branding (colors, fonts, logo) via `shared/brand.py` + `shared/layout.py`
3. Produces the file to `~/Downloads/pg-output/{prefix}.{ext}`

Customer-facing output modules **never import** `load_internal` — the KB loader enforces this structurally.

## Generating a deliverable

```bash
cd /path/to/skill/scripts
python3 generate.py --output demo_deck --audience bank
# → ~/Downloads/pg-output/PG-demo_deck-<date>.pptx

python3 generate.py --output one_pager
python3 generate.py --output faq
python3 generate.py --output feature_matrix
```

When invoked through Claude:
1. Confirm output type + audience with user
2. Run `generate.py` with the chosen flags
3. Report back with the file path and a summary of gaps (`[TO FILL]` markers in KB that surfaced in the output)

## Output types

| Output | Format | Description |
|--------|--------|-------------|
| demo_deck | PPTX | 8-slide product pitch deck for sales meetings |
| one_pager | DOCX | Single-page leave-behind / email attachment |
| faq | DOCX | Top 10 Q&A + objection handler for sales team |
| feature_matrix | XLSX | Full feature table with status/owner/flags |

## Dependencies

- Shared code: `../../shared/{brand,layout,kb_loader}.py` + `../../shared/slides/*`
- Shared assets: `../../shared-assets/logos/finverge/`
- Shared KB: `../../shared-kb/pg/{external,features,pricing,compliance}.md`

## Gaps

The PG KB may contain `[TO FILL]` markers. The skill surfaces these in a `gaps.md` sibling file alongside each output. Typical gaps for PG at the time of writing:
- Pricing slabs (no dedicated PG pricing doc in info folder yet)
- Verified bank-partner list for citation
- Specific case studies / volume numbers

Fill these in `shared-kb/pg/*.md` and regenerate — no code changes needed.

## For future skills

This skill is the pattern template. When building `nach-product`, `collect-product`, etc., copy this structure:
- `SKILL.md` (this file's pattern)
- `scripts/generate.py` (dispatcher)
- `scripts/outputs/{4 files}.py` (output modules)
- Reference shared code + its own product KB directory