sales-beehiiv

Name: sales-beehiiv
Author: sales-skills

86stars9forks

How to install sales-beehiiv?

sales-skills/sales/sales-beehiiv

$npx -y skills add sales-skills/sales --skill sales-beehiiv

Installs into the current project.

Summary

Beehiiv platform help — newsletter publishing, audience growth, monetization (ad network, paid subscriptions, Boosts), referral programs, email automations, website builder, API. Use when beehiiv emails are going to spam on shared IPs, ad network isn't generating revenue, Boosts

Files · 1

View on GitHub

SKILL.md

1	# Beehiiv Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	Ask the user:
8
9	1. What area of beehiiv do you need help with?
10	- A) Publishing — editor, templates, scheduling, content
11	- B) Audience growth — Boosts, referral program, recommendations, subscribe forms
12	- C) Monetization — Ad Network, paid subscriptions, sponsorship storefront, digital products
13	- D) Automations — email flows, segments, triggers
14	- E) Website — builder, custom domains, SEO, landing pages
15	- F) Analytics — campaign stats, subscriber metrics, A/B testing
16	- G) Integrations — Zapier, Make, webhooks, API
17	- H) Account — pricing, plan features, billing, teams
18	- I) Something else — describe it
19
20	2. What plan are you on?
21	- A) Launch (free — up to 2,500 subscribers)
22	- B) Scale (from $43/mo billed annually, $49/mo monthly — up to 100K subscribers)
23	- C) Max (from $96/mo billed annually, $109/mo monthly — up to 100K subscribers)
24	- D) Enterprise (custom — 100K+ subscribers)
25	- E) Not sure
26
27	3. What are you trying to accomplish? (describe your specific goal or question)
28
29	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
30
31	## Step 2 — Route or answer directly
32
33	If the request maps to a strategy skill, route:
34	- Newsletter monetization strategy → "This is a monetization strategy question — run: `/sales-newsletter {your question}`"
35	- Growing subscriber list strategy → "This is an audience growth question — run: `/sales-audience-growth {your question}`"
36	- Email marketing strategy (sequences, segmentation) → "This is an email marketing question — run: `/sales-email-marketing {your question}`"
37	- Email deliverability / SPF / DKIM → "This is a deliverability question — run: `/sales-deliverability {your question}`"
38	- Selling digital products → "This is a digital products question — run: `/sales-digital-products {your question}`"
39
40	If the request is beehiiv-specific (platform config, feature questions, troubleshooting), continue to Step 3.
41
42	## Step 3 — Beehiiv platform reference
43
44	Read `references/platform-guide.md` for the full platform reference — modules, pricing, integrations, data model, workflows.
45
46	Answer the user's question using only the relevant section. Don't dump the full reference.
47
48	If the question involves the API, also read `references/beehiiv-api-reference.md` for endpoint details.
49
50	## Step 4 — Actionable guidance
51
52	You no longer need the platform guide — focus on the user's specific situation.
53
54	Provide step-by-step guidance tailored to their plan tier:
55	- Check if the feature they need is available on their plan (many features are Scale+ only)
56	- If they're on Launch and need a paid feature, explain the upgrade path
57	- For API questions, provide example requests with their publication context
58	- For growth questions, recommend the beehiiv-native approach first, then third-party alternatives
59
60	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
61
62	## Gotchas
63
64	Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
65
66	1. Shared IP deliverability — all beehiiv users share sending infrastructure. If deliverability drops, it may not be your fault. Custom domains help, but dedicated IPs require Enterprise plan.
67	2. Automations are limited — email automations can only look back 30 days. You can't import complex flows from other platforms that use longer time windows.
68	3. Scale plan required for monetization — Ad Network, Boosts, paid subscriptions, and digital products all require Scale (from $43/mo annual, $49/mo monthly) or higher. The free Launch plan has no monetization features.
69	4. Webhooks require Scale plan — can't receive real-time events on the free plan.
70	5. Send API is Enterprise-only and in beta — programmatic email sending is beta, available on request to Enterprise plans. The regular API (subscriptions, posts list/get, publications, segments, tiers, custom fields, webhooks, etc.) is available on all p

People who liked this also viewed

6 picks

Type

sales-beehiiv

86stars9forks

View on GitHub

How to install sales-beehiiv?

sales-skills/sales/sales-beehiiv

$npx -y skills add sales-skills/sales --skill sales-beehiiv

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Beehiiv Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	Ask the user:
8
9	1. What area of beehiiv do you need help with?
10	- A) Publishing — editor, templates, scheduling, content
11	- B) Audience growth — Boosts, referral program, recommendations, subscribe forms
12	- C) Monetization — Ad Network, paid subscriptions, sponsorship storefront, digital products
13	- D) Automations — email flows, segments, triggers
14	- E) Website — builder, custom domains, SEO, landing pages
15	- F) Analytics — campaign stats, subscriber metrics, A/B testing
16	- G) Integrations — Zapier, Make, webhooks, API
17	- H) Account — pricing, plan features, billing, teams
18	- I) Something else — describe it
19
20	2. What plan are you on?
21	- A) Launch (free — up to 2,500 subscribers)
22	- B) Scale (from $43/mo billed annually, $49/mo monthly — up to 100K subscribers)
23	- C) Max (from $96/mo billed annually, $109/mo monthly — up to 100K subscribers)
24	- D) Enterprise (custom — 100K+ subscribers)
25	- E) Not sure
26
27	3. What are you trying to accomplish? (describe your specific goal or question)
28
29	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
30
31	## Step 2 — Route or answer directly
32
33	If the request maps to a strategy skill, route:
34	- Newsletter monetization strategy → "This is a monetization strategy question — run: `/sales-newsletter {your question}`"
35	- Growing subscriber list strategy → "This is an audience growth question — run: `/sales-audience-growth {your question}`"
36	- Email marketing strategy (sequences, segmentation) → "This is an email marketing question — run: `/sales-email-marketing {your question}`"
37	- Email deliverability / SPF / DKIM → "This is a deliverability question — run: `/sales-deliverability {your question}`"
38	- Selling digital products → "This is a digital products question — run: `/sales-digital-products {your question}`"
39
40	If the request is beehiiv-specific (platform config, feature questions, troubleshooting), continue to Step 3.
41
42	## Step 3 — Beehiiv platform reference
43
44	Read `references/platform-guide.md` for the full platform reference — modules, pricing, integrations, data model, workflows.
45
46	Answer the user's question using only the relevant section. Don't dump the full reference.
47
48	If the question involves the API, also read `references/beehiiv-api-reference.md` for endpoint details.
49
50	## Step 4 — Actionable guidance
51
52	You no longer need the platform guide — focus on the user's specific situation.
53
54	Provide step-by-step guidance tailored to their plan tier:
55	- Check if the feature they need is available on their plan (many features are Scale+ only)
56	- If they're on Launch and need a paid feature, explain the upgrade path
57	- For API questions, provide example requests with their publication context
58	- For growth questions, recommend the beehiiv-native approach first, then third-party alternatives
59
60	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
61
62	## Gotchas
63
64	Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
65
66	1. Shared IP deliverability — all beehiiv users share sending infrastructure. If deliverability drops, it may not be your fault. Custom domains help, but dedicated IPs require Enterprise plan.
67	2. Automations are limited — email automations can only look back 30 days. You can't import complex flows from other platforms that use longer time windows.
68	3. Scale plan required for monetization — Ad Network, Boosts, paid subscriptions, and digital products all require Scale (from $43/mo annual, $49/mo monthly) or higher. The free Launch plan has no monetization features.
69	4. Webhooks require Scale plan — can't receive real-time events on the free plan.
70	5. Send API is Enterprise-only and in beta — programmatic email sending is beta, available on request to Enterprise plans. The regular API (subscriptions, posts list/get, publications, segments, tiers, custom fields, webhooks, etc.) is available on all p

People who liked this also viewed

6 picks

Type