@opendirectory.dev/skills 0.1.38 → 0.1.39

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@opendirectory.dev/skills",
3
- "version": "0.1.38",
3
+ "version": "0.1.39",
4
4
  "main": "dist/index.js",
5
5
  "types": "dist/index.d.ts",
6
6
  "bin": {
package/registry.json CHANGED
@@ -151,8 +151,12 @@
151
151
  },
152
152
  {
153
153
  "name": "map-your-market",
154
- "description": ">-",
155
- "tags": [],
154
+ "description": "Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google...",
155
+ "tags": [
156
+ "SEO",
157
+ "Branding",
158
+ "Developer Tools"
159
+ ],
156
160
  "author": "opendirectory",
157
161
  "version": "0.0.1",
158
162
  "path": "skills/map-your-market"
@@ -339,6 +343,16 @@
339
343
  "version": "0.0.1",
340
344
  "path": "skills/vc-finder"
341
345
  },
346
+ {
347
+ "name": "where-your-customer-lives",
348
+ "description": "Given a product utility and ICP, researches the internet to find the specific channels.",
349
+ "tags": [
350
+ "SEO"
351
+ ],
352
+ "author": "opendirectory",
353
+ "version": "0.0.1",
354
+ "path": "skills/where-your-customer-lives"
355
+ },
342
356
  {
343
357
  "name": "yc-intent-radar-skill",
344
358
  "description": "Scrape daily job listings from YCombinator's Workatastartup platform without duplicates.",
@@ -1,14 +1,6 @@
1
1
  ---
2
2
  name: map-your-market
3
- description: >-
4
- Given a product description, category keywords, or competitor names (any combination), searches
5
- Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market
6
- experiences -- then synthesizes everything into a positioning framework showing who your ICP is,
7
- what they say out loud, and exactly how to talk to them. Use when asked to understand a market,
8
- find ICP pain points, map competitors, build a positioning doc, find messaging angles, or answer
9
- who is my customer and what do they actually care about. Trigger when a user says map my market,
10
- who is my ICP, what pains does my market have, understand my market, find my target customer,
11
- what are the top complaints in X space, help me position my product, or who should I be selling to.
3
+ description: Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences, then synthesizes everything into a positioning framework showing who your ICP is, what they say out loud, and exactly how to talk to them. Use when asked to understand a market, find ICP pain points, map competitors, build a positioning doc, find messaging angles, or answer who is my customer and what do they actually care about. Trigger when a user says map my market, who is my ICP, what pains does my market have, understand my market, find my target customer, what are the top complaints in X space, help me position my product, or who should I be selling to.
12
4
  compatibility: [claude-code, gemini-cli, github-copilot]
13
5
  ---
14
6
 
@@ -0,0 +1,4 @@
1
+ GITHUB_TOKEN= # optional -- github.com/settings/tokens (no scopes needed for public repos)
2
+ # Without it: competitor layer GitHub enrichment runs at 60 req/hr
3
+ # With it: 5000 req/hr -- use if scanning many competitors
4
+ # Core channel discovery (Reddit + DuckDuckGo) works without any token
@@ -0,0 +1,135 @@
1
+ # where-your-customer-lives
2
+
3
+ Give this skill a product utility and ICP. It searches Reddit, Hacker News, and DuckDuckGo to find the specific communities where your customer actually gathers -- then builds a per-channel playbook: evidence your ICP is there, one entry tactic, one content angle, and specific anti-patterns.
4
+
5
+ Stop guessing which communities to post in. Get signal-traced evidence.
6
+
7
+ ## Install
8
+
9
+ ```bash
10
+ npx "@opendirectory.dev/skills" install where-your-customer-lives --target claude
11
+ ```
12
+
13
+ ## What It Does
14
+
15
+ - Accepts: product description + ICP role + ICP pain + competitors (any combination)
16
+ - Signal-traces: searches Reddit/HN for posts matching your ICP, extracts which communities those posts came from
17
+ - Competitor layer: searches where competitors are discussed -- those communities have evaluating ICP
18
+ - Discovers 7 channel types: Reddit, Slack, Discord, Newsletter, Podcast, Conference, YouTube
19
+ - Fetches actual member counts from Reddit API and DuckDuckGo snippets -- no estimates
20
+ - Scores channels: ICP signal count (10x) + size (log scale) + activity + competitor mentions - entry penalty
21
+ - Generates per-channel playbook: who is here, entry tactic, content angle, anti-patterns
22
+ - Saves to `docs/channel-map/[slug]-[date].md` + JSON snapshot
23
+
24
+ ## Requirements
25
+
26
+ | Requirement | Purpose | How to Set Up |
27
+ |---|---|---|
28
+ | GITHUB_TOKEN | Optional -- improves competitor layer rate limit | github.com/settings/tokens (no scopes needed) |
29
+
30
+ No other API keys required.
31
+
32
+ ## Setup
33
+
34
+ ```bash
35
+ cp .env.example .env
36
+ # Add GITHUB_TOKEN if you want higher GitHub rate limits for competitor enrichment
37
+ ```
38
+
39
+ ## How to Use
40
+
41
+ ```
42
+ "Where does my customer live? I build observability tools for DevOps engineers."
43
+ "Find communities for my ICP: sales leaders at B2B SaaS startups dealing with low reply rates."
44
+ "Where should I post? Competitors: Clay, Apollo. ICP: growth engineers."
45
+ "What channels does my ICP use? Product: compliance automation for community banks."
46
+ "I build payment APIs for marketplaces. Who should I reach out to and where?"
47
+ ```
48
+
49
+ Include competitor names for richer channel discovery. Include ICP role + pain for accurate signal-tracing.
50
+
51
+ ## Why This Instead of Googling
52
+
53
+ A founder doing this manually would:
54
+ - Google "devops communities" and get listicles with outdated or generic results
55
+ - Post in r/devops without knowing if their ICP is actually there
56
+ - Spend a month in the wrong Slack before realizing it's not their market
57
+
58
+ This skill traces backwards from actual ICP pain posts to their source communities. The channels it returns are the ones where your ICP is already discussing the exact problem you solve.
59
+
60
+ ## Channel Scoring
61
+
62
+ ```
63
+ channel_score = (
64
+ icp_signal_count * 10 # signals traced here -- highest weight
65
+ + log10(members) * 15, max 50 # community size (log scale)
66
+ + activity_score, max 30 # posts/week proxy
67
+ + competitor_mentions * 5 # competitor discussed = ICP evaluating
68
+ ) - entry_penalty # -20 paid, -10 invite-only, 0 open
69
+ ```
70
+
71
+ Score tiers: top-priority (100+), high (60-99), medium (30-59), low (<30).
72
+
73
+ ## Velocity Tracking
74
+
75
+ Run the skill every quarter. JSON snapshots in `docs/channel-map/` let you track which communities grow or shrink for your ICP over time.
76
+
77
+ ## Cost Per Run
78
+
79
+ - Reddit, HN: free, no auth
80
+ - DuckDuckGo: free, no auth
81
+ - GitHub: free with optional token
82
+ - AI analysis: uses the model running the skill
83
+ - Total: free
84
+
85
+ ## Standalone Script
86
+
87
+ Run channel discovery without Claude. Useful when you want raw channel data first, then bring it to any AI for analysis.
88
+
89
+ ```bash
90
+ # Basic usage
91
+ python3 scripts/fetch.py "devops monitoring" --icp-role "DevOps engineers" --icp-pain "alert fatigue"
92
+
93
+ # With competitors
94
+ python3 scripts/fetch.py "B2B sales" --competitors "Clay,Apollo,HubSpot" --output results.json
95
+
96
+ # Print to stdout
97
+ python3 scripts/fetch.py "startup gtm" --icp-role "technical co-founders" --stdout | jq '.summary'
98
+
99
+ # With GitHub token
100
+ GITHUB_TOKEN=your_token python3 scripts/fetch.py "devops tools" --competitors "Datadog,Grafana"
101
+ ```
102
+
103
+ The script writes a JSON file with all discovered channels. Open it with Claude and ask: "Generate a channel playbook from this data."
104
+
105
+ ## Project Structure
106
+
107
+ ```
108
+ where-your-customer-lives/
109
+ ├── SKILL.md
110
+ ├── README.md
111
+ ├── .env.example
112
+ ├── scripts/
113
+ │ └── fetch.py standalone channel discovery script
114
+ ├── evals/
115
+ │ └── evals.json 5 test cases
116
+ └── references/
117
+ ├── channel-types.md 7 channel types, discovery methods, scoring notes
118
+ ├── entry-tactics.md entry tactic templates per channel type
119
+ └── scoring-guide.md channel scoring formula and tier thresholds
120
+ ```
121
+
122
+ ## What map-your-market Does vs. This Skill
123
+
124
+ | | map-your-market | where-your-customer-lives |
125
+ |---|---|---|
126
+ | Question answered | What does my market care about? | Where does my market gather? |
127
+ | Output | Pain clusters, ICP profile, positioning framework | Ranked channel list with per-channel playbook |
128
+ | Data sources | Reddit, HN, GitHub Issues, G2, Trends | Reddit, HN, DuckDuckGo (7 channel types) |
129
+ | Primary use | Market research, messaging | Distribution, outreach, GTM channels |
130
+
131
+ Run both for a complete picture: map-your-market tells you what to say, where-your-customer-lives tells you where to say it.
132
+
133
+ ## License
134
+
135
+ MIT