sales-influencer-marketing
Influencer marketing strategy across platforms — creator discovery, audience vetting, campaign tracking, outreach, gifting, and affiliate programs. Covers platform comparison (Modash, influData, Influencity, HypeAuditor, trendHERO, and the full long tail in references), discovery workflow, vetting (fake followers, engagement authenticity, demographics), campaign tracking (EMV, ROAS, CPM, attribution), outreach, gifting, and creator payments. Use when unsure which influencer platform to pick, can't find the right creators for your niche, worried about fake followers or inflated metrics, campaigns aren't being tracked, creators aren't responding, or influencer spend isn't showing ROI. Do NOT use for platform-specific config (use /sales-modash, /sales-infludata, /sales-influencity, /sales-hypeauditor, etc.), TikTok marketing (use /sales-tiktok-marketing), gaming influencer marketing (use /sales-gaming-marketing), ad campaigns (use /sales-retargeting), or email marketing (use /sales-email-marketing).
What this skill does
# Influencer Marketing Strategy
Helps the user plan and execute influencer marketing programs across platforms — from choosing the right tool and finding creators through vetting, outreach, campaign tracking, and ROI measurement.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated knowledge.
Ask the user:
1. **What do you need help with?**
- A) Choosing an influencer marketing platform
- B) Finding and discovering creators
- C) Vetting influencers (fake followers, audience quality)
- D) Outreach to creators (emails, DMs, negotiation)
- E) Product gifting / seeding program
- F) Campaign tracking and ROI measurement
- G) Influencer affiliate program setup
- H) Creator payments and contracts
- I) Something else — describe it
2. **What's your business type?**
- A) Ecommerce / Shopify store
- B) DTC brand
- C) SaaS / B2B
- D) Agency managing multiple clients
- E) Other — describe it
3. **What's your current setup?**
- A) Starting from scratch — no influencer program yet
- B) Manual process (spreadsheets, DMs, no tooling)
- C) Already using a platform — which one?
- D) Looking to switch platforms
4. **Budget and scale?**
- A) Small (under $1K/mo, handful of creators)
- B) Medium ($1K-5K/mo, 20-50 creators)
- C) Large ($5K+/mo, 50+ creators)
- D) Not sure yet
**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.
## Step 2 — Route or answer directly
If the request maps to a platform-specific skill, route:
- Modash setup, config, or features → `/sales-modash`
- influData setup, config, or features → `/sales-infludata`
- Creator.co setup, config, or features → `/sales-creatorco`
- Hypefy setup, config, or features → `/sales-hypefy`
- LTK setup, config, or features → `/sales-ltk`
- Influencity setup, config, or features → `/sales-influencity`
- Meltwater setup, config, or features → `/sales-meltwater`
- Skeepers setup, config, or features → `/sales-skeepers`
- Heepsy setup, config, or features → `/sales-heepsy`
- CreatorIQ setup, config, or features → `/sales-creatoriq`
- Afluencer setup, config, or features → `/sales-afluencer`
- Collabstr setup, config, or features → `/sales-collabstr`
- Cloutboost setup, config, or features → `/sales-cloutboost`
- House of Marketers agency services → `/sales-houseofmarketers`
- NeoReach setup, config, or features → `/sales-neoreach`
- inBeat agency services or free toolkit → `/sales-inbeat`
- Famesters agency services → `/sales-famesters`
- Open Influence setup, config, or agency services → `/sales-openinfluence`
- Viral Nation setup, CreatorOS, Secure, or agency services → `/sales-viralnation`
- trendHERO setup, config, or features → `/sales-trendhero`
- TikTok marketing strategy (organic, paid, content) → `/sales-tiktok-marketing`
- Gaming influencer marketing strategy → `/sales-gaming-marketing`
- HypeAuditor setup, config, or features → `/sales-hypeauditor`
- Aspire setup, config, or features → `/sales-aspire`
- Influencer Hero setup, config, or features → `/sales-influencer-hero`
- Later Influence setup, config, or features → `/sales-later`
- Sprout Social influencer features → `/sales-sproutsocial`
- Upfluence setup, Live Capture, Jaice AI, affiliate/promo codes → `/sales-upfluence`
- GRIN setup, config, or features → `/sales-grin`
- PlutoBa vetting, PlutoBa Score, brand safety, rate benchmarks → `/sales-plutoba`
- FansRevenue setup, creator monetization, or brand partnerships → `/sales-fansrevenue`
- Passionfroot setup, Zest AI agent, creator storefronts, FrootWallet → `/sales-passionfroot`
- Affiliate program design (not influencer-specific) → `/sales-affiliate-program`
- UGC galleries / shoppable content → `/sales-tagshop`
- Ad campaign strategy → `/sales-retargeting` or `/sales-b2b-advertising`
- Email marketing to subscribers → `/sales-email-marketing`
Otherwise, answer directly from the strategy knowledge below.
## Step 3 — Influencer marketing strategy reference
**Read `references/platform-guide.md`** for detailed platform comparison tables, discovery workflows, vetting frameworks, outreach best practices, rate benchmarks, gifting programs, campaign tracking, and affiliate program guidance.
*You no longer need the platform guide details — focus on the user's specific situation.*
## Step 4 — Actionable guidance
1. **Platform recommendation** — which tool fits their needs, budget, and tech stack
2. **Discovery playbook** — step-by-step search and filtering strategy
3. **Vetting checklist** — ordered checks to efficiently qualify creators
4. **Outreach templates** — personalized email/DM drafts for their specific situation
5. **Campaign plan** — tracking setup, metrics, reporting cadence
6. **Program design** — gifting, affiliate, or hybrid program structure
## Gotchas
*Best-effort from research — review these, especially items about pricing and platform capabilities that may change.*
- **Fake follower rates are high across the industry.** ~37% of influencer followers are estimated to be fake or bot accounts (2025 data). Never skip the vetting step, even for creators who look legitimate at first glance.
- **Response rates are low.** Expect 20-30% response rates on cold creator outreach. Build your shortlist at 3-5x your target number of creators. Personalization significantly improves response rates.
- **Micro-influencers outperform macro for ROI.** Creators with 10K-100K followers consistently deliver higher engagement rates and better ROAS for ecommerce brands. Don't chase follower counts.
- **Gifting ≠ guaranteed content.** No-strings gifting has a 30-50% post rate. If you need guaranteed posts, use paid partnerships or contracted gifting with clear deliverables.
- **Platform databases overlap.** Modash, influData, and Creator.co all index public profiles from the same social platforms. The differentiation is in analytics depth, workflow tools, and integrations — not the raw creator database.
- **API costs add up fast.** Both Modash and influData charge separately for API access. If you only need discovery + management, use the platform UI rather than paying for API access on top.
- **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date.
## Before recommending a specific platform skill
This skill covers a strategy domain across many platforms. **Before pointing the user to any specific platform skill** (any `/sales-{platform}` listed in `## Related skills`, e.g., `/sales-mailshake`, `/sales-klaviyo`, `/sales-apollo`), read that platform skill's actual `SKILL.md` first. The 1-line description in `## Related skills` is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.
**How to read it:**
- If `~/.claude/skills/{skill-name}/SKILL.md` exists locally, `Read` it.
- For `sales-*` skills, `WebFetch` directly from this repo: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md` — e.g., for `sales-mailshake`: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md`.
- For non-`sales-*` skills (third-party), look up `{org}/{repo}` in `~/.claude/skills/sales-do/references/skill-sources.md` if installed and fetch the same `skills/{skill-name}/SKILL.md` path under that repo.
**After reading,** ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its `argument-hint` shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's `argument-hint`. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.
## Related skills
- `/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".