@opendirectory.dev/skills 0.1.38 → 0.1.40

package/skills/where-your-customer-lives/evals/evals.json

@@ -0,0 +1,108 @@
+[
+  {
+    "id": "eval_001",
+    "name": "Developer tools ICP (devops) -- full pipeline",
+    "input": {
+      "product": "Observability platform that replaces Datadog for teams under 200 engineers",
+      "icp_role": "DevOps engineers at mid-size companies",
+      "icp_pain": "Datadog bill growing faster than team size",
+      "category": "devops observability monitoring",
+      "competitors": ["Datadog", "New Relic", "Grafana"]
+    },
+    "expected": {
+      "min_channels": 8,
+      "required_channel_types": ["reddit", "newsletter", "conference"],
+      "top_channel_must_be_type": "reddit",
+      "top_channel_must_contain": "devops",
+      "reddit_channels_min": 3,
+      "icp_signals_min": 10,
+      "competitor_layer_ran": true,
+      "entry_tactic_must_not_contain": "post about your product",
+      "banned_words": ["powerful", "robust", "seamless", "innovative", "game-changing", "streamline", "leverage", "transform", "revolutionize"],
+      "no_em_dashes": true
+    },
+    "notes": "Full pipeline. r/devops should be #1 with high icp_signal_count. Datadog/Grafana competitor mentions should boost channels where those tools are discussed. Newsletter like 'DevOps Weekly' should appear. KubeCon or similar conference expected."
+  },
+  {
+    "id": "eval_002",
+    "name": "B2B sales tool ICP -- competitor layer fires",
+    "input": {
+      "product": "AI-powered outbound sales tool for B2B SaaS companies",
+      "icp_role": "sales leaders at B2B SaaS startups",
+      "icp_pain": "outbound sequences get ignored, response rates under 1%",
+      "category": "B2B sales outbound CRM",
+      "competitors": ["Clay", "Apollo", "HubSpot", "Outreach"]
+    },
+    "expected": {
+      "min_channels": 6,
+      "required_channel_types": ["reddit", "linkedin_group"],
+      "competitor_layer_ran": true,
+      "competitor_channels_present": true,
+      "channels_differ_from_eval_001": true,
+      "reddit_channels_must_not_contain": "devops",
+      "entry_tactic_must_not_contain": "post about your product",
+      "no_em_dashes": true
+    },
+    "notes": "Competitor layer should fire strongly on Clay/Apollo/HubSpot. LinkedIn groups should appear (sales leaders use LinkedIn more than Reddit). Channel list should differ substantially from eval_001 -- different ICP produces different channels."
+  },
+  {
+    "id": "eval_003",
+    "name": "Consumer app ICP -- different channel mix",
+    "input": {
+      "product": "Personal finance app for people tracking subscriptions",
+      "icp_role": "people frustrated by unknown monthly charges",
+      "icp_pain": "losing money on subscriptions I forgot about",
+      "category": "personal finance consumer app subscriptions",
+      "competitors": ["Rocket Money", "Trim", "PocketGuard"]
+    },
+    "expected": {
+      "min_channels": 5,
+      "required_channel_types": ["reddit", "youtube"],
+      "must_not_include_type": "linkedin_group",
+      "channels_differ_from_eval_001": true,
+      "channels_differ_from_eval_002": true,
+      "no_em_dashes": true
+    },
+    "notes": "Consumer ICP should surface r/personalfinance, YouTube channels, possibly Discord. LinkedIn groups are wrong for this ICP -- flag if they appear. The channel mix should look nothing like devops or sales tool results."
+  },
+  {
+    "id": "eval_004",
+    "name": "Very niche ICP -- thin data handled honestly",
+    "input": {
+      "product": "Compliance automation for small community banks",
+      "icp_role": "compliance officers at community banks under $500M assets",
+      "icp_pain": "BSA/AML reporting takes 3 days per quarter",
+      "category": "community bank compliance BSA AML regulatory",
+      "competitors": []
+    },
+    "expected": {
+      "thin_data_acknowledged": true,
+      "min_channels": 2,
+      "no_fabricated_member_counts": true,
+      "competitor_layer_ran": false,
+      "report_must_say": "member count not found",
+      "no_em_dashes": true
+    },
+    "notes": "This ICP is niche enough that Reddit signal count will be low. Script should still try DuckDuckGo for conference/newsletter/association channels. Output must not fabricate community sizes. If member count unavailable, must say 'member count not found' not an estimated number."
+  },
+  {
+    "id": "eval_005",
+    "name": "No competitors provided -- competitor layer skipped cleanly",
+    "input": {
+      "product": "Email deliverability monitoring for SaaS companies",
+      "icp_role": "growth engineers at B2B SaaS",
+      "icp_pain": "transactional emails landing in spam without warning",
+      "category": "email deliverability SMTP SaaS",
+      "competitors": []
+    },
+    "expected": {
+      "competitor_layer_ran": false,
+      "output_notes_competitor_layer_skipped": true,
+      "min_channels": 4,
+      "required_channel_types": ["reddit"],
+      "no_em_dashes": true,
+      "output_recommends_adding_competitors": true
+    },
+    "notes": "Competitor layer should be cleanly skipped with no errors. Output should note that competitor layer was not run and suggest adding competitors (MXroute, Mailgun, Postmark, etc.) for richer results. Signal-trace should still produce valid Reddit channels."
+  }
+]

package/skills/where-your-customer-lives/references/channel-types.md

@@ -0,0 +1,147 @@
+# Channel Types Reference
+
+Seven channel types discovered by this skill. Each type has a different discovery method, metadata available, and scoring characteristics.
+
+---
+
+## 1. Reddit
+
+**Discovery method:** Signal-trace (primary) -- search Reddit for ICP pain posts, extract which subreddits those posts came from. Subreddits with the most ICP posts = highest-confidence channels.
+
+**Metadata available:**
+- `subscribers` -- total member count from `r/{sub}/about.json`
+- `active_user_count` -- users online right now (proxy for posts/day activity)
+- `public_description` -- subreddit purpose from about.json
+- `icp_signal_count` -- posts matching ICP queries found in this subreddit (counted by script)
+- `competitor_mentions` -- how many ICP posts also mention a competitor product
+
+**Scoring notes:**
+- Highest-confidence channel type because signals are traced from actual ICP posts
+- active_user_count / 100 used as activity_score (capped at 30)
+- Open entry -- no penalty
+
+**Evidence standard:** Every Reddit channel must have at least 1 evidence_post from the raw data. If icp_signal_count = 0, the channel was found via competitor layer, not signal_trace -- note this distinction.
+
+---
+
+## 2. Slack
+
+**Discovery method:** DuckDuckGo search -- `"{category} slack community"` and `"{icp_role} slack workspace"`
+
+**Metadata available:**
+- Member count from search snippets (e.g. "Join 12,000+ DevOps professionals")
+- URL from search result (often a landing page or Slack direct link)
+
+**Scoring notes:**
+- No icp_signal_count from script (0 unless competitor layer fires)
+- Member count drives size component of score
+- activity_score defaults to 5 (DDG doesn't expose post frequency)
+- Most Slack communities are open-invite (via website form) -- no penalty
+
+**Evidence standard:** Channel name and URL must come from DDG results. Member count from snippet or 0 -- never estimated. Note if invite-required (entry_type = "invite-only", -10 penalty).
+
+---
+
+## 3. Discord
+
+**Discovery method:** DuckDuckGo search -- `"{icp_role} discord server"` and `"{category} discord community"`
+
+**Metadata available:**
+- Member count from DDG snippets
+- Invite link or website from search result
+
+**Scoring notes:**
+- Same scoring structure as Slack
+- Many Discord servers are invite-only -- check the URL for discord.gg invite links
+- Gaming/consumer ICPs: Discord scores higher than Slack
+
+**Evidence standard:** Same as Slack. If invite link expires, note as "invite may expire -- check current link."
+
+---
+
+## 4. Newsletter
+
+**Discovery method:** DuckDuckGo search -- `"{category} newsletter weekly"` and HN "Ask HN: what newsletters do you read about {category}"
+
+**Metadata available:**
+- Subscriber count from DDG snippets (less reliable than Reddit API)
+- Frequency (weekly/monthly) from snippet
+- Sponsorship availability often mentioned in description
+
+**Scoring notes:**
+- Newsletters score well for reach but entry is typically paid sponsorship or content contribution
+- entry_type = "paid" (-20 penalty) if snippet mentions "sponsor" or "advertising"
+- Subscriber count varies widely -- treat as directional
+
+**Evidence standard:** Newsletter name must appear in DDG results. Subscriber count from snippet or "subscriber count not found."
+
+---
+
+## 5. Podcast
+
+**Discovery method:** DuckDuckGo search -- `"{icp_role} podcast"` and `"best {category} podcast"`
+
+**Metadata available:**
+- Episode count from snippet
+- Frequency (weekly/biweekly) from snippet
+- Guest appearances as entry point
+
+**Scoring notes:**
+- Podcasts score lower than Reddit because reach per episode is smaller and entry requires production effort
+- Guest appearances are the primary entry tactic -- not "listening"
+- activity_score defaults to 5
+
+**Evidence standard:** Podcast name and URL from DDG results. Episode count from snippet or omitted.
+
+---
+
+## 6. Conference
+
+**Discovery method:** DuckDuckGo search -- `"{category} conference summit 2025"` and `"{icp_role} conference annual"`
+
+**Metadata available:**
+- Attendee count from snippet
+- Date and location from snippet
+- Ticket price category (free/paid) from snippet
+
+**Scoring notes:**
+- Conferences have the highest ICP density per touchpoint but low accessibility
+- entry_type = "paid" (-20 penalty) for paid conferences
+- Sponsorship is a separate entry path (expensive) -- not the primary tactic
+- Hallway conversations and evening events > sponsored sessions for early-stage founders
+
+**Evidence standard:** Conference name from DDG results. Attendee count from snippet or "attendee count not found." Check for 2025/2026 dates -- exclude past conferences.
+
+---
+
+## 7. YouTube Channel
+
+**Discovery method:** DuckDuckGo search -- `"best {category} youtube channel"` and `"{icp_role} tutorial youtube"`
+
+**Metadata available:**
+- Subscriber count from DDG snippets
+- Channel name and URL
+
+**Scoring notes:**
+- YouTube channels are consumption channels, not community channels
+- Entry tactic = guest appearance or collaboration, not commenting
+- High subscriber counts inflate scores -- cap with size component (log scale)
+
+**Evidence standard:** Channel name and subscriber count from DDG results.
+
+---
+
+## 8. Forum (catch-all)
+
+**Discovery method:** Competitor layer DuckDuckGo search -- `"{competitor} community forum users"`
+
+**Metadata available:**
+- URL from DDG results
+- Description from snippet
+
+**Scoring notes:**
+- Competitor forums = high intent ICP (actively evaluating alternatives)
+- icp_signal_count = 0, but competitor_mentions bumped to 3 as proxy
+- Includes HN (scored separately with actual signal count)
+
+**Evidence standard:** URL and name from DDG results or direct knowledge (HN is always valid).

package/skills/where-your-customer-lives/references/entry-tactics.md

@@ -0,0 +1,179 @@
+# Entry Tactic Templates by Channel Type
+
+These are starting templates. The AI must customize each tactic for the specific community, using evidence posts and the subreddit description to identify actual thread types, posting norms, and community rules.
+
+---
+
+## Reddit
+
+**Template structure:** Thread type + content format + community norm + what to avoid.
+
+**Thread types to look for:**
+- Weekly/monthly megathreads: "What are you working on?", "Tools & Projects", "Self-Promotion Saturday", "Feedback Friday", "Show HN" equivalent threads
+- Recurring "Help" or "Question" flairs
+- Monthly community surveys or AMAs
+
+**Content formats that get upvotes:**
+- Technical post-mortems: "We did X, it failed, here is why, here is what we changed"
+- Comparison breakdowns: "We evaluated 5 tools for {pain} -- here is our matrix"
+- Problem-framing posts: "Anyone else dealing with {pain}? We found three approaches..."
+- Open questions with context: "We are building {thing}. Ran into {problem}. What would you do?"
+
+**Universal anti-patterns for Reddit:**
+- Posting product links in non-promotional threads (auto-removed in most subreddits)
+- Asking "what tools do you use?" without a specific problem context (flagged as market research farming)
+- First post is a product announcement (zero karma = instant distrust)
+- Responding to competitor complaints with "you should try our product"
+
+**Example (r/devops):** "Find the weekly 'What are you working on?' thread (pinned every Monday by automoderator). Reply with a 3-sentence technical challenge: what you were trying to do, what broke, and what you tried. No product mention. Build 3-4 posts of karma before posting standalone content."
+
+---
+
+## Slack
+
+**Template structure:** Specific channel within the workspace + conversation format + timing.
+
+**Entry sequence:**
+1. Join via website form or invite link
+2. Introduce yourself in #introductions with: role, company, one technical problem you are currently solving
+3. Spend 1-2 weeks answering questions in relevant channels before posting about your product
+4. Post in #show-and-tell or #tools channels after establishing presence
+
+**Content formats that get engagement:**
+- Asking a specific technical question (signals you are a practitioner, not a vendor)
+- Sharing a non-promotional resource (article, script, guide)
+- Answering someone else's question in detail
+
+**Anti-patterns:**
+- DM-ing members directly to pitch (almost always a ban)
+- Cross-posting the same message in multiple channels
+- Posting product links without being asked
+
+---
+
+## Discord
+
+**Template structure:** Server channel + role assignment + gradual contribution.
+
+**Entry sequence:**
+1. Join via invite link
+2. Complete any onboarding (many servers require role selection or intro post)
+3. Post in #introductions: role + what you build + one specific problem
+4. Contribute in technical channels for 1-2 weeks before mentioning your product
+
+**Content formats:**
+- Voice channels / stage events: joining community calls builds trust faster than text
+- Sharing tools, scripts, or resources in #resources or #tools channels
+- Participating in community challenges or hackathons
+
+**Anti-patterns:**
+- Posting in #general with a promotional message on day 1
+- Spamming invite links in other servers
+- Pinging @everyone or using excessive notifications
+
+---
+
+## Newsletter
+
+**Template structure:** Contribution type + relationship path + timeline.
+
+**Entry approaches (ranked by accessibility):**
+1. **Sponsor:** Most newsletters have a sponsor slot. Relevant for products with budget.
+2. **Guest article:** Pitch a technical deep-dive or case study. Must be non-promotional and provide genuine value.
+3. **Mention-worthy news:** Share something newsworthy (open-source release, research finding, benchmark) that the editor would want to share organically.
+
+**Content formats that get accepted:**
+- Data-backed insights ("We analyzed 500 incidents -- here is what caused the most downtime")
+- Practical guides with code/config examples
+- Contrarian takes with evidence
+
+**Anti-patterns:**
+- Pitching a sponsored post that reads like a product description
+- Sending a cold pitch with no context about why your content fits the audience
+- Sending the same pitch to 10 newsletters at once (editors talk to each other)
+
+---
+
+## Podcast
+
+**Template structure:** Guest pitch angle + pre-qualification + follow-up.
+
+**Entry approach:**
+1. Listen to 3-5 episodes to identify the host's specific framing and guest style
+2. Pitch as a practitioner, not a founder: "I am a DevOps engineer who spent 2 years solving X. I have specific opinions about Y that your audience would disagree with."
+3. Lead with controversy or counter-intuition, not company credentials
+
+**Pitch elements that work:**
+- A specific claim the audience will want to debate
+- A technical story with a surprising outcome
+- A data-backed finding that contradicts conventional wisdom
+
+**Anti-patterns:**
+- "I am the founder of X and would love to share our story" (generic, rejected)
+- Pitching via mass email tools (gets filtered as spam)
+- Offering to pay to be a guest (podcast integrity signal to hosts)
+
+---
+
+## Conference
+
+**Template structure:** Specific engagement context + entry level + timeline.
+
+**Entry approaches (ranked by cost/effort):**
+1. **Attend + hallway conversations:** Cheapest. Identify 3-5 specific sessions where your ICP will concentrate. Prepare a 30-second context-setting intro. Bring nothing promotional.
+2. **Submit a talk:** Submit 6+ months before the conference. Frame as a practitioner talk, not a product demo. "How we cut alert fatigue by 70% (and what didn't work)" beats "Introducing X."
+3. **Sponsor a workshop or unconference slot:** Moderate cost. Gives you a captive audience for 45 minutes without a hard pitch.
+4. **Conference sponsorship:** Expensive. Only viable if the conference matches your ICP exactly.
+
+**Hallway conversation format:**
+- Ask what they are currently working on (not their job title)
+- Listen for the specific problem before mentioning your product
+- Exchange contact with context: "I am working on something related to what you just described -- can I follow up?"
+
+**Anti-patterns:**
+- Setting up a booth and waiting for people to come to you
+- Handing out branded swag with no conversation
+- Pitching during the speaker's Q&A
+
+---
+
+## YouTube
+
+**Template structure:** Collaboration angle + format match + audience overlap.
+
+**Entry approaches:**
+1. **Guest appearance / collaboration:** Reach out to mid-size channels (10K-100K subscribers). Offer to demo your product in the context of a problem the channel covers.
+2. **Comment contribution:** Leave specific, detailed technical comments on relevant videos. Builds name recognition if comment is genuinely useful.
+3. **Response video:** Create a video that directly responds to or extends content from a popular channel in your space.
+
+**Content formats:**
+- Tutorials showing how to solve a specific problem (not "intro to our product")
+- Behind-the-scenes engineering decisions ("why we chose X over Y")
+- Live coding / live debugging sessions
+
+**Anti-patterns:**
+- Posting promotional comments with product links (removed by YouTube spam filters)
+- Asking channels to "check out our product" in collaboration outreach
+- Creating a channel with only product demos and expecting organic growth
+
+---
+
+## Hacker News
+
+**Template structure:** Post type + framing + timing.
+
+**Entry approaches:**
+1. **Show HN:** "Show HN: [product name] -- [what it does in one clause]" Posts that include a working demo, clear problem statement, and invite criticism score highest.
+2. **Ask HN:** "Ask HN: How do you handle [specific technical problem]?" -- Join the conversation, answer questions, mention your product only if directly relevant and asked.
+3. **Comment on relevant stories:** Find stories about competitor products or your problem space. Leave detailed, opinionated technical comments.
+
+**Timing:**
+- Post Show HN between 7am-10am US Eastern on weekdays
+- Avoid Friday afternoons and weekends
+- Flag posts by 8am to catch morning traffic
+
+**Anti-patterns:**
+- "I am the founder of X -- check out our product" (downvoted as marketing)
+- Posting without a working demo or detailed technical explanation
+- Flagging/reporting competitor posts to reduce their visibility
+- Posting the same content twice

package/skills/where-your-customer-lives/references/scoring-guide.md

@@ -0,0 +1,141 @@
+# Channel Scoring Guide
+
+## Formula
+
+```python
+channel_score = (
+    icp_signal_count * 10                          # ICP posts traced to this channel
+    + min(math.log10(max(member_count, 1)) * 15, 50)  # community size (log scale, max 50)
+    + min(activity_score, 30)                      # posts/week proxy (max 30)
+    + competitor_mention_count * 5                 # competitor discussed here = ICP present
+) - entry_difficulty_penalty                       # -20 paid, -10 invite-only, 0 open
+```
+
+## Component Breakdown
+
+### icp_signal_count (weight: 10 per signal)
+
+The number of Reddit/HN posts matching ICP queries that were found in this channel. This is the primary driver.
+
+- 10 signals = +100 points (pushes a channel to top-priority on its own)
+- 5 signals = +50 points
+- 1 signal = +10 points
+- 0 signals = 0 (channel found via DDG, not signal-trace)
+
+**Why highest weight:** A developer clicking "post" in r/devops about the exact pain your product solves is the strongest possible channel signal. It means your ICP is not just a member -- they are actively discussing the problem there.
+
+### member_count (log scale, max 50 points)
+
+Log10 of member count * 15, capped at 50 to prevent massive channels from dominating.
+
+| Members | Score contribution |
+|---|---|
+| 1,000 | 45 |
+| 10,000 | 45 |
+| 50,000 | 50 (capped) |
+| 100,000 | 50 (capped) |
+| 500,000 | 50 (capped) |
+
+**Why log scale:** The difference between 1K and 10K members matters. The difference between 200K and 500K members does not -- both are "large enough." Log scale reflects this.
+
+**Why capped:** A 5M-member general subreddit like r/programming would score 65+ on size alone even with 0 ICP signals. The cap prevents this.
+
+### activity_score (max 30 points)
+
+Reddit: `active_user_count / 100` (users currently online = proxy for posts/week frequency), capped at 30.
+
+DuckDuckGo channels: defaults to 5 (DDG doesn't expose activity metrics).
+
+HN: hardcoded to 20 (HN is always active for tech/startup ICPs).
+
+| Active users | Activity score |
+|---|---|
+| 100 | 1 |
+| 500 | 5 |
+| 1,000 | 10 |
+| 2,000 | 20 |
+| 3,000+ | 30 (capped) |
+
+### competitor_mention_count (weight: 5 per mention)
+
+Number of ICP posts in this channel that also mention a competitor product.
+
+**Why this matters:** A post that says "I'm trying to decide between Datadog and New Relic" in r/devops tells you three things: (1) the ICP is in this channel, (2) they are actively evaluating tools, (3) they are reachable at that exact moment of evaluation.
+
+- 5 competitor mentions = +25 points
+- 10 competitor mentions = +50 points
+
+### entry_difficulty_penalty
+
+| Entry type | Penalty | When to apply |
+|---|---|---|
+| Open | 0 | Free to join, no approval needed |
+| Invite-only | -10 | Requires invite link or member approval |
+| Paid | -20 | Requires paid membership or sponsorship to reach audience |
+
+**Why penalty, not exclusion:** A paid conference with 500 exact-ICP attendees is still worth knowing about. The penalty reduces its score relative to free channels -- it doesn't hide it.
+
+---
+
+## Tier Thresholds
+
+| Tier | Score range | Interpretation |
+|---|---|---|
+| top-priority | >= 100 | Strong ICP signal + sufficient size + accessible. Start here. |
+| high | 60-99 | Good signal or good size. Second tier for outreach. |
+| medium | 30-59 | Moderate signal. Worth watching but not the first channel to invest in. |
+| low | < 30 | Thin signal or small community. Useful for niche products, not general GTM. |
+| excluded | < 5 | Filtered out entirely. DDG noise, irrelevant results. |
+
+---
+
+## Worked Examples
+
+### r/devops with 34 ICP signals
+
+```
+icp_signal_count:     34 * 10  = 340
+member_count:         234,000 -> min(log10(234000) * 15, 50) = 50
+activity_score:       12,000 active_users / 100 = 120 -> capped at 30
+competitor_mentions:  12 * 5  = 60
+entry_penalty:        0 (open)
+
+Total: 340 + 50 + 30 + 60 - 0 = 480  -> top-priority
+```
+
+### DevOps Weekly Newsletter with 0 ICP signals
+
+```
+icp_signal_count:     0 * 10   = 0
+member_count:         25,000 -> min(log10(25000) * 15, 50) = 44.7 -> ~45
+activity_score:       5 (default for DDG channels)
+competitor_mentions:  0 * 5    = 0
+entry_penalty:        -20 (paid sponsorship)
+
+Total: 0 + 45 + 5 + 0 - 20 = 30  -> medium
+```
+
+### r/startups with 2 ICP signals
+
+```
+icp_signal_count:     2 * 10   = 20
+member_count:         800,000 -> capped at 50
+activity_score:       8,000 / 100 = 80 -> capped at 30
+competitor_mentions:  0 * 5    = 0
+entry_penalty:        0
+
+Total: 20 + 50 + 30 + 0 = 100  -> top-priority (barely)
+```
+
+This edge case shows why icp_signal_count is primary: r/startups hits top-priority only because it's enormous + active. In practice, its generic ICP would show in the evidence posts (founders vs. your specific ICP). The AI should note this in who_is_here.
+
+---
+
+## Score Interpretation for AI
+
+When generating the playbook, use the score and tier as a prioritization signal -- not an absolute quality ranking:
+
+- **top-priority:** Recommend the founder invest time here first. Build presence before pitching. Entry tactic should be specific and low-friction.
+- **high:** Recommend as second-tier. Good for content distribution or monitoring. Entry tactic can be higher-effort (e.g., guest appearance, newsletter pitch).
+- **medium:** Recommend for awareness only. Entry tactic should be lower-effort (e.g., occasional commenting, monitoring for competitor discussions).
+- **low:** Report in output for completeness. No entry tactic needed unless it's a competitor forum (high intent despite low score).