sales-adbutler

Name: sales-adbutler
Author: sales-skills

86stars9forks

How to install sales-adbutler?

sales-skills/sales/sales-adbutler

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

Installs into the current project.

Summary

AdButler platform help — full-stack ad server for display, video, mobile, native, and email ads with self-serve advertiser portal, programmatic SSP, REST API, MCP server, and cookieless targeting. Use when setting up AdButler to monetize your newsletter or website with ads, email

Files · 1

View on GitHub

SKILL.md

1	# AdButler Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	1. What are you trying to do?
8	- A) Set up AdButler to serve ads on my website or newsletter
9	- B) Configure the self-serve portal for advertisers
10	- C) Integrate via the REST API or MCP server
11	- D) Troubleshoot ad rendering or delivery issues
12	- E) Compare AdButler to other ad servers
13	- F) Set up programmatic demand (SSP/RTB)
14
15	2. Which side are you on?
16	- A) Publisher (I have a site/newsletter and want ad revenue)
17	- B) Advertiser (I want to place ads)
18	- C) Developer (building a custom ad platform or integration)
19
20	3. Current setup (if applicable): channel (web, email, app), monthly ad requests, current ad server
21
22	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
23
24	## Step 2 — Route or answer directly
25
26	\| If the question is about... \| Route to... \|
27	\|---\|---\|
28	\| Newsletter monetization strategy (subscriptions, pricing models) \| `/sales-newsletter [question]` \|
29	\| Sponsorship marketplace (finding sponsors) \| `/sales-paved [question]` or `/sales-hecto [question]` \|
30	\| Sponsor intelligence (brands that sponsor newsletters) \| `/sales-sponsorgap [question]` \|
31	\| Building a custom ad platform from scratch (API-first) \| `/sales-kevel [question]` \|
32	\| Email deliverability (SPF/DKIM/DMARC) \| `/sales-deliverability [question]` \|
33
34	If the question is AdButler-specific, continue to Step 3.
35
36	## Step 3 — AdButler platform reference
37
38	Read `references/platform-guide.md` for the full platform reference — capabilities, pricing, data model, email ad setup, integration recipes, code examples.
39
40	Read `references/adbutler-api-reference.md` for API endpoint details, authentication, ad serving JSON API, and MCP server setup.
41
42	Answer the user's question using only the relevant section. Don't dump the full reference.
43
44	## Step 4 — Actionable guidance
45
46	Focus on the user's specific situation:
47
48	- Publisher getting started: Create a publisher, add zones (email or web), generate zone tags, paste into your template. Start with 1-2 zones, monitor for 2-4 weeks.
49	- Email newsletters: Use email-type zones — image-only ads. Generate zone tag with your ESP's EUID macro. Paste HTML into template. Ads can be updated after send.
50	- Self-serve portal: Enable the self-serve module, configure advertiser registration, set approval workflows and payment processing. Advertisers manage their own campaigns.
51	- API integration: API Access is a paid add-on. Use Bearer token auth against `api.adbutler.com/v2/`. For ad serving, use the JSON API at `servedbyadbutler.com/adserve` (no auth needed).
52	- MCP server: Install with `claude mcp add adbutler -- npx -y @adbutler/mcp-server`. Manage campaigns, pull reports, and automate ad ops through natural language.
53	- Choosing AdButler vs alternatives: AdButler is best for publishers wanting a managed ad server with self-serve portal and email support at $179/mo+. For API-first custom builds, use Kevel. For free/open-source, consider Revive Adserver. For programmatic-only newsletter ads with no setup, use Admailr or Paved.
54
55	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
56
57	## Gotchas
58
59	> Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
60
61	1. API Access is a paid add-on on all plans — you must add it to your subscription before API keys work. Budget for this if building integrations.
62	2. Email zones are image-only — almost all email clients block Rich Media/Custom HTML ads. Only image creatives work in email zones.
63	3. Essentials plan caps at 10 zones and 10 advertisers — if you need more, you must upgrade to Standard ($682/mo). Check zone/advertiser limits

People who liked this also viewed

6 picks

Type

sales-adbutler

86stars9forks

View on GitHub

How to install sales-adbutler?

sales-skills/sales/sales-adbutler

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# AdButler Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	1. What are you trying to do?
8	- A) Set up AdButler to serve ads on my website or newsletter
9	- B) Configure the self-serve portal for advertisers
10	- C) Integrate via the REST API or MCP server
11	- D) Troubleshoot ad rendering or delivery issues
12	- E) Compare AdButler to other ad servers
13	- F) Set up programmatic demand (SSP/RTB)
14
15	2. Which side are you on?
16	- A) Publisher (I have a site/newsletter and want ad revenue)
17	- B) Advertiser (I want to place ads)
18	- C) Developer (building a custom ad platform or integration)
19
20	3. Current setup (if applicable): channel (web, email, app), monthly ad requests, current ad server
21
22	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
23
24	## Step 2 — Route or answer directly
25
26	\| If the question is about... \| Route to... \|
27	\|---\|---\|
28	\| Newsletter monetization strategy (subscriptions, pricing models) \| `/sales-newsletter [question]` \|
29	\| Sponsorship marketplace (finding sponsors) \| `/sales-paved [question]` or `/sales-hecto [question]` \|
30	\| Sponsor intelligence (brands that sponsor newsletters) \| `/sales-sponsorgap [question]` \|
31	\| Building a custom ad platform from scratch (API-first) \| `/sales-kevel [question]` \|
32	\| Email deliverability (SPF/DKIM/DMARC) \| `/sales-deliverability [question]` \|
33
34	If the question is AdButler-specific, continue to Step 3.
35
36	## Step 3 — AdButler platform reference
37
38	Read `references/platform-guide.md` for the full platform reference — capabilities, pricing, data model, email ad setup, integration recipes, code examples.
39
40	Read `references/adbutler-api-reference.md` for API endpoint details, authentication, ad serving JSON API, and MCP server setup.
41
42	Answer the user's question using only the relevant section. Don't dump the full reference.
43
44	## Step 4 — Actionable guidance
45
46	Focus on the user's specific situation:
47
48	- Publisher getting started: Create a publisher, add zones (email or web), generate zone tags, paste into your template. Start with 1-2 zones, monitor for 2-4 weeks.
49	- Email newsletters: Use email-type zones — image-only ads. Generate zone tag with your ESP's EUID macro. Paste HTML into template. Ads can be updated after send.
50	- Self-serve portal: Enable the self-serve module, configure advertiser registration, set approval workflows and payment processing. Advertisers manage their own campaigns.
51	- API integration: API Access is a paid add-on. Use Bearer token auth against `api.adbutler.com/v2/`. For ad serving, use the JSON API at `servedbyadbutler.com/adserve` (no auth needed).
52	- MCP server: Install with `claude mcp add adbutler -- npx -y @adbutler/mcp-server`. Manage campaigns, pull reports, and automate ad ops through natural language.
53	- Choosing AdButler vs alternatives: AdButler is best for publishers wanting a managed ad server with self-serve portal and email support at $179/mo+. For API-first custom builds, use Kevel. For free/open-source, consider Revive Adserver. For programmatic-only newsletter ads with no setup, use Admailr or Paved.
54
55	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
56
57	## Gotchas
58
59	> Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
60
61	1. API Access is a paid add-on on all plans — you must add it to your subscription before API keys work. Budget for this if building integrations.
62	2. Email zones are image-only — almost all email clients block Rich Media/Custom HTML ads. Only image creatives work in email zones.
63	3. Essentials plan caps at 10 zones and 10 advertisers — if you need more, you must upgrade to Standard ($682/mo). Check zone/advertiser limits

People who liked this also viewed

6 picks

Type