Compare commits
4 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
 Corey Haines
|
7c8c087486 | ||
|
coreyhaines31
|
fcf4b4e784 | ||
|
Corey Haines
|
cc1a9c106b | ||
|
marfert
|
cb4451c9a1 |
@@ -12,7 +12,7 @@
|
||||
"plugins": [
|
||||
{
|
||||
"name": "marketing-skills",
|
||||
"description": "33 marketing skills for technical marketers and founders: CRO, copywriting, cold email, SEO, AI SEO, paid ads, ad creative, churn prevention, pricing strategy, referral programs, revenue operations, sales enablement, site architecture, and more",
|
||||
"description": "33 marketing skills for technical marketers and founders: CRO, copywriting, cold email, SEO, AI SEO, paid ads, ad creative, churn prevention, pricing strategy, referral programs, revenue operations, sales enablement, customer research, site architecture, and more",
|
||||
"source": "./",
|
||||
"strict": false,
|
||||
"skills": [
|
||||
@@ -26,6 +26,7 @@
|
||||
"./skills/content-strategy",
|
||||
"./skills/copy-editing",
|
||||
"./skills/copywriting",
|
||||
"./skills/customer-research",
|
||||
"./skills/email-sequence",
|
||||
"./skills/form-cro",
|
||||
"./skills/free-tool-strategy",
|
||||
|
||||
@@ -168,7 +168,7 @@ This repository includes a tools registry for agent-compatible marketing tools.
|
||||
|
||||
- **Tool discovery**: Read `tools/REGISTRY.md` to see available tools and their capabilities
|
||||
- **Integration details**: See `tools/integrations/{tool}.md` for API endpoints, auth, and common operations
|
||||
- **MCP-enabled tools**: ga4, stripe, mailchimp, google-ads, resend, zapier, zoominfo, clay, supermetrics, coupler, outreach, crossbeam, composio
|
||||
- **MCP-enabled tools**: ga4, stripe, mailchimp, google-ads, resend, zapier, zoominfo, clay, supermetrics, coupler, outreach, crossbeam, introw, composio
|
||||
- **Composio** (integration layer): Adds MCP access to OAuth-heavy tools without native MCP servers (HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Sheets, Slack, etc.). See `tools/integrations/composio.md`
|
||||
|
||||
### Registry Structure
|
||||
@@ -219,3 +219,36 @@ When using any skill from this repository:
|
||||
## Skill Categories
|
||||
|
||||
See `README.md` for the current list of skills organized by category. When adding new skills, follow the naming patterns of existing skills in that category.
|
||||
|
||||
## Claude Code-Specific Enhancements
|
||||
|
||||
These patterns are **Claude Code only** and must not be added to `SKILL.md` files directly, as skills are designed to be cross-agent compatible (Codex, Cursor, Windsurf, etc.). Apply them locally in your own project's `.claude/skills/` overrides instead.
|
||||
|
||||
### Dynamic content injection with `!`command``
|
||||
|
||||
Claude Code supports embedding shell commands in SKILL.md using `` !`command` `` syntax. When the skill is invoked, Claude Code runs the command and injects the output inline — the model sees the result, not the instruction.
|
||||
|
||||
**Most useful application: auto-inject the product marketing context file**
|
||||
|
||||
Instead of every skill telling the agent "go check if `.agents/product-marketing-context.md` exists and read it," you can inject it automatically:
|
||||
|
||||
```markdown
|
||||
Product context: !`cat .agents/product-marketing-context.md 2>/dev/null || echo "No product context file found — ask the user about their product before proceeding."`
|
||||
```
|
||||
|
||||
Place this at the top of a skill's body (after frontmatter) to make context available immediately without any file-reading step.
|
||||
|
||||
**Other useful injections:**
|
||||
|
||||
```markdown
|
||||
# Inject today's date for recency-sensitive skills
|
||||
Today's date: !`date +%Y-%m-%d`
|
||||
|
||||
# Inject current git branch (useful for workflow skills)
|
||||
Current branch: !`git branch --show-current 2>/dev/null`
|
||||
|
||||
# Inject recent commits for context
|
||||
Recent commits: !`git log --oneline -5 2>/dev/null`
|
||||
```
|
||||
|
||||
**Why this is Claude Code-only**: Other agents that load skills will see the literal `` !`command` `` string rather than executing it, which would appear as garbled instructions. Keep cross-agent skill files free of this syntax.
|
||||
|
||||
@@ -32,8 +32,8 @@ Skills reference each other and build on shared context. The `product-marketing-
|
||||
├──────────┤ ├──────────┤ ├──────────┤ ├────────────┤ ├──────────┤ ├─────────────┤ ├───────────┤
|
||||
│seo-audit │ │page-cro │ │copywritng│ │paid-ads │ │referral │ │revops │ │mktg-ideas │
|
||||
│ai-seo │ │signup-cro│ │copy-edit │ │ad-creative │ │free-tool │ │sales-enable │ │mktg-psych │
|
||||
│site-arch │ │onboard │ │cold-email│ │ab-test │ │churn- │ │launch │ │ │
|
||||
│programm │ │form-cro │ │email-seq │ │analytics │ │ prevent │ │pricing │ │ │
|
||||
│site-arch │ │onboard │ │cold-email│ │ab-test │ │churn- │ │launch │ │customer- │
|
||||
│programm │ │form-cro │ │email-seq │ │analytics │ │ prevent │ │pricing │ │research │
|
||||
│schema │ │popup-cro │ │social │ │ │ │ │ │competitor │ │ │
|
||||
│content │ │paywall │ │ │ │ │ │ │ │ │ │ │
|
||||
└────┬─────┘ └────┬─────┘ └────┬─────┘ └─────┬──────┘ └────┬─────┘ └──────┬──────┘ └─────┬─────┘
|
||||
@@ -44,6 +44,7 @@ Skills reference each other and build on shared context. The `product-marketing-
|
||||
copywriting ↔ page-cro ↔ ab-test-setup
|
||||
revops ↔ sales-enablement ↔ cold-email
|
||||
seo-audit ↔ schema-markup ↔ ai-seo
|
||||
customer-research → copywriting, page-cro, competitor-alternatives
|
||||
```
|
||||
|
||||
See each skill's **Related Skills** section for the full dependency map.
|
||||
@@ -63,6 +64,7 @@ See each skill's **Related Skills** section for the full dependency map.
|
||||
| [content-strategy](skills/content-strategy/) | When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also... |
|
||||
| [copy-editing](skills/copy-editing/) | When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this... |
|
||||
| [copywriting](skills/copywriting/) | When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages,... |
|
||||
| [customer-research](skills/customer-research/) | When the user wants to conduct, analyze, or synthesize customer research — including interview transcripts, surveys, support tickets, review mining, Reddit/G2/forum research, persona generation, and voice of customer (VOC)... |
|
||||
| [email-sequence](skills/email-sequence/) | When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email... |
|
||||
| [form-cro](skills/form-cro/) | When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms,... |
|
||||
| [free-tool-strategy](skills/free-tool-strategy/) | When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or... |
|
||||
|
||||
@@ -0,0 +1,269 @@
|
||||
---
|
||||
name: customer-research
|
||||
description: When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.
|
||||
metadata:
|
||||
version: 1.0.0
|
||||
---
|
||||
|
||||
# Customer Research
|
||||
|
||||
You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with — so that everything from positioning to product to copy is grounded in reality rather than assumption.
|
||||
|
||||
## Before Starting
|
||||
|
||||
**Check for product marketing context first:**
|
||||
If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context to skip questions already answered.
|
||||
|
||||
---
|
||||
|
||||
## Two Modes of Research
|
||||
|
||||
### Mode 1: Analyze Existing Assets
|
||||
You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal.
|
||||
|
||||
### Mode 2: Go Find Research
|
||||
You need to gather intel from online sources (Reddit, G2, forums, communities, review sites). Your job is to know where to look and what to extract.
|
||||
|
||||
Most engagements combine both. Establish which mode applies before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## Mode 1: Analyzing Existing Research Assets
|
||||
|
||||
### Asset Types
|
||||
|
||||
**Customer interview / sales call transcripts**
|
||||
- Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered
|
||||
- Look for: the moment they decided to look for a solution, what they tried before, what success looks like to them
|
||||
|
||||
**Survey results**
|
||||
- Segment responses by customer tier, use case, or tenure before drawing conclusions
|
||||
- Flag: what open-ended answers say vs. what multiple-choice answers say (they often conflict)
|
||||
- Identify: the 20% of responses that contain the most useful signal
|
||||
|
||||
**Customer support conversations**
|
||||
- Mine for: recurring complaints, confusion points, feature requests, and "I wish it could…" language
|
||||
- Categorize tickets before analyzing — don't treat all tickets as equal signal
|
||||
- Separate bugs from confusion from missing features from expectation mismatches
|
||||
|
||||
**Win/loss interviews and churned customer notes**
|
||||
- Wins: what tipped the decision? What almost made them choose a competitor?
|
||||
- Losses and churn: was it price, features, fit, timing, or something else?
|
||||
- Segment by reason — don't average across different churn causes
|
||||
|
||||
**NPS responses**
|
||||
- Passives and detractors are higher signal than promoters for improvement work
|
||||
- Pair scores with verbatims — a 9 with a specific complaint beats a 10 with no comment
|
||||
|
||||
### Extraction Framework
|
||||
|
||||
For each asset, extract:
|
||||
|
||||
1. **Jobs to Be Done** — what outcome is the customer trying to achieve?
|
||||
- Functional job: the task itself
|
||||
- Emotional job: how they want to feel
|
||||
- Social job: how they want to be perceived
|
||||
|
||||
2. **Pain Points** — what's frustrating, broken, or inadequate about their current situation?
|
||||
- Prioritize pains mentioned unprompted and with emotional language
|
||||
|
||||
3. **Trigger Events** — what changed that made them seek a solution?
|
||||
- Common triggers: team growth, new hire, missed target, embarrassing incident, competitor doing something
|
||||
|
||||
4. **Desired Outcomes** — what does success look like in their words?
|
||||
- Capture exact quotes, not paraphrases
|
||||
|
||||
5. **Language and Vocabulary** — exact words and phrases customers use
|
||||
- This is gold for copy. "We were drowning in spreadsheets" > "manual process inefficiency"
|
||||
|
||||
6. **Alternatives Considered** — what else did they look at or try?
|
||||
- Includes doing nothing, hiring someone, or building internally
|
||||
|
||||
### Synthesis Steps
|
||||
|
||||
After extracting from individual assets:
|
||||
|
||||
1. **Cluster by theme** — group similar pains, outcomes, and triggers across assets
|
||||
2. **Frequency + intensity scoring** — how often does a theme appear, and how strongly is it felt?
|
||||
3. **Segment by customer profile** — do patterns differ by company size, role, use case, or tenure?
|
||||
4. **Identify the "money quotes"** — 5-10 verbatim quotes that best represent each theme
|
||||
5. **Flag contradictions** — where do customers say one thing but do another?
|
||||
|
||||
### Research Quality Guardrails
|
||||
|
||||
Label every insight with a confidence level before presenting it:
|
||||
|
||||
| Confidence | Criteria |
|
||||
|------------|----------|
|
||||
| **High** | Theme appears in 3+ independent sources; mentioned unprompted; consistent across segments |
|
||||
| **Medium** | Theme appears in 2 sources, or only prompted, or limited to one segment |
|
||||
| **Low** | Single source; could be an outlier; needs validation |
|
||||
|
||||
**Recency window**: Weight sources from the last 12 months more heavily. Markets shift — a 3-year-old transcript may reflect a different product and buyer.
|
||||
|
||||
**Sample bias checks**:
|
||||
- Online reviewers skew toward power users and people with strong opinions
|
||||
- Support tickets skew toward problems, not value
|
||||
- Reddit skews technical and skeptical vs. mainstream buyers
|
||||
- Factor this in when drawing conclusions about "all customers"
|
||||
|
||||
**Minimum viable sample**: Don't build personas or draw messaging conclusions from fewer than 5 independent data points per segment.
|
||||
|
||||
---
|
||||
|
||||
## Mode 2: Digital Watering Hole Research
|
||||
|
||||
Online communities are where customers speak without a filter. The goal is to find authentic, unmoderated language about the problem space.
|
||||
|
||||
### Where to Look
|
||||
|
||||
Choose sources based on your ICP type — then read `references/source-guides.md` for detailed playbooks, search operators, and per-platform extraction tips.
|
||||
|
||||
| ICP Type | Primary Sources |
|
||||
|----------|----------------|
|
||||
| B2B SaaS / technical buyers | Reddit (role-specific subs), G2/Capterra, Hacker News, LinkedIn, Indie Hackers |
|
||||
| SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups |
|
||||
| Developer / DevOps | r/devops, r/programming, Hacker News, Stack Overflow, Discord servers |
|
||||
| B2C / consumer | App store reviews (1-3 star), Reddit hobby/lifestyle subs, YouTube comments, TikTok/Instagram comments |
|
||||
| Enterprise | LinkedIn, industry analyst reports, G2 Enterprise filter, job postings |
|
||||
|
||||
**Quick decision guide:**
|
||||
- Have a product category? → Start with G2/Capterra reviews (yours + competitors)
|
||||
- Need raw language? → Reddit and YouTube comments
|
||||
- Need trigger events? → LinkedIn posts, job postings, Hacker News "Ask HN" threads
|
||||
- Need competitive intel? → Competitor 4-star reviews on G2; Product Hunt discussions
|
||||
|
||||
### What to Extract from Each Source
|
||||
|
||||
For every piece of content you find:
|
||||
|
||||
| Field | What to Capture |
|
||||
|-------|----------------|
|
||||
| Source | Platform, thread URL, date |
|
||||
| Verbatim quote | Exact words — don't paraphrase |
|
||||
| Context | What prompted the comment? |
|
||||
| Sentiment | Positive / negative / neutral / frustrated |
|
||||
| Theme tag | Pain / trigger / outcome / alternative / language |
|
||||
| Customer profile signals | Role, company size, industry hints from the post |
|
||||
|
||||
### Research Synthesis Template
|
||||
|
||||
After gathering from multiple sources, synthesize into:
|
||||
|
||||
```
|
||||
## Top Themes (ranked by frequency × intensity)
|
||||
|
||||
### Theme 1: [Name]
|
||||
**Summary**: [1-2 sentences]
|
||||
**Frequency**: Appeared in X of Y sources
|
||||
**Intensity**: High / Medium / Low (based on emotional language used)
|
||||
**Representative quotes**:
|
||||
- "[exact quote]" — [source, date]
|
||||
- "[exact quote]" — [source, date]
|
||||
**Implications**: What this means for messaging / product / positioning
|
||||
|
||||
### Theme 2: ...
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Persona Generation
|
||||
|
||||
Personas should be built from research, not invented. Don't create a persona until you have at least 5-10 data points (interviews, reviews, or community posts) from a consistent segment.
|
||||
|
||||
### Persona Structure
|
||||
|
||||
```
|
||||
## [Persona Name] — [Role/Title]
|
||||
|
||||
**Profile**
|
||||
- Title range: [e.g., "Marketing Manager to VP of Marketing"]
|
||||
- Company size: [e.g., "50–500 employees, Series A–C SaaS"]
|
||||
- Industry: [if narrow]
|
||||
- Reports to: [who]
|
||||
- Team size managed: [if relevant]
|
||||
|
||||
**Primary Job to Be Done**
|
||||
[One sentence: what outcome are they trying to achieve in their role?]
|
||||
|
||||
**Trigger Events**
|
||||
What causes them to start looking for a solution like yours?
|
||||
- [trigger 1]
|
||||
- [trigger 2]
|
||||
|
||||
**Top Pains**
|
||||
1. [Pain — in their words if possible]
|
||||
2. [Pain]
|
||||
3. [Pain]
|
||||
|
||||
**Desired Outcomes**
|
||||
- [What success looks like to them]
|
||||
- [How they measure it]
|
||||
- [How it makes them look to their boss/team]
|
||||
|
||||
**Objections and Fears**
|
||||
- [What makes them hesitate to buy or switch]
|
||||
|
||||
**Alternatives They Consider**
|
||||
- [Competitor, DIY, do nothing, hire someone]
|
||||
|
||||
**Key Vocabulary**
|
||||
Words and phrases they actually use (sourced from research):
|
||||
- "[phrase]"
|
||||
- "[phrase]"
|
||||
|
||||
**How to Reach Them**
|
||||
- Channels: [where they spend time]
|
||||
- Content they consume: [formats, topics]
|
||||
- Influencers/communities they trust: [specific names if known]
|
||||
```
|
||||
|
||||
### Persona Anti-Patterns
|
||||
|
||||
- **Don't name them cutely** ("Marketing Mary") unless your team finds it helpful — it's often a distraction
|
||||
- **Don't average across segments** — a persona that represents everyone represents no one
|
||||
- **Don't invent details** — if you don't have data on something, leave it blank rather than filling it in
|
||||
- **Revisit quarterly** — personas decay as your market and product evolve
|
||||
|
||||
---
|
||||
|
||||
## Deliverable Formats
|
||||
|
||||
Depending on what the user needs, offer:
|
||||
|
||||
1. **Research synthesis report** — themes, quotes, patterns, and implications
|
||||
2. **VOC quote bank** — organized verbatim quotes by theme, for use in copy
|
||||
3. **Persona document** — 1-3 personas built from the research
|
||||
4. **Jobs-to-be-done map** — functional, emotional, and social jobs by segment
|
||||
5. **Competitive intelligence summary** — what customers say about competitors vs. you
|
||||
6. **Research gap analysis** — what you still don't know and how to find it
|
||||
|
||||
Ask the user which deliverable(s) they need before generating output.
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask Before Proceeding
|
||||
|
||||
If context is unclear:
|
||||
|
||||
1. **What's the goal?** Improve messaging? Build personas? Find product gaps? Understand churn?
|
||||
2. **What do you already have?** (transcripts, surveys, tickets, G2 reviews, nothing)
|
||||
3. **Who is the target segment?** (all customers, a specific tier, churned users, prospects who didn't buy)
|
||||
4. **What's your product?** (if not in the product marketing context file)
|
||||
5. **What do you want delivered?** (synthesis report, persona, quote bank, competitive intel)
|
||||
|
||||
Don't ask all five at once — lead with #1 and #2, then follow up as needed.
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
| When to hand off | Skill |
|
||||
|-----------------|-------|
|
||||
| Writing copy informed by the research | `copywriting` |
|
||||
| Optimizing a page using VOC insights | `page-cro` |
|
||||
| Building a competitor comparison page | `competitor-alternatives` |
|
||||
| Creating a churn prevention strategy from churn research | `churn-prevention` |
|
||||
| Planning paid ads informed by research | `paid-ads` |
|
||||
| Writing cold email using research on pain/trigger | `cold-email` |
|
||||
| Planning content based on discovered topics | `content-strategy` |
|
||||
@@ -0,0 +1,162 @@
|
||||
{
|
||||
"skill_name": "customer-research",
|
||||
"evals": [
|
||||
{
|
||||
"id": 1,
|
||||
"prompt": "I have 20 customer interview transcripts. Help me analyze them.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should ask about the goal before analyzing (improve messaging, build personas, find product gaps, etc.). Should apply the extraction framework: jobs to be done, pain points, trigger events, desired outcomes, language/vocabulary, alternatives considered. Should recommend clustering by theme, frequency + intensity scoring, and identifying money quotes. Should ask which deliverable is needed.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Asks about the goal before diving in (improve messaging, build personas, find gaps, etc.)",
|
||||
"Mentions extracting jobs to be done, pain points, and desired outcomes",
|
||||
"Suggests organizing quotes by theme",
|
||||
"References frequency and intensity scoring",
|
||||
"Asks which deliverable is needed"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 2,
|
||||
"prompt": "I want to do ICP research but I don't have any customer interviews yet.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should recommend digital watering hole research as a starting point. Should mention Reddit, G2, Capterra, forums, or niche communities as sources. Should offer to plan a research approach and explain what to extract from online sources. Should note this is Mode 2 and ask what product/category to research.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Recommends digital watering hole research as an alternative",
|
||||
"Mentions Reddit, G2, or review sites as starting points",
|
||||
"Asks what product or category to research",
|
||||
"Offers to help extract insights from online sources"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 3,
|
||||
"prompt": "Mine Reddit and G2 to understand what people hate about project management software.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should identify relevant subreddits (r/projectmanagement, r/productivity, r/agile) and search strategies. Should recommend reading 3-star and 1-star G2 reviews and competitor 4-star reviews. Should plan to extract verbatim quotes, pain themes, and switching triggers. Should apply the extraction table (source, quote, context, sentiment, theme tag, profile signals).",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Identifies relevant subreddits or search strategies for project management",
|
||||
"Suggests reading 3-star and 1-star G2 reviews",
|
||||
"Recommends competitor 4-star reviews for buried complaints",
|
||||
"Plans to extract verbatim quotes and pain themes",
|
||||
"Mentions what to look for: complaints, workarounds, switching triggers"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 4,
|
||||
"prompt": "Build me a customer persona for a marketing manager at a B2B SaaS company.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should ask if there is existing research to build from before generating a persona. Should warn against inventing details without data. Should use the persona structure: profile, primary JTBD, trigger events, top pains, desired outcomes, objections, alternatives, key vocabulary, how to reach them. Should note that personas should be built from at least 5-10 data points.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Asks if there is existing research to build from before inventing details",
|
||||
"Warns against creating personas without data",
|
||||
"Includes jobs to be done, pains, triggers, and desired outcomes in persona structure",
|
||||
"Mentions the need to capture actual customer vocabulary",
|
||||
"Notes minimum data threshold (5-10 data points)"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 5,
|
||||
"prompt": "I have 6 months of customer support tickets. What insights can I pull from them?",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should recommend categorizing tickets before analyzing (bugs vs. confusion vs. feature requests vs. expectation mismatches). Should warn against treating all tickets as equal signal. Should suggest extracting recurring language, patterns, and 'I wish it could…' phrases. Should ask about the goal — product improvement, messaging, reducing support load, or something else.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Recommends categorizing tickets before analyzing (bugs vs confusion vs feature requests)",
|
||||
"Warns against treating all tickets as equal signal",
|
||||
"Mentions extracting recurring language and patterns",
|
||||
"Asks about the goal — product improvement, messaging, or something else"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 6,
|
||||
"prompt": "What are customers saying about my competitors on review sites?",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should ask which competitors to research. Should recommend G2 and Capterra as primary sources. Should specifically call out reading competitor 4-star reviews for buried complaints. Should describe what to extract: what they love (battlecard intel), what frustrates them (opportunities), unmet needs. Should use the review mining template.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Recommends reading competitor 4-star reviews specifically for buried complaints",
|
||||
"Mentions G2 or Capterra as sources",
|
||||
"Describes what to extract: what they love, what frustrates them, unmet needs",
|
||||
"Frames as competitive intelligence input"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 7,
|
||||
"prompt": "Help me do voice of customer research for a new SaaS in the HR space.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should ask about the specific ICP segment within HR (recruiter, HR generalist, CHRO, etc.). Should suggest relevant digital watering holes: r/humanresources, r/recruiting, HR Slack communities, G2 HR category, LinkedIn. Should plan to extract verbatim language for copy use. Should offer to produce a VOC quote bank as a deliverable.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Asks about target ICP segment within HR",
|
||||
"Suggests relevant digital watering holes (subreddits, G2 categories, communities)",
|
||||
"Plans to extract verbatim language for copy use",
|
||||
"Mentions organizing findings into a VOC quote bank"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 8,
|
||||
"prompt": "I want to understand why customers churn. I have exit survey results.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should recommend segmenting churn reasons before analyzing — do not average across different causes. Should suggest pairing open-ended responses with quantitative data. Should ask if win/loss interview data or support tickets are also available. Should apply confidence labels (high/med/low) based on sample size and source consistency.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Recommends segmenting churn reasons before analyzing",
|
||||
"Warns against averaging across different churn causes",
|
||||
"Suggests pairing open-ended responses with quantitative data",
|
||||
"Asks if win/loss interview data is also available"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 9,
|
||||
"prompt": "Find the digital watering holes where DevOps engineers talk shop.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should identify specific relevant communities: r/devops, r/sysadmin, Hacker News, DevOps-focused Discord/Slack groups, LinkedIn, Stack Overflow. Should suggest what to search for in those communities. Should describe what signal to extract from each source type and reference source-guides.md for detailed playbooks.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Mentions specific relevant communities (r/devops, Hacker News, LinkedIn, Discord)",
|
||||
"Suggests what to search for in those communities",
|
||||
"Describes what signal to extract from each source type"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 10,
|
||||
"prompt": "Turn my customer research into messaging I can use on my homepage.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should extract VOC language and top themes before moving to copy. Should identify the highest-signal quotes and language patterns. Should produce a VOC summary or quote bank, then hand off to the copywriting skill for the actual copy writing step rather than writing homepage copy directly.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Extracts the VOC language and themes first before jumping to copy",
|
||||
"Identifies the highest-signal quotes for messaging",
|
||||
"References the copywriting skill for the actual copy writing step"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 11,
|
||||
"prompt": "I run a mobile fitness app and want to understand why users drop off after week 2.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should recognize this as a B2C research scenario. Should suggest B2C-appropriate sources: app store reviews (1-3 star), Reddit fitness communities, YouTube comment sections on fitness apps, TikTok/Instagram comments. Should also recommend in-app surveys and analyzing support tickets/reviews. Should frame around activation and habit formation research.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Recognizes this as a B2C research scenario",
|
||||
"Suggests app store reviews as a primary source",
|
||||
"Mentions Reddit or community sources relevant to fitness/consumer apps",
|
||||
"Frames around understanding drop-off triggers and desired outcomes"
|
||||
],
|
||||
"files": []
|
||||
},
|
||||
{
|
||||
"id": 12,
|
||||
"prompt": "I have no existing research and don't know who my best customers are yet.",
|
||||
"expected_output": "Should check for product-marketing-context.md first. Should treat this as a bootstrap research scenario. Should recommend starting with hypothesis formation before gathering data. Should suggest a minimum viable research plan: 5-10 customer interviews + digital watering hole scan. Should provide interview recruiting tips and what questions to ask. Should warn against building personas before collecting any data.",
|
||||
"assertions": [
|
||||
"Checks for product-marketing-context.md",
|
||||
"Recognizes this as a zero-research bootstrap scenario",
|
||||
"Recommends forming hypotheses before gathering data",
|
||||
"Suggests a minimum viable research plan (interviews + online sources)",
|
||||
"Warns against building personas without any data"
|
||||
],
|
||||
"files": []
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,345 @@
|
||||
# Customer Research — Source Guides
|
||||
|
||||
Detailed, source-by-source playbooks for gathering customer intelligence from online watering holes.
|
||||
|
||||
---
|
||||
|
||||
## Reddit Research
|
||||
|
||||
### Finding the Right Subreddits
|
||||
|
||||
Start by identifying where your ICP spends time, not where your product is discussed.
|
||||
|
||||
**Discovery methods:**
|
||||
- Search `site:reddit.com "[job title] tools"` or `site:reddit.com "[problem category] software"`
|
||||
- Use [subreddit search tools](https://www.reddit.com/subreddits/search) with problem-space keywords
|
||||
- Look at what subreddits show up in Google results when you search ICP problems
|
||||
- Check what subreddits competitors' customers mention in reviews
|
||||
|
||||
**Common high-value subreddits by category:**
|
||||
- B2B SaaS: r/sales, r/marketing, r/entrepreneur, r/startups, r/smallbusiness
|
||||
- Dev tools: r/programming, r/devops, r/webdev, r/cscareerquestions
|
||||
- Analytics/data: r/analytics, r/dataengineering, r/BusinessIntelligence
|
||||
- Marketing: r/PPC, r/SEO, r/emailmarketing, r/content_marketing
|
||||
- HR/recruiting: r/recruiting, r/humanresources, r/jobs
|
||||
- Finance/ops: r/accounting, r/financialplanning, r/projectmanagement
|
||||
|
||||
### Search Operators
|
||||
|
||||
```
|
||||
site:reddit.com/r/[subreddit] "[keyword]"
|
||||
site:reddit.com "[problem]" "recommend" OR "suggestion" OR "alternative"
|
||||
site:reddit.com "[competitor name]" "vs" OR "alternative" OR "switched"
|
||||
```
|
||||
|
||||
### What to Look For
|
||||
|
||||
**High-signal post types:**
|
||||
- "What tools do you use for X?" → reveals alternatives and vocab
|
||||
- "Frustrated with [competitor], looking for alternatives" → reveals pain and switching triggers
|
||||
- "How do you handle X?" → reveals workflow and workarounds
|
||||
- "Is [your category] worth it?" → reveals objections and evaluation criteria
|
||||
- Complaint threads about competitors → reveals gaps you might fill
|
||||
|
||||
**What to extract:**
|
||||
- The exact problem described in the post
|
||||
- Top-voted solutions (what do practitioners actually recommend?)
|
||||
- Complaints about existing solutions in comments
|
||||
- The language used — note specific words and phrases
|
||||
- Upvote patterns — consensus vs. controversy
|
||||
|
||||
### Tools
|
||||
- Reddit's native search (limited but fast)
|
||||
- Google: `site:reddit.com [query]` (better results)
|
||||
- Pullpush.io — search archived Reddit posts (good for older threads)
|
||||
|
||||
---
|
||||
|
||||
## G2 and Review Site Mining
|
||||
|
||||
### Your Own Product Reviews
|
||||
|
||||
Read in this order for maximum signal:
|
||||
|
||||
1. **3-star reviews** — these are the most honest. Customer liked it enough to stay but felt something was missing.
|
||||
2. **1-star reviews** — understand the failure modes. Separate product issues from support/onboarding issues.
|
||||
3. **5-star reviews** — extract the "what they love" language. These are your proof points.
|
||||
4. **4-star reviews** — often contain "the only thing I wish…" buried in praise.
|
||||
|
||||
**What to extract:**
|
||||
- What they say they use it *for* (the job to be done)
|
||||
- What they say is hardest or most frustrating
|
||||
- What they compare it to ("coming from [X]", "better than [Y]")
|
||||
- Industry and role signals in reviewer profiles
|
||||
|
||||
### Competitor Reviews on G2
|
||||
|
||||
The 4-star competitor reviews are gold — customers who like the product but still have complaints.
|
||||
|
||||
**G2 structure to exploit:**
|
||||
- "What do you like best?" → their strengths (your battlecard intel)
|
||||
- "What do you dislike?" → their weaknesses (your opportunities)
|
||||
- "What problems are you solving?" → the job to be done
|
||||
|
||||
**Capterra** has similar structure. **Trustpilot** skews B2C. **AppSumo** reviews are useful for SMB/prosumer SaaS.
|
||||
|
||||
### Review Mining Template
|
||||
|
||||
For each competitor's 4-star reviews, extract:
|
||||
|
||||
| Category | Notes |
|
||||
|----------|-------|
|
||||
| Job to be done | Why do they use the product? |
|
||||
| Top praise | What do they love (and might be hard for you to match)? |
|
||||
| Top complaint | What frustrates them? |
|
||||
| Switching context | Did they mention switching from something else? |
|
||||
| Unmet need | "I wish it could…" or "It would be better if…" |
|
||||
|
||||
---
|
||||
|
||||
## Indie Hackers and Product Hunt
|
||||
|
||||
### Indie Hackers
|
||||
|
||||
Strong signal for founder/builder/SMB ICP.
|
||||
|
||||
**Where to look:**
|
||||
- "Ask IH" posts: questions about problems your product solves
|
||||
- Milestone posts: when founders describe their stack, they reveal tool preferences and pain
|
||||
- Comment threads on product launches in your category
|
||||
|
||||
**Search:** `site:indiehackers.com "[problem]"` or use IH's native search.
|
||||
|
||||
### Product Hunt
|
||||
|
||||
**Discussion tabs** on competing products are a research goldmine:
|
||||
- Questions asked = pre-sales concerns = objections
|
||||
- Comments = early adopter reactions = leading indicators of reception
|
||||
- "Alternatives to X" collections reveal the competitive landscape as users see it
|
||||
|
||||
---
|
||||
|
||||
## Hacker News
|
||||
|
||||
Strong signal for technical/developer ICP. Skews toward builders and skeptics.
|
||||
|
||||
**High-value searches:**
|
||||
- `site:news.ycombinator.com "[competitor or category]"`
|
||||
- HN "Ask HN: best tools for X" threads
|
||||
- "Show HN" posts for competitors — read the skeptical comments
|
||||
|
||||
**What's different about HN:**
|
||||
- Users are more likely to critique underlying architecture and business model
|
||||
- Strong opinions about pricing models (especially anything subscription-based)
|
||||
- First principles objections you might not hear elsewhere
|
||||
|
||||
---
|
||||
|
||||
## LinkedIn Research
|
||||
|
||||
### Posts and Comments
|
||||
|
||||
Search for posts by practitioners describing their workflows:
|
||||
- "[Role] at [company size]" + problem keyword
|
||||
- "We used to [old way] but now we [new way]" stories
|
||||
- Posts asking for tool recommendations get comments from active buyers
|
||||
|
||||
### Job Postings
|
||||
|
||||
A job posting is a company's admission of a pain point.
|
||||
|
||||
**What to look for:**
|
||||
- What tools are listed as "nice to have" vs. "required"? (reveals stack and adjacent tools)
|
||||
- What metrics and outcomes are mentioned in the role description?
|
||||
- What does the role spend most of its time doing? (reveals the job to be done)
|
||||
|
||||
**Search:** `site:linkedin.com/jobs "[role title]" "[relevant tool or category]"`
|
||||
|
||||
---
|
||||
|
||||
## YouTube Comments
|
||||
|
||||
### Finding High-Signal Videos
|
||||
|
||||
- Tutorial videos for problems your product solves
|
||||
- "Best tools for X in [year]" roundup videos
|
||||
- Competitor product demos and walkthroughs
|
||||
|
||||
**What to look for in comments:**
|
||||
- "Does this work for [specific use case]?" → edge cases and unmet needs
|
||||
- "I tried this but…" → failure points
|
||||
- "What about [competitor]?" → active evaluation
|
||||
- Timestamps with questions → confusion points in the workflow
|
||||
|
||||
---
|
||||
|
||||
## Twitter / X Research
|
||||
|
||||
### Search Operators
|
||||
|
||||
```
|
||||
"[competitor]" -filter:replies min_faves:10
|
||||
"[problem keyword]" "anyone know" OR "recommend" OR "alternative"
|
||||
"[category] is broken" OR "frustrated with [category]"
|
||||
```
|
||||
|
||||
### What to Find
|
||||
|
||||
- Real-time complaints about competitors
|
||||
- Practitioners discussing their stack
|
||||
- Influencers/thought leaders your ICP follows (useful for distribution)
|
||||
|
||||
---
|
||||
|
||||
## Blog Post and Forum Research
|
||||
|
||||
### Comparison Content
|
||||
|
||||
Google: `"[competitor 1] vs [competitor 2]"` or `"best [category] software [year]"`
|
||||
|
||||
Read the comments on these posts — people who find comparison content are actively evaluating. Their comments are questions your sales process should answer.
|
||||
|
||||
### Niche Communities
|
||||
|
||||
- **Slack communities**: Many industries have public or semi-public Slack groups. Search "[industry] Slack community".
|
||||
- **Discord servers**: Growing for developer and creator communities.
|
||||
- **Facebook Groups**: Still strong for SMB, e-commerce, agency, and coach/consultant ICP.
|
||||
- **Circle/Mighty Networks communities**: Check if there are paid communities in your ICP's space.
|
||||
|
||||
---
|
||||
|
||||
## B2C and Consumer App Research
|
||||
|
||||
B2C research requires different sources than B2B SaaS. Consumer buyers don't congregate on LinkedIn or G2 — they leave traces in app stores, social media, and communities built around the activity your product serves.
|
||||
|
||||
### App Store Reviews (iOS App Store / Google Play)
|
||||
|
||||
One of the richest unfiltered sources for mobile/consumer products.
|
||||
|
||||
**Read in this order:**
|
||||
1. **1-2 star reviews** — failure modes, unmet expectations, frustration peaks
|
||||
2. **3-star reviews** — honest tradeoffs and "it's good but…" feedback
|
||||
3. **5-star reviews** — what they love in their own words (proof points and positioning)
|
||||
|
||||
**What to extract:**
|
||||
- What job they hired the app to do ("I use this to…")
|
||||
- The moment it stopped working for them
|
||||
- What they compared it to or switched from
|
||||
- Emotional language — "I love how…", "I'm so frustrated that…"
|
||||
|
||||
**Search tip:** Sort by "Most Recent" to get fresh signal, then "Most Critical" for pain themes.
|
||||
|
||||
### Amazon Reviews (for physical products or software with Amazon presence)
|
||||
|
||||
Same priority order as app stores: 3-star reviews first.
|
||||
|
||||
**G2 analog for consumer SaaS**: Trustpilot, Sitejabber, and product-specific review aggregators.
|
||||
|
||||
### Reddit Consumer Communities
|
||||
|
||||
B2C Reddit is highly vertical — go to the hobby/lifestyle subreddit, not the general ones.
|
||||
|
||||
**Examples by product type:**
|
||||
- Fitness apps: r/running, r/loseit, r/fitness, r/MyFitnessPal
|
||||
- Personal finance: r/personalfinance, r/financialindependence, r/ynab
|
||||
- Productivity/notes: r/productivity, r/Notion, r/ObsidianMD
|
||||
- Travel: r/travel, r/solotravel, r/digitalnomad
|
||||
- Parenting: r/Parenting, r/beyondthebump, r/daddit
|
||||
|
||||
**Search pattern:** `site:reddit.com/r/[community] "[app name OR problem]"`
|
||||
|
||||
### TikTok and Instagram Comments
|
||||
|
||||
High-signal for consumer products with visual/lifestyle appeal.
|
||||
|
||||
**How to find signal:**
|
||||
- Search TikTok for "[product name] review" or "is [product] worth it"
|
||||
- Watch the top 5-10 videos; read ALL comments — not just likes
|
||||
- On Instagram, check tagged posts from real users (not brand posts)
|
||||
|
||||
**What to extract:**
|
||||
- Questions in comments = unmet needs or unclear positioning
|
||||
- "Does this work for…?" = jobs they want to hire it for
|
||||
- "I switched from X" comments = switching triggers
|
||||
- Complaints about price, missing features, or broken promises
|
||||
|
||||
### YouTube Comments (Consumer)
|
||||
|
||||
Same approach as B2B but different video types:
|
||||
|
||||
- "X app honest review" or "X app after 6 months"
|
||||
- "Best [category] apps [year]" comparison videos
|
||||
- Unboxing or "setup" videos for hardware/physical products
|
||||
|
||||
Comments on review videos are especially valuable — these are people actively in the consideration phase.
|
||||
|
||||
### Consumer Community Platforms
|
||||
|
||||
- **Facebook Groups**: Still dominant for many consumer verticals (parenting, fitness, local services, hobbies)
|
||||
- **Discord servers**: Growing for gaming, creator tools, productivity, crypto, lifestyle communities
|
||||
- **Nextdoor**: Useful for local service businesses
|
||||
- **Quora**: Long-form questions reveal decision anxiety and evaluation criteria
|
||||
|
||||
---
|
||||
|
||||
## Organizing Your Research
|
||||
|
||||
Use a simple tagging system across all sources:
|
||||
|
||||
| Tag | Meaning |
|
||||
|-----|---------|
|
||||
| `#pain` | A problem or frustration |
|
||||
| `#trigger` | An event that prompted the search |
|
||||
| `#outcome` | What success looks like |
|
||||
| `#language` | Exact phrases worth using in copy |
|
||||
| `#alternative` | Another solution they considered or use |
|
||||
| `#objection` | Reason to hesitate or not buy |
|
||||
| `#competitor` | Anything about a competing product |
|
||||
|
||||
Keep a running doc with columns: Source | Date | Quote | Tags | Notes
|
||||
|
||||
After 20-30 entries, patterns will emerge. Look for quotes that appear in multiple unrelated sources — those are your highest-confidence insights.
|
||||
|
||||
---
|
||||
|
||||
## Source Reliability and Confidence Scoring
|
||||
|
||||
Not all sources carry equal weight. Use this guide when assigning confidence labels.
|
||||
|
||||
### Source Weighting
|
||||
|
||||
| Source | Signal Strength | Bias to Note |
|
||||
|--------|----------------|--------------|
|
||||
| Customer interviews (unprompted) | Very high | Small sample; selection bias toward engaged customers |
|
||||
| Win/loss interviews | High | Recent memory only; rationalization common |
|
||||
| App store / G2 reviews | High | Skews toward strong opinions (love or hate) |
|
||||
| Reddit / community posts | Medium-high | Skews technical, skeptical, vocal minorities |
|
||||
| Support tickets | Medium | Skews toward problems; silent majority not represented |
|
||||
| Survey (open-ended) | Medium | Primed by question framing |
|
||||
| Survey (multiple choice) | Low-medium | Artifacts of the options you provided |
|
||||
| NPS verbatims | Medium | Correlates with score; prompted by the survey moment |
|
||||
| YouTube/TikTok comments | Medium | Skews toward engaged viewers; social performance |
|
||||
| Job postings | Low-medium | Aspirational, not necessarily reflective of current pain |
|
||||
|
||||
### Confidence Labels in Practice
|
||||
|
||||
When presenting insights, lead with confidence:
|
||||
|
||||
```
|
||||
[HIGH CONFIDENCE] Customers feel overwhelmed by manual reporting — appears in 12 of 20 interviews,
|
||||
4 Reddit threads, and is the #1 complaint in 3-star G2 reviews. Consistent across SMB and mid-market.
|
||||
|
||||
[MEDIUM CONFIDENCE] Customers compare us to spreadsheets more than to direct competitors —
|
||||
mentioned in 6 interviews and 3 Reddit threads, but not yet seen in review data.
|
||||
|
||||
[LOW CONFIDENCE] Enterprise buyers may have procurement concerns — mentioned by 2 interviewees
|
||||
from companies 500+. Needs more signal before acting on it.
|
||||
```
|
||||
|
||||
### Recency Window
|
||||
|
||||
- **Use as primary source**: Data from the last 12 months
|
||||
- **Use with caution**: 12-24 months (product and market may have shifted)
|
||||
- **Use only for baseline context**: 2+ years old
|
||||
|
||||
When a theme appears consistently across old and new data, that's a durable signal worth acting on.
|
||||
@@ -293,6 +293,7 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email
|
||||
|------|----------|:---:|-------|
|
||||
| **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) |
|
||||
| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) |
|
||||
| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) |
|
||||
| **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) |
|
||||
| **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) |
|
||||
| **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
|
||||
|
||||
@@ -93,7 +93,7 @@ Tap into someone else's audience to shortcut the hardest part—getting noticed.
|
||||
1. List industry leaders your audience follows
|
||||
2. Pitch win-win collaborations
|
||||
3. Use tools like SparkToro or Listen Notes to find audience overlap
|
||||
4. Set up affiliate/referral incentives
|
||||
4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](../../tools/integrations/introw.md) to manage deal registration and commissions)
|
||||
|
||||
**Example - TRMNL:**
|
||||
Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
|
||||
|
||||
@@ -244,6 +244,8 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key tools
|
||||
| **Mention Me** | Enterprise referral programs | [mention-me.md](../../tools/integrations/mention-me.md) |
|
||||
| **Dub.co** | Link tracking and attribution | [dub-co.md](../../tools/integrations/dub-co.md) |
|
||||
| **Stripe** | Payment processing (for commission tracking) | [stripe.md](../../tools/integrations/stripe.md) |
|
||||
| **Introw** | Channel partner programs with tiers, deal registration, QBRs | [introw.md](../../tools/integrations/introw.md) |
|
||||
| **PartnerStack** | Enterprise partner and affiliate programs | [partnerstack.md](../../tools/integrations/partnerstack.md) |
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -118,6 +118,9 @@ Provide affiliates with:
|
||||
- Tapfiliate — Simple SaaS affiliate tracking
|
||||
- FirstPromoter — SaaS affiliate management
|
||||
|
||||
**Partner Relationship Management (PRM):**
|
||||
- Introw — Full PRM with deal registration, commissions, tiers, QBRs, and partner engagement tracking ([integration guide](../../../tools/integrations/introw.md))
|
||||
|
||||
**Self-hosted:**
|
||||
- Rewardful — Stripe-integrated affiliates
|
||||
- Refersion — E-commerce affiliates
|
||||
|
||||
@@ -330,6 +330,8 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md). Key RevOp
|
||||
| **Apollo** | Contact data, enrichment, and outbound sequences | [apollo.md](../../tools/integrations/apollo.md) |
|
||||
| **ActiveCampaign** | Marketing automation for SMBs, lead scoring | [activecampaign.md](../../tools/integrations/activecampaign.md) |
|
||||
| **Zapier** | Cross-tool automation and workflow glue | [zapier.md](../../tools/integrations/zapier.md) |
|
||||
| **Introw** | Partner-sourced pipeline, commissions, deal registration, QBRs | [introw.md](../../tools/integrations/introw.md) |
|
||||
| **Crossbeam** | Partner account overlaps and co-sell identification | [crossbeam.md](../../tools/integrations/crossbeam.md) |
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -339,6 +339,16 @@ If context is missing, ask:
|
||||
|
||||
---
|
||||
|
||||
## Tool Integrations
|
||||
|
||||
For partner sales enablement, see the [tools registry](../../tools/REGISTRY.md):
|
||||
|
||||
| Tool | What It Does | Guide |
|
||||
|------|-------------|-------|
|
||||
| **Introw** | Partner engagement tracking, deal registration, mutual action plans | [introw.md](../../tools/integrations/introw.md) |
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **competitor-alternatives**: For public-facing comparison and alternative pages
|
||||
|
||||
@@ -164,7 +164,7 @@ Reporting "no schema found" based solely on `web_fetch` or `curl` leads to false
|
||||
- Primary keyword near beginning
|
||||
- 50-60 characters (visible in SERP)
|
||||
- Compelling and click-worthy
|
||||
- Brand name placement (end, usually)
|
||||
- No brand name placement (SERPs include brand name above title already)
|
||||
|
||||
**Common issues:**
|
||||
- Duplicate titles
|
||||
|
||||
+6
-1
@@ -46,6 +46,7 @@ Quick reference for AI agents to discover tool capabilities and integration meth
|
||||
| customer-io | Email | ✓ | - | [✓](clis/customer-io.js) | ✓ | [customer-io.md](integrations/customer-io.md) |
|
||||
| sendgrid | Email | ✓ | - | [✓](clis/sendgrid.js) | ✓ | [sendgrid.md](integrations/sendgrid.md) |
|
||||
| resend | Email | ✓ | ✓ | [✓](clis/resend.js) | ✓ | [resend.md](integrations/resend.md) |
|
||||
| nitrosend | Email | ✓ | ✓ | - | - | [nitrosend.md](integrations/nitrosend.md) |
|
||||
| kit | Email | ✓ | - | [✓](clis/kit.js) | ✓ | [kit.md](integrations/kit.md) |
|
||||
| beehiiv | Newsletter | ✓ | - | [✓](clis/beehiiv.js) | - | [beehiiv.md](integrations/beehiiv.md) |
|
||||
| klaviyo | Email/SMS | ✓ | - | [✓](clis/klaviyo.js) | ✓ | [klaviyo.md](integrations/klaviyo.md) |
|
||||
@@ -69,8 +70,10 @@ Quick reference for AI agents to discover tool capabilities and integration meth
|
||||
| intercom | Messaging | ✓ | - | [✓](clis/intercom.js) | ✓ | [intercom.md](integrations/intercom.md) |
|
||||
| outreach | Sales Engagement | ✓ | ✓ | [✓](clis/outreach.js) | - | [outreach.md](integrations/outreach.md) |
|
||||
| crossbeam | Partner Ecosystem | ✓ | ✓ | [✓](clis/crossbeam.js) | - | [crossbeam.md](integrations/crossbeam.md) |
|
||||
| introw | Partner Ecosystem | - | ✓ | - | - | [introw.md](integrations/introw.md) |
|
||||
| pendo | Product Analytics | ✓ | - | [✓](clis/pendo.js) | - | [pendo.md](integrations/pendo.md) |
|
||||
| similarweb | Competitive Intelligence | ✓ | - | [✓](clis/similarweb.js) | - | [similarweb.md](integrations/similarweb.md) |
|
||||
| firehose | Competitive Intelligence | ✓ | - | - | - | [firehose.md](integrations/firehose.md) |
|
||||
| airops | AI Content | ✓ | - | [✓](clis/airops.js) | - | [airops.md](integrations/airops.md) |
|
||||
| buffer | Social | ✓ | - | [✓](clis/buffer.js) | - | [buffer.md](integrations/buffer.md) |
|
||||
| wistia | Video | ✓ | - | [✓](clis/wistia.js) | - | [wistia.md](integrations/wistia.md) |
|
||||
@@ -354,8 +357,9 @@ Partner data sharing, co-sell, and ecosystem management.
|
||||
| Tool | Best For | Notes |
|
||||
|------|----------|-------|
|
||||
| **crossbeam** | Account overlaps, co-sell | Now part of Reveal |
|
||||
| **introw** | Partner management, deal registration, QBRs | MCP-enabled PRM |
|
||||
|
||||
**Agent recommendation**: Crossbeam for identifying partner account overlaps and co-sell opportunities.
|
||||
**Agent recommendation**: Crossbeam for identifying partner account overlaps and co-sell opportunities. Introw for full partner relationship management — partner pipeline, commissions, tasks, and automated business review prep.
|
||||
|
||||
### Email Outreach
|
||||
|
||||
@@ -426,6 +430,7 @@ These tools have Model Context Protocol servers available, enabling direct agent
|
||||
- **coupler** - Marketing data pipelines
|
||||
- **outreach** - Sales engagement sequences
|
||||
- **crossbeam** - Partner ecosystem data
|
||||
- **introw** - Partner relationship management
|
||||
|
||||
To use MCP tools, ensure the appropriate MCP server is configured in your environment.
|
||||
|
||||
|
||||
@@ -0,0 +1,159 @@
|
||||
# Firehose
|
||||
|
||||
Real-time web data streaming API that monitors web pages and delivers matching content instantly via server-sent events (SSE). Built for competitive intelligence, brand monitoring, and news tracking without polling.
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Integration | Available | Notes |
|
||||
|-------------|-----------|-------|
|
||||
| API | ✓ | RESTful endpoints for managing rules + SSE for streaming |
|
||||
| MCP | - | Not available |
|
||||
| CLI | - | Not available |
|
||||
| SDK | - | Native AI agent skill available |
|
||||
|
||||
## Authentication
|
||||
|
||||
- **Type**: API Key
|
||||
- **Currently**: Free beta — no credit card required
|
||||
- **Get access**: Sign up at firehose.com
|
||||
|
||||
## Core Concepts
|
||||
|
||||
**Rules** — Filters that define what content to match. Uses Lucene query syntax.
|
||||
|
||||
**Stream** — A server-sent event (SSE) connection that delivers matching content in real-time as it's published on the web.
|
||||
|
||||
Instead of polling an endpoint on a schedule, you define rules once and receive a continuous stream of matches as they happen.
|
||||
|
||||
## Query Syntax (Lucene)
|
||||
|
||||
```
|
||||
# Exact phrase
|
||||
"your brand name"
|
||||
|
||||
# Field-specific
|
||||
title:tesla
|
||||
domain:reuters.com
|
||||
domain:techcrunch.com
|
||||
|
||||
# Boolean operators
|
||||
"Series A" AND (SaaS OR software)
|
||||
competitor OR "competitor name" NOT "your company"
|
||||
|
||||
# Wildcard
|
||||
market* AND funding
|
||||
|
||||
# Language filter
|
||||
language:en
|
||||
|
||||
# Date range
|
||||
publish_time:[2026-01-01 TO 2026-03-18]
|
||||
|
||||
# ML-classified categories
|
||||
category:finance
|
||||
category:technology
|
||||
```
|
||||
|
||||
## Common Agent Operations
|
||||
|
||||
### Create a monitoring rule
|
||||
|
||||
```bash
|
||||
POST https://api.firehose.com/rules
|
||||
|
||||
{
|
||||
"query": "\"your brand name\" OR \"your product name\"",
|
||||
"label": "brand-mentions"
|
||||
}
|
||||
```
|
||||
|
||||
### List active rules
|
||||
|
||||
```bash
|
||||
GET https://api.firehose.com/rules
|
||||
```
|
||||
|
||||
### Delete a rule
|
||||
|
||||
```bash
|
||||
DELETE https://api.firehose.com/rules/{rule_id}
|
||||
```
|
||||
|
||||
### Connect to the stream
|
||||
|
||||
```bash
|
||||
GET https://api.firehose.com/stream
|
||||
Authorization: Bearer {api_key}
|
||||
|
||||
# Returns server-sent events:
|
||||
# data: {"url": "...", "title": "...", "publish_time": "...", "matched_rule": "..."}
|
||||
```
|
||||
|
||||
### Example: Node.js stream consumer
|
||||
|
||||
```javascript
|
||||
import EventSource from 'eventsource';
|
||||
|
||||
const stream = new EventSource('https://api.firehose.com/stream', {
|
||||
headers: { Authorization: `Bearer ${process.env.FIREHOSE_API_KEY}` }
|
||||
});
|
||||
|
||||
stream.onmessage = (event) => {
|
||||
const item = JSON.parse(event.data);
|
||||
console.log(`[${item.matched_rule}] ${item.title} — ${item.url}`);
|
||||
};
|
||||
```
|
||||
|
||||
## Use Cases for Marketing
|
||||
|
||||
### Competitive intelligence
|
||||
Monitor competitors' press coverage, product announcements, and funding news in real-time.
|
||||
|
||||
```
|
||||
query: "CompetitorName" AND (launch OR funding OR "product update" OR partnership)
|
||||
```
|
||||
|
||||
### Brand monitoring
|
||||
Track mentions of your brand across news and web content.
|
||||
|
||||
```
|
||||
query: "YourBrand" OR "YourProductName" NOT site:yourdomain.com
|
||||
```
|
||||
|
||||
### Category / market news
|
||||
Stay current on your market without manually checking sources.
|
||||
|
||||
```
|
||||
query: category:technology AND ("no-code" OR "low-code") AND funding
|
||||
domain:techcrunch.com OR domain:venturebeat.com
|
||||
```
|
||||
|
||||
### Lead trigger monitoring
|
||||
Track signals that indicate a prospect is ready to buy (hiring, funding, tool mentions).
|
||||
|
||||
```
|
||||
query: ("hiring" OR "we're growing") AND "RevOps" AND (HubSpot OR Salesforce)
|
||||
```
|
||||
|
||||
### PR and link building
|
||||
Get alerted when publications cover topics in your space, enabling timely outreach.
|
||||
|
||||
```
|
||||
query: "best [category] tools" OR "top [category] software" AND publish_time:[now-7d TO now]
|
||||
```
|
||||
|
||||
## When to Use
|
||||
|
||||
- Real-time competitive intelligence (faster than Google Alerts)
|
||||
- Brand mention monitoring across news and web
|
||||
- Market signal tracking for sales prospecting
|
||||
- Automated content curation pipelines
|
||||
- Trigger-based workflows (new mention → Slack alert, CRM update, etc.)
|
||||
|
||||
## Relevant Skills
|
||||
|
||||
- competitor-alternatives
|
||||
- customer-research
|
||||
- content-strategy
|
||||
- cold-email
|
||||
- marketing-ideas
|
||||
@@ -0,0 +1,182 @@
|
||||
# Introw PRM
|
||||
|
||||
Partner Relationship Management platform for managing channel partners, tracking partner-sourced deals, commissions, tasks, and engagement — with built-in business review generation.
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Integration | Available | Notes |
|
||||
|-------------|-----------|-------|
|
||||
| API | - | Not available |
|
||||
| MCP | ✓ | Full read/write via Claude connector |
|
||||
| CLI | - | Not available |
|
||||
| SDK | - | Not available |
|
||||
|
||||
## Authentication
|
||||
|
||||
- **Type**: OAuth2 (via MCP connector)
|
||||
- **Setup**: Connect via Claude MCP connector — no API key management needed
|
||||
- **Scope**: All data is scoped to the authenticated organisation
|
||||
|
||||
## Common Agent Operations
|
||||
|
||||
All operations are performed via MCP tools. The following are the primary tool calls available.
|
||||
|
||||
### Search Partners
|
||||
|
||||
```
|
||||
search_partners
|
||||
dateRange: { field: "CREATED_AT" | "LAST_ACTIVITY_AT", from: "YYYY-MM-DD", to: "YYYY-MM-DD" }
|
||||
```
|
||||
|
||||
Returns: partner name/ID, contact info, tier, lifecycle stage, categories, country, last activity date.
|
||||
|
||||
### Search CRM Objects (Deals, Tickets, Leads, Companies, Contacts)
|
||||
|
||||
```
|
||||
search_crm_objects
|
||||
objectType: "DEAL" | "TICKET" | "LEAD" | "COMPANY" | "CONTACT"
|
||||
stage: "OPEN" | "WON" | "LOST"
|
||||
view: "ALL" | "DUE" | "OVERDUE" | "INACTIVE"
|
||||
rollingDateFilter: { field: "CLOSED_AT", value: "THIS_QUARTER" }
|
||||
sortBy: { property: "AMOUNT", direction: "DESC" }
|
||||
limit: 10
|
||||
```
|
||||
|
||||
Synonym mapping: Opportunity/Forecast → `DEAL`, Account → `COMPANY`, Case → `TICKET`.
|
||||
|
||||
### Search Tasks
|
||||
|
||||
```
|
||||
search_tasks
|
||||
status: "TODO" | "IN_PROGRESS" | "PENDING" | "COMPLETED" | "DONE"
|
||||
partnerId: "{partner_id}"
|
||||
```
|
||||
|
||||
### Search Commissions
|
||||
|
||||
```
|
||||
search_commissions
|
||||
partnerId: "{partner_id}"
|
||||
```
|
||||
|
||||
Returns: commission amounts, currency, payment status, associated partner and deals.
|
||||
|
||||
### Generate Business Review (QBR/MBR/WBR)
|
||||
|
||||
```
|
||||
generate_business_review
|
||||
duration: "QUARTERLY" | "MONTHLY" | "WEEKLY"
|
||||
partnerId: "{partner_id}"
|
||||
```
|
||||
|
||||
Returns: pipeline & forecast analysis, form submissions overview, mutual action plan, goal tracking, timed agenda and next steps.
|
||||
|
||||
### Search Partner Engagement
|
||||
|
||||
```
|
||||
search_partner_engagement
|
||||
partnerId: "{partner_id}"
|
||||
type: "ROOM_VISIT" | "OBJECT_SHARE" | "COMMENT" | "FORM_SUBMIT" | "TASK_CREATED" | ...
|
||||
dateRange: { from: "YYYY-MM-DD", to: "YYYY-MM-DD" }
|
||||
```
|
||||
|
||||
Returns: comments, deal updates, asset views, task events, portal visits, form submissions, announcements, quotes.
|
||||
|
||||
### Add Comment to Deal/Object
|
||||
|
||||
```
|
||||
add_comment
|
||||
comment: "Comment text"
|
||||
objectId: "{crm_object_id}"
|
||||
objectType: "DEAL" | "TICKET" | "LEAD" | "COMPANY" | "CONTACT"
|
||||
```
|
||||
|
||||
### Create or Update Tasks
|
||||
|
||||
```
|
||||
add_task
|
||||
name: "Task title"
|
||||
dueDate: "2025-02-20"
|
||||
assignedTo: "PARTNER" | "ORGANISATION"
|
||||
partnerId: "{partner_id}"
|
||||
|
||||
update_task
|
||||
taskId: 123
|
||||
status: "TODO" | "IN_PROGRESS" | "DONE"
|
||||
```
|
||||
|
||||
### Update CRM Object Properties
|
||||
|
||||
```
|
||||
update_crm_object
|
||||
objectId: "{crm_object_id}"
|
||||
objectType: "DEAL"
|
||||
propertiesToUpdate: { "amount": 50000, "stage": "Negotiation" }
|
||||
```
|
||||
|
||||
### Share Lead or Register Deal
|
||||
|
||||
Two-step flow:
|
||||
1. **Discovery**: provide `objectType` and `callToAction` to get form fields
|
||||
2. **Submit**: provide `formId` and `userProvidedData` to submit
|
||||
|
||||
```
|
||||
share_lead_or_register_deal
|
||||
objectType: "Deal"
|
||||
callToAction: "Register Deal"
|
||||
partnerId: "{partner_id}"
|
||||
```
|
||||
|
||||
## Key Metrics
|
||||
|
||||
### Partner Data
|
||||
- `id` - Partner ID
|
||||
- `name` - Partner company name
|
||||
- `championEmail` - Primary contact email
|
||||
- `tier` - Current tier level
|
||||
- `lifecycleStage` - Partner lifecycle stage
|
||||
- `categories` - Partner categories
|
||||
- `country` - Partner country
|
||||
- `lastActivityAt` - Last activity date
|
||||
|
||||
### CRM Object Data
|
||||
- `objectId` - External CRM ID
|
||||
- `objectType` - DEAL, TICKET, LEAD, COMPANY, CONTACT
|
||||
- `stage` - OPEN, WON, LOST
|
||||
- `amount` - Deal amount
|
||||
- `closeDate` - Expected close date
|
||||
|
||||
### Commission Data
|
||||
- `amount` - Commission amount
|
||||
- `currency` - Payment currency
|
||||
- `paymentStatus` - Current payment status
|
||||
- `partnerId` - Associated partner
|
||||
- `dealId` - Associated deal
|
||||
|
||||
### Engagement Data
|
||||
- `type` - Activity type (ROOM_VISIT, COMMENT, FORM_SUBMIT, etc.)
|
||||
- `partnerId` - Partner involved
|
||||
- `crmObjectId` - Related CRM object
|
||||
- `createdAt` - Activity timestamp
|
||||
|
||||
## When to Use
|
||||
|
||||
- Managing channel partner relationships and tracking partner activity
|
||||
- Reviewing partner-sourced pipeline (deals, leads, opportunities)
|
||||
- Preparing QBR/MBR/WBR meetings with automated business review generation
|
||||
- Tracking partner commissions and payouts
|
||||
- Managing mutual action plans via tasks assigned to partners or internal teams
|
||||
- Processing deal registrations and lead sharing from partners
|
||||
- Monitoring partner portal engagement and content asset views
|
||||
|
||||
## Rate Limits
|
||||
|
||||
- Rate limits managed by the MCP connector
|
||||
- All data scoped to authenticated organisation
|
||||
|
||||
## Relevant Skills
|
||||
|
||||
- revops
|
||||
- sales-enablement
|
||||
- referral-program
|
||||
- competitor-alternatives
|
||||
@@ -0,0 +1,113 @@
|
||||
# Nitrosend
|
||||
|
||||
AI-native email platform that combines transactional and marketing email in one stack, controlled entirely through AI assistants via MCP. No traditional dashboard required — build sequences, campaigns, and automations by prompting.
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Integration | Available | Notes |
|
||||
|-------------|-----------|-------|
|
||||
| API | ✓ | REST API available |
|
||||
| MCP | ✓ | Full MCP support — primary integration method |
|
||||
| CLI | - | Not available |
|
||||
| SDK | - | Use MCP or API directly |
|
||||
|
||||
## Authentication
|
||||
|
||||
- **Type**: API Key
|
||||
- **MCP Setup**: Add Nitrosend MCP server to your Claude Code / AI assistant config
|
||||
- **BYO Infrastructure**: Optionally bring your own SendGrid, Postmark, SES, or Resend keys
|
||||
- **Get access**: Sign up at nitrosend.com — free tier includes 8K emails initially, then 500/month
|
||||
|
||||
## Pricing
|
||||
|
||||
| Plan | Cost | Volume |
|
||||
|------|------|--------|
|
||||
| Free | $0 | 8K initially, then 500/mo |
|
||||
| Hobby | $20/mo | 25,000/mo |
|
||||
| Pro | $100/mo | 150,000/mo |
|
||||
| Scale | $300/mo | 500,000/mo |
|
||||
| BYO | $60/mo | Unlimited (your infrastructure) |
|
||||
|
||||
Unlimited contacts on all plans — pay per email sent, not per subscriber.
|
||||
|
||||
## What Makes It Different
|
||||
|
||||
- **AI-first**: Designed to be controlled by Claude, ChatGPT, Codex, Cursor, Gemini, Windsurf — not a human clicking through a dashboard
|
||||
- **Unified transactional + marketing**: Single platform for both, on separate infrastructure
|
||||
- **Automatic optimization**: Continuously tests subject lines, send times, and content based on engagement
|
||||
- **Auto-configured deliverability**: DKIM, SPF, DMARC, and dedicated IP warmup handled automatically
|
||||
- **Migration-friendly**: Import from Mailchimp, Klaviyo, ActiveCampaign, HubSpot
|
||||
|
||||
## Common Agent Operations (via MCP)
|
||||
|
||||
### Create an email sequence
|
||||
|
||||
```
|
||||
"Create a 5-email onboarding sequence for new SaaS trial users.
|
||||
Email 1: Welcome + what to do first (send immediately)
|
||||
Email 2: Key feature highlight (day 2)
|
||||
Email 3: Use case / success story (day 4)
|
||||
Email 4: Check-in + support offer (day 7)
|
||||
Email 5: Upgrade prompt (day 12)"
|
||||
```
|
||||
|
||||
Nitrosend builds the sequence, timing, and sends — no manual setup in a dashboard.
|
||||
|
||||
### Send a transactional email
|
||||
|
||||
```
|
||||
"Send a password reset email to user@example.com with a reset link valid for 1 hour."
|
||||
```
|
||||
|
||||
### Create a campaign
|
||||
|
||||
```
|
||||
"Create a re-engagement campaign for subscribers who haven't opened in 90 days.
|
||||
Subject line variants: [A] 'We miss you', [B] 'Still interested in [topic]?'
|
||||
Test both, send winner to remaining list after 4 hours."
|
||||
```
|
||||
|
||||
### Check sequence performance
|
||||
|
||||
```
|
||||
"Show me open rates, click rates, and unsubscribes for the onboarding sequence."
|
||||
```
|
||||
|
||||
### Import a list
|
||||
|
||||
```
|
||||
"Import this CSV of 2,000 subscribers from our Mailchimp export."
|
||||
```
|
||||
|
||||
## Deliverability Setup
|
||||
|
||||
Nitrosend handles this automatically on signup:
|
||||
- DKIM signing
|
||||
- SPF record configuration
|
||||
- DMARC policy
|
||||
- Dedicated IP provisioning (Pro+)
|
||||
- IP warmup schedule
|
||||
|
||||
For BYO plan users: bring your own SendGrid, Postmark, SES, or Resend account and Nitrosend routes through your infrastructure.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Building email sequences via AI without touching a dashboard
|
||||
- Teams already using Claude Code or other AI coding tools as their primary workflow
|
||||
- Combining transactional (password resets, receipts) and marketing (nurture, campaigns) in one place
|
||||
- Rapid sequence prototyping — describe the sequence, get it built
|
||||
- Migrating from Mailchimp/Klaviyo and wanting AI control going forward
|
||||
|
||||
## When to Use Something Else
|
||||
|
||||
- **Customer.io** — if you need complex event-based branching logic and behavioral triggers
|
||||
- **Klaviyo** — if you're in e-commerce and need deep Shopify integration
|
||||
- **Resend** — if you need transactional-only and prefer a pure API/code approach
|
||||
- **Kit** — if you're a creator or newsletter-first
|
||||
|
||||
## Relevant Skills
|
||||
|
||||
- email-sequence
|
||||
- onboarding-cro
|
||||
- churn-prevention
|
||||
- lead-magnets
|
||||
@@ -8,7 +8,7 @@ Developer-friendly transactional email service with modern API.
|
||||
|-------------|-----------|-------|
|
||||
| API | ✓ | Simple REST API for sending emails |
|
||||
| MCP | ✓ | Available via Resend MCP server |
|
||||
| CLI | - | Not available |
|
||||
| CLI | ✓ | Official Resend CLI |
|
||||
| SDK | ✓ | Official SDKs for Node.js, Python, Go, etc. |
|
||||
|
||||
## Authentication
|
||||
@@ -17,6 +17,49 @@ Developer-friendly transactional email service with modern API.
|
||||
- **Header**: `Authorization: Bearer {api_key}`
|
||||
- **Get key**: API Keys section in Resend dashboard
|
||||
|
||||
## CLI
|
||||
|
||||
### Install
|
||||
|
||||
```bash
|
||||
npm install -g resend-cli
|
||||
```
|
||||
|
||||
### Setup
|
||||
|
||||
```bash
|
||||
resend login
|
||||
# or set env var: RESEND_API_KEY=re_xxx
|
||||
```
|
||||
|
||||
### Common commands
|
||||
|
||||
```bash
|
||||
# Send a test email
|
||||
resend emails send --from hello@example.com --to user@example.com --subject "Test" --text "Hello"
|
||||
|
||||
# List recent emails
|
||||
resend emails list
|
||||
|
||||
# Get email status
|
||||
resend emails get <email_id>
|
||||
|
||||
# List domains
|
||||
resend domains list
|
||||
|
||||
# Add a domain
|
||||
resend domains create --name example.com
|
||||
|
||||
# Verify a domain
|
||||
resend domains verify <domain_id>
|
||||
|
||||
# List API keys
|
||||
resend api-keys list
|
||||
|
||||
# Create an API key
|
||||
resend api-keys create --name "Production"
|
||||
```
|
||||
|
||||
## Common Agent Operations
|
||||
|
||||
### Send email
|
||||
@@ -155,6 +198,7 @@ await resend.emails.send({
|
||||
- Receipt and notification emails
|
||||
- Developer-friendly email integration
|
||||
- React-based email templates
|
||||
- Quick CLI testing of email flows without writing code
|
||||
|
||||
## Rate Limits
|
||||
|
||||
|
||||
Reference in New Issue
Block a user