sales-mixmax
Mixmax platform help — sequences, email tracking, one-click meetings, rules engine, dialer, AI Compose, Salesforce/HubSpot integration, polls, reporting. Use when Mixmax sequences aren't sending, rules or automations aren't firing, Salesforce or HubSpot sync is broken, scheduling links aren't working, open/click tracking seems inaccurate, or Mixmax emails are landing in spam. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), meeting scheduling strategy (use /sales-meeting-scheduler), email tracking strategy (use /sales-email-tracking), or connecting Mixmax to other tools via Zapier (use /sales-integration).
What this skill does
# Mixmax Platform Help Help the user with Mixmax platform questions — from sequences and email tracking through one-click meetings, rules engine, dialer, AI Compose, Salesforce/HubSpot integration, polls, and reporting. ## Step 1 — Gather context If `references/learnings.md` exists, read it first for accumulated knowledge. Ask the user: 1. **What area of Mixmax do you need help with?** - A) Sequences — multi-channel outreach campaigns (email, phone, LinkedIn, tasks) - B) Email Tracking — open, click, download, and RSVP tracking - C) Meeting Scheduling — one-click meetings, round-robin, inbound lead routing - D) Rules Engine — IF/THEN automations, Salesforce triggers, webhooks - E) Templates & Snippets — reusable email content with personalization - F) Dialer — in-Gmail calling with CRM and Gong logging - G) AI Features — AI Compose, Smart Send, AI sequence builder - H) Polls & Surveys — embedded one-click response polls in emails - I) Salesforce Integration — inbox sidebar, auto-create records, dynamic fields, advanced rules - J) HubSpot Integration — activity sync, list import, sidebar - K) Reporting — opens, clicks, bounces, replies, downloads, RSVPs - L) Admin — branding, team settings, compliance - M) API — programmatic access to sequences, messages, rules, contacts - N) Something else — describe it 2. **What's your role?** - A) Sales rep / AE / BDR - B) Sales manager / team lead - C) RevOps / Sales Ops - D) Admin / IT - E) Founder / solo seller - F) 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` - Meeting scheduling strategy → `/sales-meeting-scheduler` - Email tracking strategy → `/sales-email-tracking` - Connecting Mixmax to other tools via Zapier → `/sales-integration` Otherwise, answer directly from platform knowledge using the reference below. ## Step 3 — Mixmax 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. **Step-by-step instructions** — numbered steps to accomplish their goal in Mixmax 2. **Configuration recommendations** — specific settings to change, with navigation paths (typically via the Mixmax sidebar in Gmail or Mixmax dashboard) 3. **Common pitfalls** — what can go wrong and how to avoid it 4. **Verification** — how to confirm the change worked as expected 5. **Plan check** — flag any features that require a specific plan tier before recommending them ## Gotchas *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.* - **Mixmax is Gmail-only — there is no Outlook support.** Mixmax works exclusively as a Gmail/Google Workspace extension. Don't recommend Mixmax to users on Outlook or Microsoft 365. If they need Outlook support, suggest alternatives like Salesloft, Yesware, or Mailshake. - **Salesforce advanced rules require Growth+CRM plan (~$89/user/mo).** Basic Salesforce sidebar and activity logging are on the Growth plan, but rules triggered by Salesforce objects (opportunities, accounts, custom objects) require Growth+CRM. Always ask about the user's plan before suggesting SF-triggered automations. - **The Contacts API is deprecated.** Don't recommend building integrations against the `/contacts` endpoints. Use Salesforce or HubSpot as the contact source of truth instead. The contacts endpoints may be removed in a future API version. - **API rate limits are undocumented.** Mixmax does not publish official rate limits. The API is described as "optimized for lightweight, real-time interactions" — it is NOT suitable for bulk exports or high-volume sync. Recommend building with conservative backoff and small batch sizes. - **One-click meetings require the recipient's email client to render rich HTML.** If the recipient uses a plain-text email client or has images disabled, one-click meeting proposals won't render correctly. They'll fall back to a scheduling link, but the one-click experience is lost. - **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 Mixmax sequences) - `/sales-deliverability` — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement - `/sales-meeting-scheduler` — Meeting scheduling strategy and best practices (platform-agnostic) - `/sales-email-tracking` — Email tracking strategy and best practices (platform-agnostic) - `/sales-integration` — Connect Mixmax to other tools via Zapier, webhooks, or native integrations - `/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: Multi-channel sequence setup **User says**: "How do I set up a multi-channel sequence in Mixmax with email, phone, and LinkedIn?" **Skill does**: 1. Explains Mixmax sequences as multi-channel campaigns with email, phone, LinkedIn Sales Navigator, and task steps 2. Walks through creating a sequence: name, stages, channel per stage, timing between stages 3. Explains how to add LinkedIn Sales Navigator steps (InMail and connection requests) as automated sequence stages 4. Notes that LinkedIn Sales Navigator license is required separately **Result**: User has a multi-channel sequence with email, phone, and LinkedIn steps configured ### Example 2: Salesforce integration with advanced rules **User says**: "I want to automatically add prospects to a Mixmax sequence when an opportunity moves to a specific stage in Salesforce" **Skill does**: 1. States upfront that Salesforce object-triggered rules require Growth+CRM plan (~$89/user/mo) 2. Walks through creating an advanced rule: trigger on Salesforce Opportunity stage change → action: add related contact to sequence 3. Explains how to configure the rule trigger (Salesforce object, field, condition) and action (target sequence, recipient mapping) 4. Suggests testing with a single opportunity before applying broadly **Result**: User has an advanced rule that auto-enrolls prospects into sequences based on Salesforce deal stage changes ### Example 3: API-driven recipient management **User says**: "I want to use the Mixmax API to programmatically add recipients to a sequence" **Skill does**: 1. Points to `references/mixmax-api-reference.md` for full API documentation 2. Explains API key authentication via the `X-API-Token` header 3. Walks through the workflow: GET /sequences to find the sequence ID → POST /sequences/:id/recipients to add recipients 4. Warns about undocumented rate limits and recommends conservative batching **Result**: User understands the API workflow for adding recipients and the precautions needed ## Troubleshooting ### Email tracking not showing opens **Symptom**: Emails show as sent but no open notifications appear **Cause**: Recipient's email client blocks tracking pixels (Apple Mail Privacy Protection, corporate proxies), or tracking is not enabled for
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".