anysite-market-research
Conduct comprehensive market research using Y Combinator data, SEC filings, social media insights, and web scraping via anysite MCP server. Analyze tech markets, research startup ecosystems, study public companies, identify market opportunities, and understand competitive dynamics. Supports startup discovery, industry analysis, public company research, and social sentiment analysis. Use when users need to analyze market opportunities, research industries, evaluate startups, study public companies, or gather market intelligence for strategic planning and investment decisions.
What this skill does
# anysite Market Research
Comprehensive market research using Y Combinator, SEC, social media, and web data through anysite MCP. Analyze tech markets, research startups, and study competitive landscapes.
## Overview
- **Research startup ecosystems** via Y Combinator data
- **Analyze public companies** through SEC filings
- **Gather market intelligence** from social platforms
- **Study industry trends** across communities
- **Identify market opportunities** through data analysis
**Coverage**: 70% - Excellent for tech/startup markets; pivoted from local business to tech focus
## Supported Platforms
- ✅ **Y Combinator**: Startup research, batch analysis, founder discovery, funding data
- ✅ **SEC**: Public company filings, financial data, disclosures
- ✅ **Reddit**: Market sentiment, community insights, product discussions
- ✅ **LinkedIn**: Industry trends, company intelligence, professional discussions
- ✅ **Twitter/X**: Market pulse, news, influencer opinions
- ✅ **Web Scraping**: Company websites, industry reports, market data
## v2 MCP Tool Interface
All data fetching uses the universal `execute()` meta-tool. Always call `discover(source, category)` first if you need to verify endpoint names or parameters.
**Core workflow**:
1. `execute(source, category, endpoint, params)` -- fetch data (returns first page + `cache_key`)
2. `get_page(cache_key, offset, limit)` -- paginate through remaining results
3. `query_cache(cache_key, conditions, sort_by, aggregate, group_by)` -- filter/sort/aggregate cached data without new API calls
4. `export_data(cache_key, format)` -- export to CSV, JSON, or JSONL for deliverables
**Error handling**: check response for `llm_hint` field -- it contains actionable guidance when calls fail or return partial data.
## Quick Start
**Step 1: Define Research Scope**
Choose focus:
- Startup ecosystem: `execute("yc", "search", "search", {"query": ...})`
- Public companies: `execute("sec", "search", "search", {"query": ...})`
- Industry sentiment: `execute("reddit", "search", "search", {"query": ...})`, `execute("twitter", "search", "search_users", {"query": ...})`
- Company intelligence: `execute("linkedin", "search", "search_companies", {...})`
**Step 2: Gather Data**
Execute searches:
```
# Startup research
execute("yc", "search", "search", {"query": "fintech", "batch": "W24,S23"})
# Public company research
execute("sec", "search", "search", {"query": "tech company"})
# Market sentiment
execute("reddit", "search", "search", {"query": "fintech trends"})
→ use get_page(cache_key, offset, limit) to collect up to 100 results
```
**Step 3: Analyze Results**
Use `query_cache()` to slice data without re-fetching:
```
# Count startups by category
query_cache(cache_key, aggregate={"field": "category", "function": "count"})
# Filter high-engagement posts
query_cache(cache_key, conditions=[{"field": "score", "operator": ">", "value": 50}], sort_by={"field": "score", "order": "desc"})
```
Extract insights:
- Market size indicators
- Competitive landscape
- Technology trends
- Consumer sentiment
- Funding patterns
**Step 4: Synthesize Findings**
Use `export_data(cache_key, "csv")` or `export_data(cache_key, "json")` to deliver:
- Market opportunity assessment
- Competitive analysis
- Trend identification
- Strategic recommendations
## Common Workflows
### Workflow 1: Startup Ecosystem Analysis
**Scenario**: Analyze fintech startup landscape
**Steps**:
1. **Find Startups**
```
execute("yc", "search", "search", {
"query": "fintech",
"batch": "W24,S23,W23,S22"
})
→ use get_page(cache_key, offset, limit) to paginate through all results
```
2. **Categorize by Focus**
```
For each startup:
execute("yc", "company", "get", {"slug": company_slug})
Group by:
- Payments
- Lending
- Investment/Trading
- Banking
- Insurance
- B2B fintech tools
Or use query_cache to group:
query_cache(cache_key, group_by="category")
```
3. **Analyze Patterns**
```
Identify:
- Hot subcategories (most startups)
- Team size distribution
- Geographic concentration
- Common tech stacks (from job postings)
Use query_cache for aggregation:
query_cache(cache_key, aggregate={"field": "team_size", "function": "avg"})
```
4. **Research Traction**
```
For promising startups:
execute("linkedin", "search", "search_companies", {"keywords": startup_name})
→ Check employee growth
execute("twitter", "search", "search_users", {"query": startup_name})
→ Check social presence and buzz
execute("webparser", "parse", "parse", {"url": startup_website})
→ Check positioning and features
```
5. **Identify White Spaces**
```
Compare:
- Overcrowded categories
- Underserved segments
- Emerging opportunities
- Geographic gaps
```
**Expected Output**:
- 50-100 startup landscape map
- Category distribution
- Funding trends
- Market gaps identified
- Competitive intensity by segment
Use `export_data(cache_key, "csv")` to deliver the startup list as a spreadsheet.
### Workflow 2: Public Company Competitive Analysis
**Scenario**: Research public competitors in cloud infrastructure
**Steps**:
1. **Find Companies**
```
execute("sec", "search", "search", {
"query": "cloud"
})
→ use get_page(cache_key, offset, limit) to collect up to 50 results
```
2. **Get Financial Data**
```
For each company:
execute("sec", "document", "get", {"url": document_url})
Extract:
- Revenue and growth
- Operating margins
- R&D spending
- Geographic breakdown
- Risk factors mentioned
```
3. **Analyze Strategy**
```
From 10-K filings:
- Business model
- Target markets
- Competitive advantages
- Growth initiatives
- Challenges and risks
```
4. **Track Changes**
```
Compare year-over-year:
- Revenue growth trends
- Market focus shifts
- New initiatives
- Risk factor changes
```
5. **Supplement with Social Intel**
```
execute("linkedin", "search", "search_companies", {"keywords": company_name})
→ Employee count, hiring patterns
execute("linkedin", "company", "get", {"company": company_urn})
→ Company details and strategic messaging
execute("reddit", "search", "search", {"query": company_name})
→ Customer sentiment
Use query_cache to filter sentiment:
query_cache(cache_key, conditions=[{"field": "text", "operator": "contains", "value": "review"}])
```
**Expected Output**:
- Competitive landscape map
- Financial benchmarks
- Strategic positioning
- Growth trajectories
- Market opportunities
Use `export_data(cache_key, "json")` for structured competitive data.
### Workflow 3: Industry Trend Analysis
**Scenario**: Understand AI/ML market evolution
**Steps**:
1. **YC Startup Trends**
```
execute("yc", "search", "search", {
"query": "AI OR machine learning OR artificial intelligence"
})
→ use get_page(cache_key, offset, limit) to collect up to 200 results
Group by batch to see:
- Trend over time
- Focus area shifts
- Team size changes
query_cache(cache_key, group_by="batch", aggregate={"field": "id", "function": "count"})
```
2. **Public Market Signals**
```
execute("sec", "search", "search", {
"query": "artificial intelligence"
})
→ use get_page(cache_key, offset, limit) to collect up to 50 results
Check 10-K mentions of:
- "AI" or "machine learning" frequency
- AI-related investments
- AI revenue segments
```
3. **Community Sentiment**
```
execute("reddit", "search", "search", {
"query": "AI trends 2026"
})
→ use get_page(cache_key, offset, limit) to collect up to 100 results
Analyze for:
- Excitement vs. concern
- Adoption barriers
- Use case validation
- Technology maturity
query_cache(cache_key, sort_by={"field": "score", "order": "desc"})
```
4. **Professional Discussion**
```
execute("linkedin", "post", "search_posts", {
"keywords": "artificial intelligence"
})
Check:
- Industry adoption
- Job market signals
- Skill requirements
- Thought leader opinions
```
5. **Web Intelligence**
```
For key AI companies:
execute("webparser", "parse", "parse", {"url": website + "/blog"})
→ Technology updates, product launches
```
**Expected OutpRelated in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.