sales-snov
Snov.io platform help — email finder, email verifier, multichannel campaigns (email + LinkedIn), LinkedIn automation, sales CRM, email warmup, deliverability check, email tracker, AI email writer, prospect management. Use when Snov.io email finder returns no results, campaign reply rates are low, email warmup scores aren't improving, LinkedIn automation isn't sending connection requests, email verification is flagging too many addresses, or the Snov.io API isn't working as expected. Do NOT use for general deliverability strategy (use /sales-deliverability), enrichment strategy (use /sales-enrich), cadence strategy (use /sales-cadence), or prospect list building strategy (use /sales-prospect-list).
What this skill does
# Snov.io Platform Help Help the user with Snov.io platform questions — from email finder and verification through multichannel campaigns, LinkedIn automation, sales CRM, email warmup, deliverability checks, email tracker, AI email writer, prospect management, 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 Snov.io do you need help with?** - A) Email Finder — domain search, name+domain search, LinkedIn enrichment, company domain lookup - B) Email Verifier — single/bulk verification, SMTP checks, 7-tier validation - C) Campaigns — multichannel drip campaigns (email + LinkedIn), A/B testing, AI email writer - D) LinkedIn Automation — profile views, connection requests, follow-ups - E) Sales CRM — deal tracking, pipelines, Google Calendar sync - F) Email Warmup — inbox warming, deliverability improvement - G) Deliverability Check — inbox placement, reputation monitoring - H) Email Tracker — Gmail extension for opens/clicks - I) API — REST API, OAuth, webhooks, automation - J) Integrations — CRM connections, Zapier, Make - K) Something else — describe it 2. **What's your role?** - A) Sales rep / BDR / AE - B) Sales manager / team lead - C) RevOps / Sales Ops - D) Admin / IT - E) Founder / solo seller - F) Agency owner / operator - G) 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: - Cross-platform deliverability strategy -> `/sales-deliverability` - Contact enrichment strategy (platform-agnostic) -> `/sales-enrich` - Outbound cadence strategy / sequence design -> `/sales-cadence` - Building prospect lists -> `/sales-prospect-list` - Email tracking strategy -> `/sales-email-tracking` - Connecting Snov.io to other tools via Zapier or middleware -> `/sales-integration` Otherwise, answer directly from platform knowledge using the reference below. ## Step 3 — Snov.io 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 ## Gotchas > Best-effort from research — verify details against current Snov.io documentation. 1. **LinkedIn automation is a separate paid add-on ($69/mo per slot)** — not included in any base plan. If you build campaigns with LinkedIn steps but haven't purchased the add-on, those steps won't execute. Budget accordingly. 2. **OAuth access token expires in 1 hour** — your integration must handle token refresh. Exchange `client_id` + `client_secret` for a new `access_token` before the old one expires. Failing to refresh causes silent API failures. 3. **V1 vs V2 API endpoints** — Snov.io has both V1 and V2 API endpoints. Some features are only available on V2. Check which version supports the endpoint you need before building integrations. 4. **Credit costs vary by action** — email finds, verifications, and LinkedIn enrichments each consume different credit amounts. A domain search with many results can burn through credits quickly. Always check your balance via the Account endpoint and use email count checks before bulk domain searches. 5. **Warmup slots are limited on lower plans** — Starter plan includes only 3 warmup slots. If you have more than 3 sending mailboxes on Starter, upgrade to Pro S or higher for unlimited warmup. Running campaigns from un-warmed mailboxes damages sender reputation. - **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date. ## Step 5 — Related skills - `/sales-deliverability` — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement - `/sales-enrich` — Enrich contacts with emails/phones before importing into Snov.io - `/sales-cadence` — Design outbound cadence strategy (platform-agnostic, works with Snov.io campaigns) - `/sales-prospect-list` — Build prospect lists to import into Snov.io - `/sales-email-tracking` — Email tracking strategy and best practices - `/sales-integration` — Connect Snov.io to other tools via webhooks, Zapier, Make, or API - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do` ## Examples ### Example 1: Finding and verifying emails for a target company **User says**: "I need to find email addresses for decision-makers at Acme Corp using Snov.io and verify them before outreach." **Skill does**: 1. Runs an email count check on acmecorp.com to estimate available contacts and credit cost 2. Performs a domain search to retrieve all known prospects at the domain 3. Uses name + domain search for any specific contacts not found in the domain search 4. Runs bulk verification on all found emails — filters to "valid" status only 5. Explains credit consumption for each step and recommends checking balance **Result**: User has a verified list of decision-maker emails at Acme Corp, ready for campaign import ### Example 2: Setting up a multichannel drip campaign with LinkedIn **User says**: "How do I create a campaign in Snov.io that combines email follow-ups with LinkedIn connection requests?" **Skill does**: 1. Confirms the user has the LinkedIn Automation add-on ($69/mo) — required for LinkedIn steps 2. Walks through creating a new drip campaign with an initial email step 3. Adds a LinkedIn connection request step triggered by non-engagement (e.g., no open after 3 days) 4. Configures follow-up email steps with A/B testing on subject lines 5. Sets up sentiment analysis on replies and auto-stop on positive responses **Result**: User has a multichannel campaign with email and LinkedIn steps, conditional logic, A/B testing, and automated reply handling ### Example 3: Integrating Snov.io with HubSpot via API **User says**: "I want to automatically push verified leads from Snov.io into HubSpot using the API." **Skill does**: 1. Explains Snov.io's OAuth 2.0 authentication — exchange client_id + client_secret for a 1-hour access token 2. Shows how to use the Email Finder and Verifier endpoints to find and validate contacts 3. Walks through using webhook callbacks on async finder endpoints to receive results 4. Recommends using the native HubSpot integration for direct sync, or Zapier/Make for custom workflows 5. Warns about the 60 req/min rate limit and 1-hour token expiry for custom API integrations **Result**: User understands their integration options — native HubSpot sync for simplicity, or custom API pipeline for full control — with proper auth and rate limit handling ## Troubleshooting ### High bounce rate on campaigns **Symptom**: Campaign bounce rate above 3%, damaging sender reputation **Cause**: Sending to unverified or stale email addresses, or sending to catch-all domains without caution **Solution**: Always verify emails before adding to campaigns — only send to "valid" status. Re-verify lists older than 3 months. For catch-all domains, consider a test send to one address before bulk outreach. Enable email warmup on all sending mailboxes. Check your deliverability score before launching. If bounce rate is already high, pause the campaign, clean your list, and run warmup-only for 2 weeks before relaunching. See `/sales-deliverability` for a full diagnosis fra
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".