sales-woodpecker
Woodpecker.co platform help — cold email campaigns, condition-based sequences, email warmup, Bounce Shield, Adaptive Sending, email verification, inbox rotation, centralized inbox, LinkedIn automation, Lead Finder, agency panel, API & webhooks. Use when Woodpecker emails are landing in spam, campaign open rates are dropping, you're not sure how to set up condition-based sequences, warmup isn't improving deliverability, the agency panel isn't isolating client data properly, or Woodpecker sending has stopped unexpectedly. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Woodpecker to other tools via Zapier (use /sales-integration).
What this skill does
# Woodpecker.co Platform Help Help the user with Woodpecker.co platform questions — from cold email campaign setup and condition-based sequences through deliverability tools, warmup, inbox rotation, LinkedIn automation, Lead Finder, agency panel, API, and integrations. ## Step 1 — Gather context If `references/learnings.md` exists, read it first for accumulated knowledge. Ask the user: 1. **What area of Woodpecker do you need help with?** - A) Campaigns — creating condition-based sequences, A/B testing, follow-ups - B) Deliverability — Bounce Shield, Adaptive Sending, ESP Matching, domain audit, spam checker - C) Warmup — built-in email warmup powered by Mailivery - D) Agency panel — multi-client management, per-client isolation - E) Integrations / API — connecting to CRMs, webhooks, API automation - F) Lead Finder — B2B lead database, data credits - G) Inbox — centralized inbox, reply management, auto-categorization - H) LinkedIn automation — automated connection requests, messages, multichannel sequences - I) Something else — describe it 2. **What's your role?** - A) Admin / account owner - B) Sales rep / BDR / AE - C) Agency owner / account manager - D) Other 3. **What are you trying to accomplish?** (describe your specific goal or question) **If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context. Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit. ## Step 2 — Route or answer directly If the request maps to a specialized skill, route: - Outbound cadence strategy / sequence design -> `/sales-cadence` - Cross-platform email deliverability -> `/sales-deliverability` - Email tracking strategy -> `/sales-email-tracking` - Building prospect lists -> `/sales-prospect-list` - Connecting Woodpecker to other tools via Zapier or middleware -> `/sales-integration` - Multi-client agency architecture (platform-agnostic) -> `/sales-agency-outbound` Otherwise, answer directly from platform knowledge using the reference below. ## Step 3 — Woodpecker platform reference **Read `references/platform-guide.md`** for detailed module documentation, pricing, integrations, and data model. *You no longer need the platform guide details — focus on the user's specific situation.* ## Step 4 — Actionable guidance Based on the user's specific question: 1. **Recommended setup order** for new accounts: 1. Connect mailbox(es) (Gmail, Outlook, or SMTP) 2. Enable warmup on all connected mailboxes 3. Wait 2+ weeks for warmup to build reputation 4. Set up domain authentication (SPF, DKIM, DMARC) — use Woodpecker's domain audit to verify 5. Create your first campaign with condition-based steps 6. Add prospects (manually, CSV, Lead Finder, or API) 7. Run spam checker on your email copy 8. Launch campaign 2. **Configuration recommendations**: - Enable Bounce Shield on all campaigns — there is no reason to skip it - Enable Adaptive Sending to let Woodpecker auto-throttle based on engagement - Set daily per-mailbox limits conservatively (30-50 for cold outbound) - Use inbox rotation with 3+ mailboxes to distribute volume - A/B test subject lines first, then body copy — test one variable at a time 3. **For API questions**: Always include a pointer — "For the full endpoint catalog, request/response schemas, and rate limits, see `references/woodpecker-api-reference.md`." ## Gotchas > Best-effort from research — verify details against current Woodpecker documentation. 1. **API access is a paid add-on (EUR 20/mo)** — not included in base plans. Many users expect API access by default, but you need the API & integrations add-on or an active trial to use the API at all. 2. **LinkedIn automation is a separate add-on (EUR 29/LinkedIn account)** — not included in any plan tier. Each LinkedIn account you want to automate costs extra on top of your base plan. 3. **Woodpecker prices by "contacted prospects" not by user/seat** — every new person added to a campaign counts against your monthly limit, even if they don't receive all steps. Recontacting the same prospect in a different campaign counts again. 4. **The agency panel is per active client (EUR 27/client/mo)** — costs scale linearly with client count. Compare with Smartlead's flat agency pricing if managing many clients. 5. **Woodpecker's API has a strict 1-concurrent-request limit with a queue of only 6** — high-volume API integrations need careful throttling and retry logic. Requests beyond 6 queued return HTTP 429 immediately (15-second timeout per queued request). - **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date. ## Step 5 — Related skills - `/sales-cadence` — Design outbound cadence strategy (platform-agnostic, works with Woodpecker campaigns) - `/sales-deliverability` — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement - `/sales-email-tracking` — Email tracking strategy — open/click tracking, engagement signals - `/sales-prospect-list` — Build prospect lists to import into Woodpecker - `/sales-integration` — Connect Woodpecker to other tools via webhooks, Zapier, or API - `/sales-agency-outbound` — Multi-client agency architecture — infrastructure, client isolation, onboarding - `/sales-enrich` — Enrich contacts with emails/phones before importing into Woodpecker - `/sales-smartlead` — Smartlead platform help (if evaluating alternatives to Woodpecker) - `/sales-lemlist` — Lemlist platform help (if evaluating alternatives to Woodpecker) - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install with `/install-skill sales-do` if you don't have it. ## Examples ### Example 1: Basic campaign setup with A/B testing **User says**: "How do I set up a cold email campaign in Woodpecker with A/B testing and follow-ups?" **Skill does**: 1. Walks through creating a new campaign with condition-based steps 2. Explains adding up to 16 steps with delays between them — initial email plus follow-ups 3. Shows how to create A/B test variants (up to 5 per step) for subject lines and body copy 4. Configures auto-stop on reply so prospects exit the sequence when they respond 5. Recommends connecting 3+ mailboxes with inbox rotation for volume distribution **Result**: User has a multi-step campaign with A/B testing, follow-ups, and proper mailbox rotation configured ### Example 2: Deliverability audit **User says**: "My Woodpecker emails are going to spam. How do I fix deliverability?" **Skill does**: 1. Runs through Woodpecker's domain audit — checks SPF, DKIM, DMARC with fix suggestions 2. Verifies warmup status on all connected mailboxes — must be running 2+ weeks with healthy reputation 3. Enables Bounce Shield and Adaptive Sending if not already active 4. Uses spam checker to audit email copy for spammy words, broken links, and authentication issues 5. Recommends deliverability monitor for ongoing inbox placement tracking **Result**: User has a complete deliverability diagnosis with specific fixes and ongoing monitoring ### Example 3: Agency panel configuration **User says**: "I run an agency and need to manage 10 clients in Woodpecker" **Skill does**: 1. Explains the agency panel add-on pricing (EUR 27/active client/mo = EUR 270/mo for 10 clients) 2. Walks through setting up per-client isolation — separate campaigns, prospects, and mailboxes 3. Shows the Agency API authentication pattern: HQ key + `x-company-id` header 4. Configures per-company API keys for any clients needing their own API access 5. Sets up a single-dashboard workflow for monitoring all 10 clients **Result**:
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".