feat: add SparkToro as audience research tool

Add SparkToro integration guide, registry entry, and references in customer-research skill. SparkToro reveals where your ICP spends time using clickstream, search, and social data — essential for finding podcasts, YouTube channels, subreddits, and websites your audience engages with. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-01 13:50:02 -07:00
10 changed files with 13 additions and 822 deletions
@@ -1,8 +1,8 @@
 ---
 name: ab-test-setup
-description: When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
+description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
 metadata:
-  version: 1.2.0
+  version: 1.1.0
 ---

 # A/B Test Setup
@@ -229,93 +229,6 @@ Document every test with:

 ---

-## Growth Experimentation Program
-
-Individual tests are valuable. A continuous experimentation program is a compounding asset. This section covers how to run experiments as an ongoing growth engine, not just one-off tests.
-
-### The Experiment Loop
-
-```
-1. Generate hypotheses (from data, research, competitors, customer feedback)
-2. Prioritize with ICE scoring
-3. Design and run the test
-4. Analyze results with statistical rigor
-5. Promote winners to a playbook
-6. Generate new hypotheses from learnings
-→ Repeat
-```
-
-### Hypothesis Generation
-
-Feed your experiment backlog from multiple sources:
-
-| Source | What to Look For |
-|--------|-----------------|
-| Analytics | Drop-off points, low-converting pages, underperforming segments |
-| Customer research | Pain points, confusion, unmet expectations |
-| Competitor analysis | Features, messaging, or UX patterns they use that you don't |
-| Support tickets | Recurring questions or complaints about conversion flows |
-| Heatmaps/recordings | Where users hesitate, rage-click, or abandon |
-| Past experiments | "Significant loser" tests often reveal new angles to try |
-
-### ICE Prioritization
-
-Score each hypothesis 1-10 on three dimensions:
-
-| Dimension | Question |
-|-----------|----------|
-| **Impact** | If this works, how much will it move the primary metric? |
-| **Confidence** | How sure are we this will work? (Based on data, not gut.) |
-| **Ease** | How fast and cheap can we ship and measure this? |
-
-**ICE Score** = (Impact + Confidence + Ease) / 3
-
-Run highest-scoring experiments first. Re-score monthly as context changes.
-
-### Experiment Velocity
-
-Track your experimentation rate as a leading indicator of growth:
-
-| Metric | Target |
-|--------|--------|
-| Experiments launched per month | 4-8 for most teams |
-| Win rate | 20-30% is common for mature programs (sustained higher rates may indicate conservative hypotheses) |
-| Average test duration | 2-4 weeks |
-| Backlog depth | 20+ hypotheses queued |
-| Cumulative lift | Compound gains from all winners |
-
-### The Experiment Playbook
-
-When a test wins, don't just implement it — document the pattern:
-
-```
-## [Experiment Name]
-**Date**: [date]
-**Hypothesis**: [the hypothesis]
-**Sample size**: [n per variant]
-**Result**: [winner/loser/inconclusive] — [primary metric] changed by [X%] (95% CI: [range], p=[value])
-**Guardrails**: [any guardrail metrics and their outcomes]
-**Segment deltas**: [notable differences by device, segment, or cohort]
-**Why it worked/failed**: [analysis]
-**Pattern**: [the reusable insight — e.g., "social proof near pricing CTAs increases plan selection"]
-**Apply to**: [other pages/flows where this pattern might work]
-**Status**: [implemented / parked / needs follow-up test]
-```
-
-Over time, your playbook becomes a library of proven growth patterns specific to your product and audience.
-
-### Experiment Cadence
-
-**Weekly (30 min)**: Review running experiments for technical issues and guardrail metrics. Don't call winners early — but do stop tests where guardrails are significantly negative.
-
-**Bi-weekly**: Conclude completed experiments. Analyze results, update playbook, launch next experiment from backlog.
-
-**Monthly (1 hour)**: Review experiment velocity, win rate, cumulative lift. Replenish hypothesis backlog. Re-prioritize with ICE.
-
-**Quarterly**: Audit the playbook. Which patterns have been applied broadly? Which winning patterns haven't been scaled yet? What areas of the funnel are under-tested?
-
---
-
 ## Common Mistakes

 ### Test Design
@@ -2,7 +2,7 @@
 name: ai-seo
 description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup."
 metadata:
-  version: 1.2.0
+  version: 1.1.0
 ---

 # AI SEO
@@ -226,50 +226,6 @@ AI systems don't just cite your website — they cite where you appear.
 - Create YouTube content for key how-to queries
 - Answer relevant Quora questions with depth

-### Machine-Readable Files for AI Agents
-
-AI agents aren't just answering questions — they're becoming buyers. When an AI agent evaluates tools on behalf of a user, it needs structured, parseable information. If your pricing is locked in a JavaScript-rendered page or a "contact sales" wall, agents will skip you and recommend competitors whose information they can actually read.
-
-Add these machine-readable files to your site root:
-
-**`/pricing.md` or `/pricing.txt`** — Structured pricing data for AI agents
-
-```markdown
-# Pricing — [Your Product Name]
-
-## Free
- Price: $0/month
- Limits: 100 emails/month, 1 user
- Features: Basic templates, API access
-
-## Pro
- Price: $29/month (billed annually) | $35/month (billed monthly)
- Limits: 10,000 emails/month, 5 users
- Features: Custom domains, analytics, priority support
-
-## Enterprise
- Price: Custom — contact sales@example.com
- Limits: Unlimited emails, unlimited users
- Features: SSO, SLA, dedicated account manager
-```
-
-**Why this matters now:**
- AI agents increasingly compare products programmatically before a human ever visits your site
- Opaque pricing gets filtered out of AI-mediated buying journeys
- A simple markdown file is trivially parseable by any LLM — no rendering, no JavaScript, no login walls
- Same principle as `robots.txt` (for crawlers), `llms.txt` (for AI context), and `AGENTS.md` (for agent capabilities)
-
-**Best practices:**
- Use consistent units (monthly vs. annual, per-seat vs. flat)
- Include specific limits and thresholds, not just feature names
- List what's included at each tier, not just what's different
- Keep it updated — stale pricing is worse than no file
- Link to it from your sitemap and main pricing page
-
-**`/llms.txt`** — Context file for AI systems (see [llmstxt.org](https://llmstxt.org))
-
-If you don't have one yet, add an `llms.txt` that gives AI systems a quick overview of what your product does, who it's for, and links to key pages (including your pricing).
-
 ### Schema Markup for AI

 Structured data helps AI systems understand your content. Key schemas:
@@ -353,7 +309,7 @@ Monthly manual check:
 - Feature comparison tables (you vs. category, not just competitors)
 - Specific metrics ("processes 10,000 transactions/sec" not "blazing fast")
 - Customer count or social proof with numbers
- Pricing transparency (AI cites pages with visible pricing) — add a `/pricing.md` file so AI agents can parse your plans without rendering your page (see "Machine-Readable Files" above)
+- Pricing transparency (AI cites pages with visible pricing)
 - FAQ section addressing common buyer questions

 ### Blog Content
@@ -402,7 +358,6 @@ Monthly manual check:
 - **Ignoring third-party presence** — You may get more AI citations from a Wikipedia mention than from your own blog
 - **No structured data** — Schema markup gives AI systems structured context about your content
 - **Keyword stuffing** — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study)
- **Hiding pricing behind "contact sales" or JS-rendered pages** — AI agents evaluating your product on behalf of buyers can't parse what they can't read. Add a `/pricing.md` file
 - **Blocking AI bots** — If GPTBot, PerplexityBot, or ClaudeBot are blocked in robots.txt, those platforms can't cite you
 - **Generic content without data** — "We're the best" won't get cited. "Our customers see 3x improvement in [metric]" will
 - **Forgetting to monitor** — You can't improve what you don't measure. Check AI visibility monthly at minimum
@@ -1,143 +0,0 @@
---
-name: community-marketing
-description: Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."
-metadata:
-  version: 1.0.0
---
-
-# Community Marketing
-
-You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.
-
-## Before You Start
-
-**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 and only ask for information not already covered.
-
-Understand the situation (ask if not provided):
-
-1. **What is the product or brand?** — What problem does it solve, who uses it
-2. **What community platform(s) are in play?** — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
-3. **What stage is the community at?** — Pre-launch, 0–100 members, 100–1k, scaling, or established
-4. **What is the primary community goal?** — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
-5. **Who is the ideal community member?** — Role, motivation, what they hope to get from joining
-
-Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
-
---
-
-## Community Strategy Principles
-
-### Build around a shared identity, not just a product
-
-The strongest communities are built around who members *are* or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.
-
-Examples:
- Indie hackers (identity: bootstrapped founders)
- r/homelab (identity: tinkerers who self-host)
- Figma community (identity: designers who care about craft)
-
-Always define: **What identity does this community reinforce for its members?**
-
-### Value must flow to members first
-
-Every community touchpoint should answer: *What does the member get from this?*
-
- Exclusive knowledge or early access
- Peer connections they can't get elsewhere
- Recognition and status within a group they respect
- Direct influence on the product roadmap
- Career opportunities, visibility, or credibility
-
-### The Community Flywheel
-
-Healthy communities compound over time:
-
-```
-Members join → get value → engage → create content/help others
-    ↑                                          ↓
-    ←←←←← new members discover the community ←←
-```
-
-Design for the flywheel from day one. Every decision should ask: *Does this accelerate the loop or slow it down?*
-
---
-
-## Playbooks by Goal
-
-### Launching a Community from Zero
-
-1. **Recruit 20–50 founding members manually** — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
-2. **Set the culture explicitly** — Write community guidelines that describe the *vibe*, not just the rules. What does great participation look like here?
-3. **Seed conversations before launch** — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
-4. **Do things that don't scale at first** — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof.
-5. **Define your core loop** — What action do you want members to take weekly? Make it easy and reward it publicly.
-
-### Growing an Existing Community
-
-1. **Audit where members drop off** — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
-2. **Create a new member journey** — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear "start here" path.
-3. **Surface member wins publicly** — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
-4. **Run recurring community rituals** — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
-5. **Identify and invest in power users** — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.
-
-### Building a Brand Ambassador / Advocate Program
-
-1. **Identify candidates** — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
-2. **Make the ask personal** — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
-3. **Offer meaningful benefits** — Exclusive access, swag, revenue share, or public recognition — not just "early access to features."
-4. **Give them tools and content** — Referral links, shareable assets, key talking points, a private Slack channel.
-5. **Measure and iterate** — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.
-
-### Community-Led Support (Deflection + Retention)
-
-1. **Create a searchable knowledge base** from top community questions
-2. **Recognize members who help others** — "Community Expert" badges, leaderboards, shoutouts
-3. **Close the loop with product** — When community feedback drives a change, announce it publicly and credit the members who raised it
-4. **Monitor sentiment weekly** — Look for patterns in complaints or confusion before they become churn signals
-
---
-
-## Platform Selection Guide
-
-| Platform | Best For | Watch Out For |
-|----------|----------|---------------|
-| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |
-| Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |
-| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |
-| Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard |
-| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |
-| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
-
---
-
-## Community Health Metrics
-
-Track these signals weekly:
-
- **DAU/MAU ratio** — Stickiness. Above 20% is healthy for most communities.
- **New member post rate** — % of new members who post within 7 days of joining
- **Thread reply rate** — % of posts that receive at least one reply
- **Churn / lurker ratio** — Members who joined but haven't posted in 30+ days
- **Content created by non-staff** — % of posts not written by the company team
-
-**Warning signs:**
- Most posts are from the company team, not members
- Questions go unanswered for >24 hours
- The same 5 people account for 80%+ of engagement
- New members stop posting after their intro message
-
---
-
-## Output Formats
-
-Depending on what the user needs, produce one of:
-
- **Community Strategy Doc** — Platform choice, identity definition, core loop, 90-day launch plan
- **Channel Architecture** — Recommended channels/categories with purpose and posting guidelines for each
- **New Member Journey** — Welcome sequence: pinned post, DM template, first-week prompts
- **Community Ritual Calendar** — Weekly/monthly recurring events and threads
- **Ambassador Program Brief** — Criteria, benefits, outreach template, tracking plan
- **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix
-
-Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.
@@ -1,8 +1,8 @@
 ---
 name: copy-editing
-description: "When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting."
+description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting."
 metadata:
-  version: 1.3.0
+  version: 1.1.0
 ---

 # Copy Editing
@@ -256,57 +256,6 @@ For every statement, ask "Okay, so what?" If the copy doesn't answer that questi

 ---

-## Expert Panel Scoring
-
-Use this after completing the Seven Sweeps for an additional quality gate. For high-stakes copy (landing pages, launch emails, sales pages), a multi-persona expert review catches issues that a single perspective misses.
-
-### How It Works
-
-1. **Assemble 3-5 expert personas** relevant to the copy type
-2. **Each persona scores the copy 1-10** on their area of expertise
-3. **Collect specific critiques** — not just scores, but what to fix
-4. **Revise based on feedback** — address the lowest-scoring areas first
-5. **Re-score after revisions** — iterate until all personas score 7+, with an average of 8+ across the panel
-
-### Recommended Expert Panels
-
-**Landing page copy:**
- Conversion copywriter (clarity, CTA strength, benefit hierarchy)
- UX writer (scannability, cognitive load, user flow)
- Target customer persona (does this speak to me? do I trust it?)
- Brand strategist (voice consistency, positioning accuracy)
-
-**Email sequence:**
- Email marketing specialist (subject lines, open/click optimization)
- Copywriter (hooks, storytelling, persuasion)
- Spam filter analyst (deliverability red flags, trigger words)
- Target customer persona (relevance, value, unsubscribe risk)
-
-**Sales page / long-form:**
- Direct response copywriter (offer structure, objection handling, urgency)
- Skeptical buyer persona (proof gaps, trust issues, red flags)
- Editor (flow, readability, conciseness)
- SEO specialist (keyword coverage, search intent alignment)
-
-### Scoring Rubric
-
-| Score | Meaning |
-|-------|---------|
-| 9-10 | Publish-ready. No meaningful improvements. |
-| 7-8 | Strong. Minor tweaks only. |
-| 5-6 | Functional but has clear gaps. Needs another pass. |
-| 3-4 | Significant issues. Major revision needed. |
-| 1-2 | Fundamentally broken. Rethink approach. |
-
-### When to Use
-
- **Always** for launch copy, pricing pages, and high-traffic landing pages
- **Recommended** for email sequences, sales pages, and ad copy
- **Optional** for blog posts, social content, and internal docs
- **Skip** for quick updates, minor edits, and low-stakes content
-
---
-
 ## Quick-Pass Editing Checks

 Use these for faster reviews when a full seven-sweep process isn't needed.
@@ -467,15 +416,6 @@ This iterative process ensures each edit doesn't create new problems while respe
 ## References

 - [Plain English Alternatives](references/plain-english-alternatives.md): Replace complex words with simpler alternatives
- [Content Refresh](references/content-refresh.md): Full checklist, refresh vs. rewrite matrix, and cadence guide
-
---
-
-## Content Refresh Editing
-
-Copy editing isn't just for new content. Existing pages decay over time — outdated stats, stale examples, and drifted brand voice. Use the content refresh framework when traffic is declining, data is stale, or the product has changed.
-
-**For the full refresh checklist, refresh vs. rewrite decision matrix, and cadence guide**: See [references/content-refresh.md](references/content-refresh.md)

 ---

@@ -485,7 +425,6 @@ Copy editing isn't just for new content. Existing pages decay over time — outd
 2. What action should readers take?
 3. Are there specific concerns or known issues?
 4. What proof/evidence do you have available?
-5. Is this new copy or a refresh of existing content?

 ---

@@ -1,38 +0,0 @@
-# Content Refresh Editing
-
-Copy editing isn't just for new content. Existing pages and posts decay over time — outdated stats, stale examples, drifted brand voice, and missed SEO opportunities. A content refresh applies the same editing rigor to content that's already published.
-
-## When to Refresh
-
- **Traffic declining** on a page that used to perform well
- **Stats or data** are more than 12 months old
- **Product has changed** — features, pricing, or positioning no longer match
- **Competitors updated** their version of the same content
- **AI search visibility** matters — outdated content gets cited less (see ai-seo skill)
-
-## Content Refresh Checklist
-
-1. **Freshness pass** — Update all dates, stats, and examples. Replace "in 2024" with current data. Remove references to deprecated features or tools.
-2. **Accuracy pass** — Verify all claims are still true. Check that linked resources still exist. Confirm pricing and feature descriptions match current state.
-3. **Voice pass** — Does the tone match your current brand voice? Older content often reflects an earlier stage of the company.
-4. **SEO pass** — Has search intent shifted for this topic? Are there new keywords or questions to address? Add "Last updated: [date]" prominently.
-5. **Proof pass** — Can you add newer testimonials, case studies, or data points that didn't exist when this was first published?
-6. **Structure pass** — Add comparison tables, FAQ sections, or other scannable formats that make the content easier to consume.
-
-## Refresh vs. Rewrite
-
-| Signal | Action |
-|--------|--------|
-| Core message still valid, details outdated | Refresh (update facts, stats, examples) |
-| Brand voice has evolved significantly | Refresh + voice rewrite |
-| Topic angle or audience has shifted | Full rewrite |
-| Page structure doesn't match current search intent | Full rewrite |
-| Just needs updated stats and links | Light refresh |
-
-## Refresh Cadence
-
- **Pricing and product pages**: Every quarter, or when pricing/features change
- **High-traffic blog posts**: Every 6 months
- **Comparison and alternatives pages**: Every 3-6 months (competitors change fast)
- **Evergreen guides**: Annually, unless traffic drops sooner
- **Low-traffic pages**: Only when traffic data suggests an opportunity
@@ -2,7 +2,7 @@
 name: social-content
 description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurposing, or scheduling task. For broader content strategy, see content-strategy."
 metadata:
-  version: 1.2.0
+  version: 1.1.0
 ---

 # Social Content
@@ -49,7 +49,6 @@ Gather this context (ask if not provided):
 | Facebook | Communities, local businesses | 1-2x/day | Groups, native video |

 **For detailed platform strategies**: See [references/platforms.md](references/platforms.md)
-**For hashtag limits and character counts**: See [references/platform-limits.md](references/platform-limits.md)

 ---

@@ -108,7 +107,7 @@ The first line determines whether anyone reads the rest.

 ## Content Repurposing System

-Turn one piece of content into many. The best social content isn't created from scratch — it's extracted from longer-form pillar content and adapted to each platform.
+Turn one piece of content into many:

 ### Blog Post → Social Content

@@ -120,61 +119,13 @@ Turn one piece of content into many. The best social content isn't created from
 | Instagram | Carousel with visuals |
 | Instagram | Reel summarizing the post |

-### Podcast / Video → Social Content
-
-Extract "content atoms" — self-contained moments from any long-form content that work on their own:
-
-| Atom Type | What to Look For | Best Platform |
-|-----------|-----------------|---------------|
-| Quotable moment | A bold claim, hot take, or memorable line (15-60 sec) | Twitter/X, LinkedIn, TikTok |
-| Story arc | A complete mini-story with setup, conflict, resolution (60-90 sec) | Instagram Reels, TikTok, YouTube Shorts |
-| Tactical tip | A specific how-to or framework explained clearly (30-60 sec) | LinkedIn, YouTube Shorts |
-| Controversial take | A contrarian opinion that sparks debate | Twitter/X, LinkedIn |
-| Data/stat callout | A surprising number or research finding | LinkedIn carousel, Twitter/X |
-| Behind-the-scenes | Authentic, unpolished moments | Instagram Stories, TikTok |
-
-**Podcast repurposing workflow:**
-1. **Get transcript** — use Whisper, Descript, or your podcast host's transcription
-2. **Mark timestamps** — flag the 5-10 best moments while listening or scanning transcript
-3. **Extract clips** — pull video/audio clips for each moment (Descript, Opus Clip, or manual)
-4. **Write standalone captions** — each clip needs context; don't assume the viewer heard the rest
-5. **Add subtitles** — most social video is watched without sound
-6. **Schedule across 1-2 weeks** — spread a single episode across multiple posts
-
-**Per episode, aim for:**
- 3-5 short video clips or audiograms (15-60 sec) for Reels/TikTok/Shorts
- 1-2 LinkedIn text posts from key insights
- 1 Twitter/X thread of takeaways
- 1 carousel summarizing the main framework or list
- 1 newsletter section or blog post from the best segment
-
-### Webinar / Live Event → Social Content
-
-| Extract | Format |
-|---------|--------|
-| Key slides with commentary | LinkedIn carousel |
-| Q&A highlights | Twitter/X thread |
-| Speaker quotes | Quote graphics for Instagram/LinkedIn |
-| Audience reactions/poll results | Engagement posts |
-| Full recording → short clips | Reels, TikTok, Shorts |
-
-### Newsletter → Social Content
-
-| Extract | Format |
-|---------|--------|
-| Main insight | LinkedIn post |
-| Curated links with commentary | Twitter/X thread |
-| Data or stat | Quote graphic |
-| Hot take or opinion | Twitter/X post, LinkedIn |
-
 ### Repurposing Workflow

-1. **Create pillar content** (blog, video, podcast, webinar, newsletter)
-2. **Extract content atoms** (5-10 per piece — quotes, stories, tips, data)
-3. **Adapt to each platform** (format, length, and tone)
-4. **Write standalone captions** (each post must work without context)
-5. **Schedule across the week** (spread distribution, don't dump all at once)
-6. **Update and reshare** (evergreen content can repeat every 3-6 months)
+1. **Create pillar content** (blog, video, podcast)
+2. **Extract key insights** (3-5 per piece)
+3. **Adapt to each platform** (format and tone)
+4. **Schedule across the week** (spread distribution)
+5. **Update and reshare** (evergreen content can repeat)

 ---

@@ -1,110 +0,0 @@
-# Platform Limits Reference
-
-Quick reference for hashtag limits, character counts, and visible text thresholds on each major social platform.
-
---
-
-## Instagram
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | 5 (official limit) |
-| Recommended hashtags | 3 – 5 |
-| Max caption chars | 2,200 |
-| Visible before "more" | ~125 chars |
-
---
-
-## Facebook
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | No official limit |
-| Recommended hashtags | 1 – 2 |
-| Max post chars | 63,206 |
-| Ideal for engagement | 40 – 80 chars |
-
---
-
-## TikTok
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | 5 (since August 2025) |
-| Recommended hashtags | 3 – 5 |
-| Max caption chars | 4,000 |
-| Visible before "more" | ~150 chars |
-
---
-
-## LinkedIn
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | No official limit |
-| Recommended hashtags | 3 – 5 |
-| Max post chars | 3,000 |
-| Visible before "more" | ~210 chars |
-
---
-
-## Twitter/X
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | No official limit |
-| Recommended hashtags | 1 – 2 |
-| Max tweet chars | 280 (standard) / 25,000 (Premium+) |
-| Visible before "more" | Full tweet (280 standard) |
-
---
-
-## YouTube
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | 15 (exceeding this causes YouTube to ignore ALL hashtags) |
-| Recommended hashtags | 3 – 5 |
-| Max title chars | 100 (visible before truncation: ~70) |
-| Max description chars | 5,000 |
-| Visible before "Show more" | ~100 chars |
-
-> The first 3 hashtags in the description automatically appear above the title as clickable links. For Shorts, use 1 – 5 hashtags.
-
---
-
-## Pinterest
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | 20 per pin |
-| Recommended hashtags | 2 – 5 |
-| Max pin title chars | 100 |
-| Max description chars | 500 |
-| Visible before "More" | ~50 chars (desktop) |
-
-> Pinterest has deprioritized hashtags. Focus on keywords as natural sentences within the description for better SEO instead of relying on hashtags.
-
---
-
-## Threads (Meta)
-
-| Element | Limit |
-|---------|-------|
-| Max hashtags | 1 per post (topic tag) |
-| Recommended hashtags | 1 |
-| Max post chars | 500 |
-| Max with text attachment | 10,500 (500 + 10,000 expandable) |
-| Visible without expanding | First ~1 – 2 lines |
-
-> Threads limits topic tags to one per post. The platform is not hashtag-driven — the algorithm prioritizes content from followed accounts mixed with recommendations.
-
---
-
-## Usage Tips
-
- **Hashtags count against character limits** on all platforms
- **Front-load your message** before the "more" truncation point
- On Instagram and TikTok, fewer hashtags now outperform hashtag-stuffing
- On LinkedIn, hashtags at the end of the post perform better than inline
- On Facebook, hashtags have minimal impact on reach — use sparingly
@@ -75,8 +75,6 @@ Quick reference for AI agents to discover tool capabilities and integration meth
 | similarweb | Competitive Intelligence | ✓ | - | [✓](clis/similarweb.js) | - | [similarweb.md](integrations/similarweb.md) |
 | firehose | Competitive Intelligence | ✓ | - | - | - | [firehose.md](integrations/firehose.md) |
 | sparktoro | Audience Research | - | - | - | - | [sparktoro.md](integrations/sparktoro.md) |
-| rb2b | Visitor Identification | ✓ | - | - | - | [rb2b.md](integrations/rb2b.md) |
-| gong | Revenue Intelligence | ✓ | - | - | - | [gong.md](integrations/gong.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) |
@@ -353,26 +351,6 @@ Audience intelligence and behavioral research tools.

 **Agent recommendation**: SparkToro for discovering where your ICP spends time — what they read, watch, listen to, follow, and search for. Essential for customer research, content strategy, and media buying decisions.

-### Visitor Identification
-
-Website visitor de-anonymization for B2B sales and marketing.
-
-| Tool | Best For | Notes |
-|------|----------|-------|
-| **rb2b** | Person-level visitor ID, intent signals | LinkedIn profiles, emails, page-level data |
-
-**Agent recommendation**: RB2B for identifying anonymous B2B website visitors and routing high-intent visitors to outreach tools. Pairs well with Clay for enrichment and Instantly/Lemlist for cold email.
-
-### Revenue Intelligence
-
-Sales conversation analytics, call recording, and deal intelligence.
-
-| Tool | Best For | Notes |
-|------|----------|-------|
-| **gong** | Call recording, transcript analysis, deal insights | REST API, 10k API calls/day |
-
-**Agent recommendation**: Gong for mining sales call transcripts for customer research, competitive intelligence, and coaching insights. Essential for revenue attribution and win/loss analysis.
-
 ### AI Content

 AI-powered content generation and optimization platforms.
@@ -1,144 +0,0 @@
-# Gong
-
-Revenue intelligence platform that records, transcribes, and analyzes sales conversations (calls, video meetings, emails) to surface deal insights, coaching opportunities, and competitive intelligence.
-
-## Capabilities
-
-| Integration | Available | Notes |
-|-------------|-----------|-------|
-| API | ✓ | REST API, Basic Auth or OAuth2 |
-| MCP | - | Not available |
-| CLI | - | Not available |
-| SDK | - | REST API only; community Python client via dltHub |
-
-## Authentication
-
- **Type**: Basic Auth (Access Key + Secret) or OAuth2 for published apps
- **Get key**: Admin-only — Settings > API at https://app.gong.io
- **Base URL**: Tenant-specific — retrieve from your Gong API settings (typically `https://{tenant}.api.gong.io/v2/`)
- **Docs**: https://help.gong.io/docs/what-the-gong-api-provides
-
-## API Endpoints
-
-Most Gong API endpoints use **POST** with JSON request bodies for filtering. Check the [official API docs](https://gong.app.gong.io/settings/api/documentation) for current endpoint availability.
-
-### Calls
-
-```bash
-# List calls (with date/user filters)
-POST /v2/calls/extensive
-
-# Get call transcripts (batch, by call IDs)
-POST /v2/calls/transcript
-```
-
-### Users & Stats
-
-```bash
-# List users
-GET /v2/users
-
-# Get activity stats (talk ratio, questions asked, longest monologue)
-POST /v2/stats/activity/day-by-day
-```
-
-### Engagement Flows
-
-```bash
-# List flows
-GET /v2/flows
-
-# Get flow analytics
-GET /v2/flows/{id}/analytics
-```
-
-## Key Data Points
-
-### Per Call
- Full transcript with speaker labels and timestamps
- Talk-to-listen ratio per participant
- Topics discussed (auto-detected)
- Questions asked (count and content)
- Longest monologue duration
- Next steps mentioned
- Competitor mentions
- Pricing discussions flagged
-
-### Per Deal
- All associated calls and emails
- Deal stage progression
- Risk signals (gone dark, competitor mentioned, champion left)
- Engagement score
-
-### Per Rep
- Talk ratio trends
- Question frequency
- Topic coverage vs. playbook
- Win rate correlation with behaviors
-
-## Common Agent Operations
-
-### Extract Competitive Intelligence from Calls
-
-1. Query calls mentioning competitor names
-2. Extract: objections raised, features compared, pricing discussed
-3. Synthesize into competitive battlecard updates
-4. Track competitor mention frequency over time
-
-### Mine Calls for Customer Research
-
-1. Pull transcripts from recent won/lost deals
-2. Extract: pain points, trigger events, decision criteria, language used
-3. Feed into persona building and messaging work
-4. Identify recurring objections for sales enablement
-
-### Revenue Attribution
-
-1. Pull call data alongside CRM deal data
-2. Map which content/pages were discussed in winning deals
-3. Identify which talking points correlate with closed-won
-4. Build content-to-revenue attribution reports
-
-### Rep Coaching Insights
-
-1. Compare top performer call patterns vs. team average
-2. Identify: talk ratio, question frequency, topic coverage gaps
-3. Surface specific call moments for coaching review
-4. Track improvement over time
-
-## Rate Limits
-
- 3 API calls per second
- 10,000 API calls per day
- Pagination required for large result sets
-
-## When to Use
-
- Mining sales call transcripts for customer research and VOC data
- Extracting competitive intelligence from prospect conversations
- Building revenue attribution models (content → deal influence)
- Analyzing win/loss patterns across deal transcripts
- Coaching sales reps based on conversation analytics
- Identifying common objections and buying signals
-
-## Limitations
-
- API access requires admin credentials
- Transcript quality depends on call audio quality
- Rate limits (10k/day) may constrain large-scale analysis
- Pricing is enterprise-level (not publicly listed, typically $100+/user/month)
- Requires team adoption — records calls via integrations, but also supports uploading calls from non-integrated telephony systems
-
-## Relevant Skills
-
- customer-research
- sales-enablement
- competitor-alternatives
- revops
- cold-email
-
-## Sources
-
- [Gong API overview](https://help.gong.io/docs/what-the-gong-api-provides)
- [Gong API documentation](https://gong.app.gong.io/settings/api/documentation)
- [Call upload support](https://help.gong.io/docs/uploading-calls-from-a-non-integrated-telephony-system)
@@ -1,110 +0,0 @@
-# RB2B
-
-Website visitor identification platform that de-anonymizes B2B website traffic, revealing the individual people visiting your site with LinkedIn profiles, emails, and company data.
-
-## Capabilities
-
-| Integration | Available | Notes |
-|-------------|-----------|-------|
-| API | Limited | API Partner Program (separate from standard app) |
-| MCP | - | Not available |
-| CLI | - | Not available |
-| SDK | - | Not available |
-
-Most teams use RB2B via its native integrations (Slack, CRM push, Zapier, webhooks) rather than direct API access. A separate [API Partner Program](https://www.rb2b.com/apis) exists for programmatic access.
-
-## Authentication
-
- **Type**: Native integrations (no API key needed for standard use)
- **API Partner Program**: Separate credentials via https://www.rb2b.com/apis
- **Free tier**: Limited credits/month with Slack alerts
-
-## Pricing Tiers
-
-Pricing changes frequently — verify at https://www.rb2b.com/pricing.
-
-| Plan | Approx. Price | Key Features |
-|------|--------------|-------------|
-| Free | $0 | Limited credits, Slack alerts, LinkedIn profiles |
-| Starter | ~$79/mo | Person-level ID, basic integrations |
-| Pro | ~$129-349/mo | CSV export, CRM push, validated emails |
-| Pro+ | ~$299+/mo | All integrations, higher credit volume |
-
-## Key Integrations
-
-RB2B pushes identified visitor data to 50+ tools:
- **CRM**: Salesforce, HubSpot
- **Outreach**: Instantly, HeyReach, Lemlist
- **Enrichment**: Clay, Apollo, Clearbit
- **Automation**: Zapier, Make
- **Alerts**: Slack (real-time notifications)
-
-## What RB2B Reveals Per Visitor
-
- Full name and LinkedIn profile URL
- Job title and company
- Validated business email (Pro+)
- Pages visited and visit duration
- Number of visits and return frequency
- Company data (size, industry, location)
-
-## Common Agent Operations
-
-### Real-Time Visitor Alerts
-
-Configure Slack alerts for high-intent visitors:
- Visitors who hit pricing page
- Visitors who return 3+ times
- Visitors from target account list
- Visitors matching ICP job titles
-
-### Visitor-to-Outreach Pipeline
-
-1. RB2B identifies visitor with LinkedIn + email
-2. Filter by ICP criteria (title, company size, pages visited)
-3. Route to outreach tool (Instantly, Lemlist) or CRM (HubSpot, Salesforce)
-4. Trigger personalized cold email referencing pages they visited
-
-### Intent Scoring
-
-Score visitors by behavior signals:
- **High intent**: Pricing page, demo page, comparison pages, 3+ visits
- **Medium intent**: Feature pages, case studies, 2 visits
- **Low intent**: Blog only, single visit, bounced quickly
-
-### Suppression Lists
-
-Prevent outreach to:
- Existing customers (match against CRM)
- Active deals in pipeline
- Competitors and agencies
- Recently contacted prospects
-
-## When to Use
-
- Identifying anonymous website visitors for sales outreach
- Building ABM (account-based marketing) target lists from site traffic
- Understanding which companies are researching your product
- Triggering personalized outreach based on page-level intent signals
- Feeding enrichment tools (Clay, Apollo) with warm visitor data
-
-## Limitations
-
- Person-level identification works best for US B2B traffic
- Not all visitors can be identified (typical match rates: 15-30%)
- Requires sufficient website traffic to be cost-effective
- Privacy considerations — ensure compliance with applicable regulations
- Free tier limited to Slack alerts (no CRM push or email export)
-
-## Relevant Skills
-
- cold-email
- revops
- customer-research
- paid-ads
-
-## Sources
-
- [RB2B pricing](https://www.rb2b.com/pricing)
- [RB2B plans comparison](https://support.rb2b.com/en/articles/9173659-rb2b-plans-side-by-side-comparisons)
- [RB2B API Partner Program](https://support.rb2b.com/en/articles/12579420-rb2b-apis-rb2b-s-api-partner-program)