@nerdev/skillset 0.2.1

package/skills/business/startup-founder/references/marketing/customer-research.md

@@ -0,0 +1,276 @@
+---
+name: customer-research
+description: When the user wants to do, 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 cro.
+metadata:
+  version: 2.0.1
+
+# Customer Research
+
+You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with. This grounds everything from positioning to product to copy in reality rather than assumption.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, 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: when they decided to seek 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. Do not 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. Do not 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 others to see them
+
+2. **Pain Points**: what frustrates, breaks, or falls short in 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 can 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**: Do not 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, SparkToro |
+| SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups, SparkToro |
+| 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, SparkToro |
+
+**Quick decision guide:**
+- Have a product category? → Start with G2/Capterra reviews (yours + competitors)
+- Need to know where your audience spends time? → SparkToro (reveals podcasts, YouTube, subreddits, websites, social accounts)
+- 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; SparkToro competitor audience analysis
+
+### 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. Do not 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
+
+### When there are no reviews yet
+
+Early-stage products (or new categories) lack first-party review data. Do not invent personas. Walk outward through proxy sources, in order:
+
+1. **Your own differentiator**: what the product does differently defines who feels that difference most. Write the hypothesis down.
+2. **Direct competitors' reviews**: their customers describe the problem space in their words. Note what reviewers praise and what they find absent.
+3. **Comparable products on marketplaces**: Amazon/App Store reviews for adjacent solutions to the same job
+4. **Adjacent brands sharing the audience**: what else this buyer buys. Their reviews reveal the broader language and values of the buyer.
+
+Personas built this way are provisional. Tag each with its proxy source. Replace proxy evidence with first-party evidence as real reviews arrive.
+
+
+Build personas from research, not from invention. Do not create a persona until you have at least 5-10 data points from a consistent segment. Each point can come from an interview, a review, or a community post.
+
+### 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
+
+- **Do not name them cutely** ("Marketing Mary") unless your team finds it helpful. It is often a distraction.
+- **Do not average across segments**. A persona that represents everyone represents no one.
+- **Do not invent details**. If you do not 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 do not 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 is 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 did not buy)
+4. **What is your product?** (if not in the product marketing context file)
+5. **What do you want delivered?** (synthesis report, persona, quote bank, competitive intel)
+
+Do not ask all five at once. Lead with #1 and #2. Then continue with the rest as needed.
+
+
+## Related Skills
+
+| When to hand off | Skill |
+|-----------------|-------|
+| Writing copy informed by the research | `copywriting` |
+| Optimizing a page with VOC insights | `cro` |
+| Building a competitor comparison page | `competitors` |
+| Creating a churn prevention strategy from churn research | `churn-prevention` |
+| Planning paid ads informed by research | `ads` |
+| Writing cold email with research on pain or trigger | `cold-email` |
+| Translating customer research into an ICP for outbound | `prospecting` |
+| Planning content based on discovered topics | `content-strategy` |
+| Rolling research into a full marketing plan | `marketing-plan` |

package/skills/business/startup-founder/references/marketing/free-tools.md

@@ -0,0 +1,168 @@
+---
+name: free-tools
+description: When the user wants to plan, evaluate, or build a free tool for marketing purposes. Lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "is a free tool worth building," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
+metadata:
+  version: 2.0.0
+
+# Free Tool Strategy (Engineering as Marketing)
+
+You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before designing a tool strategy, understand:
+
+1. **Business Context** - What is the core product? Who is the target audience? What problems do they have?
+
+2. **Goals** - Lead generation? SEO/traffic? Brand awareness? Product education?
+
+3. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?
+
+
+## Core Principles
+
+### 1. Solve a Real Problem
+- Tool must give genuine value
+- Solves a problem your audience actually has
+- Useful even without your main product
+
+### 2. Adjacent to Core Product
+- Related to what you sell
+- Natural path from tool to product
+- Educates on problem you solve
+
+### 3. Simple and Focused
+- Does one thing well
+- Low friction to use
+- Immediate value
+
+### 4. Worth the Investment
+- Lead value × expected leads > build cost + maintenance
+
+
+## Tool Types Overview
+
+| Type | Examples | Best For |
+|------|----------|----------|
+| Calculators | ROI, savings, pricing estimators | Decisions involving numbers |
+| Generators | Templates, policies, names | Creating something quickly |
+| Analyzers | Website graders, SEO auditors | Evaluating existing work |
+| Testers | Meta tag preview, speed tests | Checking if something works |
+| Libraries | Icon sets, templates, snippets | Reference material |
+| Interactive | Tutorials, playgrounds, quizzes | Learning/understanding |
+
+**For detailed tool types and examples**: See [references/tool-types.md](references/tool-types.md)
+
+
+## Ideation Framework
+
+### Start with Pain Points
+
+1. **What problems does your audience Google?** - Search query research, common questions
+
+2. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations
+
+3. **What do they need before buying your product?** - Assessments, planning, comparisons
+
+4. **What information do they wish they had?** - Data they cannot easily access, benchmarks
+
+### Validate the Idea
+
+- **Search demand**: Is there search volume? How competitive?
+- **Uniqueness**: What exists? How can you be 10x better?
+- **Lead quality**: Does this audience match buyers?
+- **Build feasibility**: How complex? Can you scope an MVP?
+
+
+## Lead Capture Strategy
+
+### Gating Options
+
+| Approach | Pros | Cons |
+|----------|------|------|
+| Fully gated | Maximum capture | Lower usage |
+| Partially gated | Balance of both | Common pattern |
+| Ungated + optional | Maximum reach | Lower capture |
+| Ungated entirely | Pure SEO/brand | No direct leads |
+
+### Lead Capture Best Practices
+- Value exchange clear: "Get your full report"
+- Minimal friction: Email only
+- Show preview of what they will get
+- Optional: Segment by asking one qualifying question
+
+
+## SEO Considerations
+
+### Keyword Strategy
+**Tool landing page**: "[thing] calculator", "[thing] generator", "free [tool type]"
+
+**Supporting content**: "How to [use case]", "What is [concept]"
+
+### Link Building
+Free tools attract links because:
+- Genuinely useful (people reference them)
+- Unique (cannot link to just any page)
+- Shareable (social amplification)
+
+
+## Build vs. Buy
+
+### Build Custom
+When: Unique concept, core to brand, high strategic value, have dev capacity
+
+### Use No-Code Tools
+Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow
+When: Speed to market, limited dev resources, testing concept
+
+### Embed Existing
+When: Something good exists, white-label available, not core differentiator
+
+
+## MVP Scope
+
+### Minimum Viable Tool
+1. Core functionality only: does the one thing, works reliably
+2. Essential UX: clear input, obvious output, mobile works
+3. Basic lead capture: email collection, leads go somewhere useful
+
+### What to Skip Initially
+Account creation, saving results, advanced features, perfect design, every edge case
+
+
+## Evaluation Scorecard
+
+Rate each factor 1-5:
+
+| Factor | Score |
+|--------|-------|
+| Search demand exists | ___ |
+| Audience match to buyers | ___ |
+| Uniqueness vs. existing | ___ |
+| Natural path to product | ___ |
+| Build feasibility | ___ |
+| Maintenance burden (inverse) | ___ |
+| Link-building potential | ___ |
+| Share-worthiness | ___ |
+
+**25+**: Strong candidate | **15-24**: Promising | **<15**: Reconsider
+
+
+## Task-Specific Questions
+
+1. What existing tools does your audience use for workarounds?
+2. How do you currently generate leads?
+3. What technical resources are available?
+4. What is the timeline and budget?
+
+
+## Related Skills
+
+- **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates)
+- **cro**: For optimizing the landing page
+- **seo-audit**: For SEO-optimizing the tool
+- **analytics**: For measuring tool usage
+- **emails**: For nurturing leads from the tool