@anysiteio/agent-skills 1.0.0
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/.claude-plugin/marketplace.json +113 -0
- package/.claude-plugin/plugin.json +45 -0
- package/LICENSE +21 -0
- package/README.md +221 -0
- package/bin/install.js +55 -0
- package/package.json +45 -0
- package/skills/anysite-audience-analysis/SKILL.md +273 -0
- package/skills/anysite-audience-analysis/references/PLATFORM_COVERAGE.md +53 -0
- package/skills/anysite-audience-analysis/references/TOOL_MAPPING.md +27 -0
- package/skills/anysite-brand-reputation/SKILL.md +373 -0
- package/skills/anysite-brand-reputation/references/MONITORING_GUIDE.md +84 -0
- package/skills/anysite-competitor-analyzer/SKILL.md +847 -0
- package/skills/anysite-competitor-intelligence/SKILL.md +642 -0
- package/skills/anysite-competitor-intelligence/references/ANALYSIS_PATTERNS.md +97 -0
- package/skills/anysite-content-analytics/SKILL.md +298 -0
- package/skills/anysite-content-analytics/references/METRICS_GUIDE.md +63 -0
- package/skills/anysite-influencer-discovery/SKILL.md +398 -0
- package/skills/anysite-influencer-discovery/references/DISCOVERY_CRITERIA.md +50 -0
- package/skills/anysite-lead-generation/SKILL.md +1022 -0
- package/skills/anysite-lead-generation/references/LINKEDIN_STRATEGIES.md +739 -0
- package/skills/anysite-lead-generation/references/WEB_SCRAPING.md +910 -0
- package/skills/anysite-market-research/SKILL.md +379 -0
- package/skills/anysite-market-research/references/RESEARCH_METHODS.md +65 -0
- package/skills/anysite-person-analyzer/SKILL.md +604 -0
- package/skills/anysite-trend-analysis/SKILL.md +310 -0
- package/skills/anysite-trend-analysis/references/SOCIAL_MONITORING.md +46 -0
- package/skills/anysite-vc-analyst/SKILL.md +269 -0
|
@@ -0,0 +1,310 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: anysite-trend-analysis
|
|
3
|
+
description: Discover and track emerging trends across Twitter/X, Reddit, YouTube, LinkedIn, and Instagram using anysite MCP server. Identify viral content, monitor topic momentum, detect trending hashtags, analyze search patterns, and track industry shifts. Supports multi-platform trend detection, sentiment analysis, and momentum tracking. Use when users need to identify emerging trends, track viral content, monitor market shifts, discover trending topics, or analyze social media conversations for strategic insights.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# anysite Trend Analysis
|
|
7
|
+
|
|
8
|
+
Discover emerging trends and track viral content across social platforms using anysite MCP. Identify what's gaining momentum before it peaks.
|
|
9
|
+
|
|
10
|
+
## Overview
|
|
11
|
+
|
|
12
|
+
- **Detect emerging trends** across multiple platforms
|
|
13
|
+
- **Track viral content** and identify breakout topics
|
|
14
|
+
- **Monitor hashtag performance** and trending keywords
|
|
15
|
+
- **Analyze topic momentum** and growth patterns
|
|
16
|
+
- **Identify market shifts** through social listening
|
|
17
|
+
|
|
18
|
+
**Coverage**: 75% - Good for Twitter, Reddit, YouTube, LinkedIn, Instagram
|
|
19
|
+
|
|
20
|
+
## Supported Platforms
|
|
21
|
+
|
|
22
|
+
- ✅ **Twitter/X**: Trending topics, viral tweets, hashtag tracking
|
|
23
|
+
- ✅ **Reddit**: Trending posts, subreddit activity, upvote velocity
|
|
24
|
+
- ✅ **YouTube**: Trending videos, search trends, rising channels
|
|
25
|
+
- ✅ **LinkedIn**: Professional trends, industry discussions
|
|
26
|
+
- ✅ **Instagram**: Trending hashtags, viral content
|
|
27
|
+
|
|
28
|
+
## Quick Start
|
|
29
|
+
|
|
30
|
+
**Step 1: Search for Trending Content**
|
|
31
|
+
|
|
32
|
+
By platform:
|
|
33
|
+
- Twitter: `search_twitter_posts(query, count)` sorted by engagement
|
|
34
|
+
- Reddit: `search_reddit_posts(query, count)` sorted by upvotes
|
|
35
|
+
- YouTube: `search_youtube_videos(query, count)` by recent
|
|
36
|
+
- LinkedIn: `search_linkedin_posts(keywords, count)`
|
|
37
|
+
- Instagram: `search_instagram_posts(query, count)`
|
|
38
|
+
|
|
39
|
+
**Step 2: Analyze Momentum**
|
|
40
|
+
|
|
41
|
+
Check indicators:
|
|
42
|
+
- Engagement velocity (growth rate)
|
|
43
|
+
- Cross-platform presence
|
|
44
|
+
- Comment volume and sentiment
|
|
45
|
+
- Share/retweet patterns
|
|
46
|
+
|
|
47
|
+
**Step 3: Track Over Time**
|
|
48
|
+
|
|
49
|
+
Monitor changes:
|
|
50
|
+
- Daily engagement growth
|
|
51
|
+
- New platform adoption
|
|
52
|
+
- Mainstream vs. niche spread
|
|
53
|
+
- Peak timing prediction
|
|
54
|
+
|
|
55
|
+
**Step 4: Report Insights**
|
|
56
|
+
|
|
57
|
+
Deliver:
|
|
58
|
+
- Trending topics list
|
|
59
|
+
- Momentum indicators
|
|
60
|
+
- Strategic recommendations
|
|
61
|
+
- Early warnings or opportunities
|
|
62
|
+
|
|
63
|
+
## Common Workflows
|
|
64
|
+
|
|
65
|
+
### Workflow 1: Multi-Platform Trend Detection
|
|
66
|
+
|
|
67
|
+
**Scenario**: Identify what's trending in tech/AI space
|
|
68
|
+
|
|
69
|
+
**Steps**:
|
|
70
|
+
|
|
71
|
+
1. **Search Across Platforms**
|
|
72
|
+
```
|
|
73
|
+
# Twitter
|
|
74
|
+
search_twitter_posts(query="AI OR artificial intelligence", count=100)
|
|
75
|
+
Filter for: Posted within 24-48h, high engagement
|
|
76
|
+
|
|
77
|
+
# Reddit
|
|
78
|
+
search_reddit_posts(query="artificial intelligence", count=100)
|
|
79
|
+
Filter: r/technology, r/MachineLearning, r/singularity
|
|
80
|
+
|
|
81
|
+
# YouTube
|
|
82
|
+
search_youtube_videos(query="AI news", count=50)
|
|
83
|
+
Filter: Published this week, views >10k
|
|
84
|
+
|
|
85
|
+
# LinkedIn
|
|
86
|
+
search_linkedin_posts(keywords="artificial intelligence", count=50)
|
|
87
|
+
Filter: High engagement, recent
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
2. **Extract Common Themes**
|
|
91
|
+
```
|
|
92
|
+
Analyze content for recurring:
|
|
93
|
+
- Keywords and phrases
|
|
94
|
+
- Company/product mentions
|
|
95
|
+
- Events or announcements
|
|
96
|
+
- Questions or concerns
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
3. **Calculate Trend Score**
|
|
100
|
+
```
|
|
101
|
+
For each theme:
|
|
102
|
+
- Platform count (how many platforms)
|
|
103
|
+
- Total engagement
|
|
104
|
+
- Growth velocity
|
|
105
|
+
- Sentiment distribution
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
4. **Identify Breakout Trends**
|
|
109
|
+
```
|
|
110
|
+
Trends with:
|
|
111
|
+
- Presence on 3+ platforms
|
|
112
|
+
- Engagement growing >50% daily
|
|
113
|
+
- Positive or controversial sentiment
|
|
114
|
+
- Coverage by influencers/media
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
**Expected Output**:
|
|
118
|
+
- Top 5-10 trending themes
|
|
119
|
+
- Platform-by-platform breakdown
|
|
120
|
+
- Momentum indicators
|
|
121
|
+
- Strategic implications
|
|
122
|
+
|
|
123
|
+
### Workflow 2: Hashtag Performance Tracking
|
|
124
|
+
|
|
125
|
+
**Scenario**: Monitor hashtag growth and adoption
|
|
126
|
+
|
|
127
|
+
**Steps**:
|
|
128
|
+
|
|
129
|
+
1. **Search by Hashtag**
|
|
130
|
+
```
|
|
131
|
+
# Instagram
|
|
132
|
+
search_instagram_posts(query="#sustainability", count=100)
|
|
133
|
+
Group by: Last 24h, last week, last month
|
|
134
|
+
|
|
135
|
+
# Twitter
|
|
136
|
+
search_twitter_posts(query="#sustainability", count=100)
|
|
137
|
+
Track tweet volume over time
|
|
138
|
+
|
|
139
|
+
# LinkedIn
|
|
140
|
+
search_linkedin_posts(keywords="sustainability", count=50)
|
|
141
|
+
Check professional adoption
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
2. **Calculate Velocity**
|
|
145
|
+
```
|
|
146
|
+
Hashtag velocity:
|
|
147
|
+
- Posts in last 24h vs. previous 24h
|
|
148
|
+
- Engagement rate change
|
|
149
|
+
- New accounts using hashtag
|
|
150
|
+
- Geographic spread
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
3. **Analyze Content Evolution**
|
|
154
|
+
```
|
|
155
|
+
Compare early vs. recent posts:
|
|
156
|
+
- Topic shifts
|
|
157
|
+
- Audience changes
|
|
158
|
+
- Influencer involvement
|
|
159
|
+
- Commercial adoption
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
4. **Predict Peak**
|
|
163
|
+
```
|
|
164
|
+
Based on growth curve:
|
|
165
|
+
- Early stage (accelerating)
|
|
166
|
+
- Peak stage (plateauing)
|
|
167
|
+
- Decline stage (slowing)
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
**Expected Output**:
|
|
171
|
+
- Hashtag performance report
|
|
172
|
+
- Growth trajectory
|
|
173
|
+
- Peak timing estimate
|
|
174
|
+
- Strategic recommendations
|
|
175
|
+
|
|
176
|
+
### Workflow 3: Reddit Trend Mining
|
|
177
|
+
|
|
178
|
+
**Scenario**: Find emerging discussions in specific communities
|
|
179
|
+
|
|
180
|
+
**Steps**:
|
|
181
|
+
|
|
182
|
+
1. **Search Target Subreddits**
|
|
183
|
+
```
|
|
184
|
+
search_reddit_posts(
|
|
185
|
+
query="",
|
|
186
|
+
subreddit="technology"
|
|
187
|
+
)
|
|
188
|
+
→ Get top posts from last week
|
|
189
|
+
```
|
|
190
|
+
|
|
191
|
+
2. **Analyze Post Momentum**
|
|
192
|
+
```
|
|
193
|
+
For each post:
|
|
194
|
+
get_reddit_post(post_url)
|
|
195
|
+
get_reddit_post_comments(post_url)
|
|
196
|
+
|
|
197
|
+
Calculate:
|
|
198
|
+
- Upvotes per hour
|
|
199
|
+
- Comment velocity
|
|
200
|
+
- Award count
|
|
201
|
+
- Controversial score
|
|
202
|
+
```
|
|
203
|
+
|
|
204
|
+
3. **Extract Discussion Themes**
|
|
205
|
+
```
|
|
206
|
+
From high-momentum posts:
|
|
207
|
+
- What problems are discussed?
|
|
208
|
+
- What solutions are proposed?
|
|
209
|
+
- What companies/products mentioned?
|
|
210
|
+
- What sentiment (positive, negative, concerned)?
|
|
211
|
+
```
|
|
212
|
+
|
|
213
|
+
4. **Track Cross-Pollination**
|
|
214
|
+
```
|
|
215
|
+
Check if trending Reddit topics appear on:
|
|
216
|
+
- Twitter (mainstream awareness)
|
|
217
|
+
- LinkedIn (professional discussion)
|
|
218
|
+
- YouTube (explainer content)
|
|
219
|
+
```
|
|
220
|
+
|
|
221
|
+
**Expected Output**:
|
|
222
|
+
- Top Reddit trends
|
|
223
|
+
- Community sentiment
|
|
224
|
+
- Mainstream potential
|
|
225
|
+
- Early mover opportunities
|
|
226
|
+
|
|
227
|
+
## MCP Tools Reference
|
|
228
|
+
|
|
229
|
+
### Twitter/X
|
|
230
|
+
- `search_twitter_posts(query, count)` - Find tweets, filter by engagement
|
|
231
|
+
- `get_twitter_user(user)` - Check influencer adoption
|
|
232
|
+
|
|
233
|
+
### Reddit
|
|
234
|
+
- `search_reddit_posts(query, subreddit, count)` - Find discussions
|
|
235
|
+
- `get_reddit_post(url)` - Get post details and momentum
|
|
236
|
+
- `get_reddit_post_comments(url)` - Analyze discussion depth
|
|
237
|
+
|
|
238
|
+
### YouTube
|
|
239
|
+
- `search_youtube_videos(query, count)` - Find trending videos
|
|
240
|
+
- `get_youtube_video(video)` - Track view velocity
|
|
241
|
+
- `get_youtube_video_comments(video, count)` - Gauge interest
|
|
242
|
+
|
|
243
|
+
### LinkedIn
|
|
244
|
+
- `search_linkedin_posts(keywords, count)` - Professional trends
|
|
245
|
+
- `get_linkedin_company_posts(urn, count)` - Corporate adoption
|
|
246
|
+
|
|
247
|
+
### Instagram
|
|
248
|
+
- `search_instagram_posts(query, count)` - Hashtag trends
|
|
249
|
+
- `get_instagram_post(post_id)` - Engagement metrics
|
|
250
|
+
|
|
251
|
+
## Trend Identification Framework
|
|
252
|
+
|
|
253
|
+
**Trend Stages**:
|
|
254
|
+
|
|
255
|
+
1. **Emergence** (0-20% awareness)
|
|
256
|
+
- Niche communities discussing
|
|
257
|
+
- Low but accelerating engagement
|
|
258
|
+
- Early adopters experimenting
|
|
259
|
+
- Action: Monitor closely, prepare strategy
|
|
260
|
+
|
|
261
|
+
2. **Growth** (20-50% awareness)
|
|
262
|
+
- Crossing into mainstream platforms
|
|
263
|
+
- Rapid engagement growth
|
|
264
|
+
- Influencer adoption
|
|
265
|
+
- Action: Create content, engage actively
|
|
266
|
+
|
|
267
|
+
3. **Peak** (50-80% awareness)
|
|
268
|
+
- Maximum visibility
|
|
269
|
+
- Slowing growth rate
|
|
270
|
+
- Saturation approaching
|
|
271
|
+
- Action: Maximize presence before decline
|
|
272
|
+
|
|
273
|
+
4. **Decline** (80-100% awareness)
|
|
274
|
+
- Engagement decreasing
|
|
275
|
+
- Moving to "background noise"
|
|
276
|
+
- New trends emerging
|
|
277
|
+
- Action: Shift focus to next trend
|
|
278
|
+
|
|
279
|
+
**Momentum Indicators**:
|
|
280
|
+
- **Volume**: Mentions per day
|
|
281
|
+
- **Velocity**: Growth rate (% change)
|
|
282
|
+
- **Reach**: Unique accounts discussing
|
|
283
|
+
- **Spread**: Number of platforms
|
|
284
|
+
- **Sentiment**: Positive/negative ratio
|
|
285
|
+
- **Influence**: Key accounts involved
|
|
286
|
+
|
|
287
|
+
## Output Formats
|
|
288
|
+
|
|
289
|
+
**Chat Summary**:
|
|
290
|
+
- Top 5 trends with momentum scores
|
|
291
|
+
- Platform breakdown
|
|
292
|
+
- Strategic recommendations
|
|
293
|
+
|
|
294
|
+
**CSV Export**:
|
|
295
|
+
- Trend name, platforms, volume
|
|
296
|
+
- Growth rate, sentiment
|
|
297
|
+
- Key influencers mentioning
|
|
298
|
+
|
|
299
|
+
**JSON Export**:
|
|
300
|
+
- Complete trend data
|
|
301
|
+
- Time-series metrics
|
|
302
|
+
- Cross-platform correlations
|
|
303
|
+
|
|
304
|
+
## Reference Documentation
|
|
305
|
+
|
|
306
|
+
- **[SOCIAL_MONITORING.md](references/SOCIAL_MONITORING.md)** - Social listening techniques, monitoring strategies, and trend prediction methods
|
|
307
|
+
|
|
308
|
+
---
|
|
309
|
+
|
|
310
|
+
**Ready to discover trends?** Ask Claude to help you identify emerging topics, track viral content, or monitor market shifts across social platforms!
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# Social Media Trend Monitoring
|
|
2
|
+
|
|
3
|
+
## Trend Detection Techniques
|
|
4
|
+
|
|
5
|
+
**Volume Spike Detection**:
|
|
6
|
+
```
|
|
7
|
+
Track mentions per hour/day
|
|
8
|
+
Alert when >2x normal volume
|
|
9
|
+
Indicates emerging interest
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
**Velocity Tracking**:
|
|
13
|
+
```
|
|
14
|
+
Calculate growth rate:
|
|
15
|
+
(Today's mentions - Yesterday's mentions) / Yesterday's mentions
|
|
16
|
+
|
|
17
|
+
>50% = High momentum
|
|
18
|
+
>100% = Viral potential
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
**Cross-Platform Validation**:
|
|
22
|
+
```
|
|
23
|
+
True trends appear on multiple platforms:
|
|
24
|
+
- Niche platform (Reddit) → Mainstream (Twitter) → Professional (LinkedIn)
|
|
25
|
+
- Early signal: Reddit or specialty forums
|
|
26
|
+
- Confirmation: Twitter + LinkedIn adoption
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
## Monitoring Cadence
|
|
30
|
+
|
|
31
|
+
**Daily**: Hot topics, viral content
|
|
32
|
+
**Weekly**: Emerging themes
|
|
33
|
+
**Monthly**: Industry shifts
|
|
34
|
+
**Quarterly**: Market trends
|
|
35
|
+
|
|
36
|
+
## Trend Prediction Signals
|
|
37
|
+
|
|
38
|
+
**Early Indicators**:
|
|
39
|
+
- Sudden subreddit activity
|
|
40
|
+
- Influencer experimentation
|
|
41
|
+
- Technical community discussion
|
|
42
|
+
|
|
43
|
+
**Confirmation Signals**:
|
|
44
|
+
- Media coverage
|
|
45
|
+
- Corporate adoption
|
|
46
|
+
- Mainstream platform presence
|
|
@@ -0,0 +1,269 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: anysite-vc-analyst
|
|
3
|
+
description: |
|
|
4
|
+
Universal VC investor analysis and outreach agent. Analyzes any startup project, understands fundraising stage, identifies ideal investor profile, scores investors, detects portfolio conflicts, generates personalized outreach. Starts with discovery questions to understand the project. Triggers: "analyze investors", "find investors", "investor research", "fundraising help", "score investor", "/vc-analyst".
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# VC Investor Analyst
|
|
8
|
+
|
|
9
|
+
Universal agent for startup investor research and outreach.
|
|
10
|
+
|
|
11
|
+
## Onboarding Flow (REQUIRED FIRST)
|
|
12
|
+
|
|
13
|
+
Before analyzing investors, gather project context. Use `AskUserQuestion` tool.
|
|
14
|
+
|
|
15
|
+
### Step 1: Project Discovery
|
|
16
|
+
|
|
17
|
+
Ask user to provide:
|
|
18
|
+
1. **Company website** - to fetch and analyze
|
|
19
|
+
2. **Pitch deck or materials** - file path or link
|
|
20
|
+
3. **One-liner** - what does the company do?
|
|
21
|
+
|
|
22
|
+
```
|
|
23
|
+
AskUserQuestion:
|
|
24
|
+
- "What's your company website?"
|
|
25
|
+
- "Do you have a pitch deck I can review? (path or link)"
|
|
26
|
+
- "In one sentence, what does your company do?"
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
### Step 2: Fetch & Analyze Project
|
|
30
|
+
|
|
31
|
+
1. **Website**: Use `mcp__anysite__parse_webpage(url=website)` to understand:
|
|
32
|
+
- Product/service description
|
|
33
|
+
- Target market
|
|
34
|
+
- Key features
|
|
35
|
+
- Pricing (if visible)
|
|
36
|
+
|
|
37
|
+
2. **Pitch deck**: Use `Read` tool if local file, or `WebFetch` if link
|
|
38
|
+
|
|
39
|
+
3. **Extract key info**:
|
|
40
|
+
- Problem & Solution
|
|
41
|
+
- Market size (TAM/SAM/SOM)
|
|
42
|
+
- Business model
|
|
43
|
+
- Traction metrics
|
|
44
|
+
- Team background
|
|
45
|
+
- Competitive landscape
|
|
46
|
+
|
|
47
|
+
### Step 3: Fundraising Context
|
|
48
|
+
|
|
49
|
+
Ask with `AskUserQuestion`:
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
questions:
|
|
53
|
+
- question: "What stage are you raising?"
|
|
54
|
+
header: "Stage"
|
|
55
|
+
options:
|
|
56
|
+
- label: "Pre-Seed ($250K-$1M)"
|
|
57
|
+
description: "First institutional round, idea to early product"
|
|
58
|
+
- label: "Seed ($1M-$3M)"
|
|
59
|
+
description: "Product-market fit exploration"
|
|
60
|
+
- label: "Series A ($5M-$15M)"
|
|
61
|
+
description: "Scaling proven model"
|
|
62
|
+
- label: "Other"
|
|
63
|
+
description: "Specify your round"
|
|
64
|
+
|
|
65
|
+
- question: "How much are you raising?"
|
|
66
|
+
header: "Amount"
|
|
67
|
+
options:
|
|
68
|
+
- label: "$500K or less"
|
|
69
|
+
- label: "$500K - $1M"
|
|
70
|
+
- label: "$1M - $2M"
|
|
71
|
+
- label: "$2M+"
|
|
72
|
+
|
|
73
|
+
- question: "What's your current traction?"
|
|
74
|
+
header: "Traction"
|
|
75
|
+
options:
|
|
76
|
+
- label: "Pre-revenue"
|
|
77
|
+
description: "Building product, no revenue yet"
|
|
78
|
+
- label: "Early revenue (<$10K MRR)"
|
|
79
|
+
description: "First paying customers"
|
|
80
|
+
- label: "$10K-$50K MRR"
|
|
81
|
+
description: "Growing customer base"
|
|
82
|
+
- label: "$50K+ MRR"
|
|
83
|
+
description: "Strong traction"
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
### Step 4: Investor Preferences
|
|
87
|
+
|
|
88
|
+
Ask with `AskUserQuestion`:
|
|
89
|
+
|
|
90
|
+
```
|
|
91
|
+
questions:
|
|
92
|
+
- question: "What type of investors are you targeting?"
|
|
93
|
+
header: "Investor Type"
|
|
94
|
+
multiSelect: true
|
|
95
|
+
options:
|
|
96
|
+
- label: "Angel investors"
|
|
97
|
+
description: "Individual investors, $25K-$250K checks"
|
|
98
|
+
- label: "Micro VCs"
|
|
99
|
+
description: "Small funds, $100K-$500K checks"
|
|
100
|
+
- label: "Seed VCs"
|
|
101
|
+
description: "Institutional seed funds, $500K-$2M"
|
|
102
|
+
- label: "Strategic angels"
|
|
103
|
+
description: "Industry experts for advice + capital"
|
|
104
|
+
|
|
105
|
+
- question: "Geographic preference?"
|
|
106
|
+
header: "Location"
|
|
107
|
+
options:
|
|
108
|
+
- label: "US only"
|
|
109
|
+
- label: "US + Europe"
|
|
110
|
+
- label: "Global"
|
|
111
|
+
- label: "Specific region"
|
|
112
|
+
|
|
113
|
+
- question: "Any specific industries or themes they should focus on?"
|
|
114
|
+
header: "Thesis"
|
|
115
|
+
multiSelect: true
|
|
116
|
+
options:
|
|
117
|
+
- label: "B2B SaaS"
|
|
118
|
+
- label: "AI/ML"
|
|
119
|
+
- label: "Developer Tools"
|
|
120
|
+
- label: "Other (specify)"
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
### Step 5: Build Investor Profile
|
|
124
|
+
|
|
125
|
+
After gathering info, create `investor_criteria.json`:
|
|
126
|
+
|
|
127
|
+
```json
|
|
128
|
+
{
|
|
129
|
+
"company": {
|
|
130
|
+
"name": "...",
|
|
131
|
+
"website": "...",
|
|
132
|
+
"one_liner": "...",
|
|
133
|
+
"stage": "Pre-Seed",
|
|
134
|
+
"raising": "$1M",
|
|
135
|
+
"traction": "...",
|
|
136
|
+
"thesis_keywords": ["B2B SaaS", "AI", "..."]
|
|
137
|
+
},
|
|
138
|
+
"ideal_investor": {
|
|
139
|
+
"types": ["Angel", "Micro VC"],
|
|
140
|
+
"check_size": "$50K-$500K",
|
|
141
|
+
"stage_focus": ["Pre-Seed", "Seed"],
|
|
142
|
+
"thesis_match": ["B2B SaaS", "AI", "Developer Tools"],
|
|
143
|
+
"geography": "US + Europe"
|
|
144
|
+
},
|
|
145
|
+
"competitors": ["competitor1", "competitor2"],
|
|
146
|
+
"outreach": {
|
|
147
|
+
"pitch_deck_link": "...",
|
|
148
|
+
"calendar_link": "...",
|
|
149
|
+
"sender_name": "...",
|
|
150
|
+
"sender_title": "..."
|
|
151
|
+
}
|
|
152
|
+
}
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
Save to `data/investor_criteria.json` for reference.
|
|
156
|
+
|
|
157
|
+
---
|
|
158
|
+
|
|
159
|
+
## Investor Analysis Workflow
|
|
160
|
+
|
|
161
|
+
After onboarding, analyze investors from CSV or list.
|
|
162
|
+
|
|
163
|
+
### 1. Fetch LinkedIn Profile (ALWAYS FIRST)
|
|
164
|
+
|
|
165
|
+
```
|
|
166
|
+
mcp__anysite__get_linkedin_profile(user="linkedin-url-or-username")
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
CSV data has ~20% error rate. Always verify actual role before scoring.
|
|
170
|
+
|
|
171
|
+
### 2. Score Investor (0-100)
|
|
172
|
+
|
|
173
|
+
| Factor | Weight | Check |
|
|
174
|
+
|--------|--------|-------|
|
|
175
|
+
| **Is Actually Investor** | GATE | Role: Partner, GP, Angel, EIR (NOT: Director, Manager, Engineer) |
|
|
176
|
+
| **Stage Fit** | 25% | Matches company's raising stage |
|
|
177
|
+
| **Thesis Match** | 25% | Matches company's thesis keywords |
|
|
178
|
+
| **Portfolio Relevance** | 30% | Similar companies in portfolio |
|
|
179
|
+
| **Activity Level** | 10% | Investments in last 12-18 months |
|
|
180
|
+
| **Network Value** | 10% | Accelerator ties, fund network |
|
|
181
|
+
|
|
182
|
+
**Disqualifiers (Score = 0):**
|
|
183
|
+
- Corporate role at non-investment firm
|
|
184
|
+
- Thesis mismatch (e.g., Crypto-only when company is SaaS)
|
|
185
|
+
- Wrong person at LinkedIn URL
|
|
186
|
+
- Stage too late (Series B+ fund for pre-seed company)
|
|
187
|
+
|
|
188
|
+
### 3. Check Portfolio Conflicts
|
|
189
|
+
|
|
190
|
+
Search for investments in company's competitors:
|
|
191
|
+
```
|
|
192
|
+
WebSearch("[Fund name] portfolio companies")
|
|
193
|
+
WebSearch("[Investor name] investments [competitor name]")
|
|
194
|
+
```
|
|
195
|
+
|
|
196
|
+
**If conflict found:** -20 points + flag "PORTFOLIO CONFLICT"
|
|
197
|
+
|
|
198
|
+
### 4. Generate Outreach Message
|
|
199
|
+
|
|
200
|
+
For Score > 70, create personalized message using company's outreach config:
|
|
201
|
+
|
|
202
|
+
```
|
|
203
|
+
Hi [Name],
|
|
204
|
+
|
|
205
|
+
[Hook from verified portfolio/achievement relevant to THIS company]
|
|
206
|
+
|
|
207
|
+
[1-2 sentences about company - from one_liner]
|
|
208
|
+
|
|
209
|
+
[Traction from company profile]
|
|
210
|
+
|
|
211
|
+
[Question based on their expertise]
|
|
212
|
+
|
|
213
|
+
Here's our pitch deck: [pitch_deck_link]
|
|
214
|
+
|
|
215
|
+
If you'd like to chat: [calendar_link]
|
|
216
|
+
If no slots work, send your availability.
|
|
217
|
+
|
|
218
|
+
Best,
|
|
219
|
+
[sender_name]
|
|
220
|
+
[sender_title]
|
|
221
|
+
```
|
|
222
|
+
|
|
223
|
+
---
|
|
224
|
+
|
|
225
|
+
## Output Format
|
|
226
|
+
|
|
227
|
+
### Per Investor
|
|
228
|
+
```json
|
|
229
|
+
{
|
|
230
|
+
"investor": "Name",
|
|
231
|
+
"linkedin": "url",
|
|
232
|
+
"score": 85,
|
|
233
|
+
"current_role": "Partner @ Fund",
|
|
234
|
+
"stage_fit": "Pre-seed focus - MATCH",
|
|
235
|
+
"thesis_match": ["AI", "B2B SaaS"],
|
|
236
|
+
"portfolio_relevant": ["Company1", "Company2"],
|
|
237
|
+
"conflicts": [],
|
|
238
|
+
"risk_factors": [],
|
|
239
|
+
"outreach_hook": "Your investment in X...",
|
|
240
|
+
"message": "Full outreach text"
|
|
241
|
+
}
|
|
242
|
+
```
|
|
243
|
+
|
|
244
|
+
### Batch Summary
|
|
245
|
+
```json
|
|
246
|
+
{
|
|
247
|
+
"batch": 1,
|
|
248
|
+
"total_analyzed": 20,
|
|
249
|
+
"strong_fit": 4,
|
|
250
|
+
"good_fit": 3,
|
|
251
|
+
"not_fit": 13,
|
|
252
|
+
"top_candidates": ["Name1", "Name2"]
|
|
253
|
+
}
|
|
254
|
+
```
|
|
255
|
+
|
|
256
|
+
---
|
|
257
|
+
|
|
258
|
+
## Quick Commands
|
|
259
|
+
|
|
260
|
+
| Command | Action |
|
|
261
|
+
|---------|--------|
|
|
262
|
+
| `/vc-analyst` | Start full onboarding flow |
|
|
263
|
+
| `/vc-analyst analyze [linkedin]` | Analyze single investor (requires prior onboarding) |
|
|
264
|
+
| `/vc-analyst batch [csv-path]` | Analyze batch from CSV |
|
|
265
|
+
| `/vc-analyst update-criteria` | Update investor criteria |
|
|
266
|
+
|
|
267
|
+
## Scoring Reference
|
|
268
|
+
|
|
269
|
+
See [references/scoring.md](references/scoring.md) for detailed criteria and examples.
|