campaign-setup
Prepares an email campaign by adding recipients from your leads. Use when the user wants to set up a campaign, add recipients to a campaign, or prepare for outreach.
What this skill does
# Campaign Setup
Add recipients to a Hunter campaign and prepare it for sending.
## Examples
- `/hunter:campaign-setup Add my fintech leads to the Q2 Outreach campaign`
- `"Set up my campaign with these contacts"`
- `"Add the leads from my SaaS list to campaign 12345"`
- `"Prepare the outreach campaign"`
## Workflow
### Step 1: Identify the Campaign
- If the user provides a campaign ID or name, use it directly.
- Otherwise, call `List-Campaigns` to show available campaigns and ask the user to choose.
```
# Your Campaigns
| ID | Name | Status | Recipients |
|----|------|--------|------------|
| 123 | Q2 Outreach | draft | 0 |
| 456 | Product Launch | running | 150 |
Which campaign would you like to add recipients to?
```
### Step 2: Identify Recipients
Determine the source of recipients:
- **From a leads list** — call `List-Leads` with `leads_list_id` to get the emails.
- **From specific emails** — the user provides email addresses directly.
- **From lead IDs** — the user provides lead IDs.
- **From a previous search** — use contacts already found.
### Step 3: Add Recipients
Call `Add-Campaign-Recipients` with the campaign ID and email addresses or lead IDs. Max 50 per request — batch larger lists automatically.
Report progress: "Adding batch 1 of 3 (50 recipients)..."
### Step 4: Present Summary
```
# Campaign Ready: [Campaign Name]
**Recipients added:** [count]
View campaign: https://hunter.io/campaigns/{campaign_id}
## Important
Before starting the campaign, verify in Hunter that:
- Email subject and body are configured
- A sending email account is connected
- Follow-up steps are set up (if desired)
Campaign creation and editing must be done in the Hunter UI:
https://hunter.io/campaigns/{campaign_id}
## Next Steps
1. Review and edit the campaign in Hunter
2. Start the campaign (Start-Campaign) — once subject, body, and sender are configured
3. Check campaign status (List-Campaigns)
4. Add more recipients
```
## Credit Cost
Free — adding recipients to a campaign does not consume credits.
## Important Notes
- Max 50 recipients per `Add-Campaign-Recipients` call — batch larger lists
- Campaign creation, subject/body editing, and follow-up configuration are done in the Hunter UI (not available via API)
- `Start-Campaign` will fail if the campaign lacks a subject, body, or connected email account
- Use `List-Campaign-Recipients` to check who is already in the campaign
- Use `Remove-Campaign-Recipients` to remove contacts if needed
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".