sales-ghost

name	sales-ghost
description	Ghost platform help — publishing, newsletters, memberships, Stripe subscriptions, themes, Mailgun email delivery, Content API, Admin API, and migration. Use when Ghost newsletters aren't being delivered, Stripe payments aren't syncing with member status, Mailgun setup is failing, theme customization isn't working, migrating from Substack or WordPress, newsletter analytics look wrong, membership tiers aren't gating content correctly, or Ghost API calls are returning errors. Do NOT use for email marketing strategy (use /sales-email-marketing), newsletter monetization strategy (use /sales-newsletter), or growing your subscriber list (use /sales-audience-growth).
argument-hint	[describe what you need help with in Ghost]
license	MIT
version	1.0.0
tags	["sales","publishing","newsletter","membership","platform"]
github	https://github.com/TryGhost

Ghost Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

1. What do you need help with?

   • A) Newsletter setup — Mailgun config, sending, delivery issues
   • B) Membership & subscriptions — Stripe integration, tiers, paid content gating
   • C) Content publishing — editor, scheduling, email-only posts, cards
   • D) Theme customization — Handlebars templates, custom settings, marketplace themes
   • E) Migration — from Substack, WordPress, Medium, Mailchimp, or other platforms
   • F) API integration — Content API, Admin API, webhooks, custom integrations
   • G) Analytics — newsletter open/click rates, member growth, engagement
   • H) Self-hosting — installation, updates, configuration, performance
   • I) Ghost(Pro) — plan selection, billing, limits, custom SSL
   • J) Something else

2. How are you running Ghost?

   • A) Ghost(Pro) managed hosting
   • B) Self-hosted (Docker, DigitalOcean, AWS, etc.)
   • C) Third-party managed host (MagicPages, Pikapods, etc.)
   • D) Haven't set up yet — planning

3. What's your goal? (describe your specific question or issue)

If the user's request already provides most of this context, skip directly to the relevant step.

Step 2 — Route or answer directly

If the request maps to a strategy skill, route with the exact command:

Problem domain	Route to
Email marketing strategy (sequences, segmentation, automation)	"This is an email marketing question — run: /sales-email-marketing {user's question}"
Newsletter monetization (paid tiers, finding sponsors)	"This is a monetization question — run: /sales-newsletter {user's question}"
Growing subscriber/member list	"This is a growth question — run: /sales-audience-growth {user's question}"
Membership site structure, course content, retention	"This is a membership question — run: /sales-membership {user's question}"
Email deliverability (SPF, DKIM, DMARC beyond Mailgun)	"This is a deliverability question — run: "