lemonsqueezy-tier-setup

Skill: lemonsqueezy-tier-setup

Important context (Lemon Squeezy API constraint): The Lemon Squeezy REST API does not allow creating products or variants programmatically. They must be created manually in the Lemon Squeezy dashboard. This skill therefore operates in Discover & Configure mode: it reads what exists, validates it against an expected tier structure, and emits the configuration artefacts your app needs.

When to use

• You just finished creating your subscription products (e.g. Starter/Pro/ Enterprise) in the Lemon Squeezy dashboard and want the variant IDs mapped into your environment / pricing config.
• You're auditing an existing store and want to know which variants your app is missing or has wired incorrectly.
• You want to confirm the webhook subscription is correctly registered before running lemonsqueezy-webhook-test.

Inputs

The user provides — directly or via a manifest — the expected tier layout and how they want the output emitted.

Option A: Inline (conversational)

"I have Starter (Monthly + Yearly), Pro (Monthly + Yearly), Enterprise (Monthly

• Yearly) in store 12345. Map them to env vars prefixed LEMONSQUEEZY_VARIANT_."

Option B: YAML manifest

storeId: "12345"
currency: USD
webhookUrl: "https://app.example.com/api/webhooks/lemonsqueezy"
envPrefix: "LEMONSQUEEZY_VARIANT_"     # optional, this is the default
tierNames: [starter, pro, enterprise]  # your own names — no fixed taxonomy
outputFormat: env                      # env | table | both  (default: both)
expectedTiers:
  starter:
    productName: "Starter"
    monthlyVariantSlug: "starter-monthly"
    yearlyVariantSlug: "starter-yearly"
  pro:
    productName: "Pro"
    monthlyVariantSlug: "pro-monthly"
    yearlyVariantSlug: "pro-yearly"
  enterprise:
    productName: "Enterprise"
    monthlyVariantSlug: "enterprise-monthly"
    yearlyVariantSlug: "enterprise-yearly"

Workflow

1. Verify auth — call lemonsqueezy_whoami. Fail loudly if no API key configured.
2. Confirm store — call lemonsqueezy_list_stores, match against the expected storeId. If not allowed by LEMONSQUEEZY_ALLOWED_STORE_IDS, stop and ask the user to update the allowlist.
3. Discover products — call lemonsqueezy_list_products filtered by storeId. Match against expectedTiers[*].productName.
4. Discover variants — for each matched product, call lemonsqueezy_list_variants. Pair them with the expected monthlyVariantSlug / yearlyVariantSlug.
5. Pull prices — call lemonsqueezy_list_prices for each variant to confirm monthly/yearly billing intervals.
6. Webhook check — call lemonsqueezy_list_webhooks. If the configured webhookUrl is missing, offer to call lemonsqueezy_create_webhook with the event set your app needs (subscription_*, subscription_payment_*, order_created, …) and a freshly generated 32-char secret.
7. Emit artefacts (per outputFormat):
   • env: <envPrefix><TIER>_<INTERVAL>=<id> lines you can paste into your .env (e.g. LEMONSQUEEZY_VARIANT_PRO_MONTHLY=300001)
   • table: a summary — tier → variant ID → monthly price → yearly price → status