mcpbeat Sign in

Market Research Skill for Claude

Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.

612 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
265
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/loulanyue/awesome-claude-notes --skill market-research

The instruction itself

10 sections, as written by the author

Market Research

Produce research that supports decisions, not research theater.

When to Activate

  • researching a market, category, company, investor, or technology trend
  • building TAM/SAM/SOM estimates
  • comparing competitors or adjacent products
  • preparing investor dossiers before outreach
  • pressure-testing a thesis before building, funding, or entering a market

Research Standards

  • Every important claim needs a source.
  • Prefer recent data and call out stale data.
  • Include contrarian evidence and downside cases.
  • Translate findings into a decision, not just a summary.
  • Separate fact, inference, and recommendation clearly.

Common Research Modes

Investor / Fund Diligence

Collect:

  • fund size, stage, and typical check size
  • relevant portfolio companies
  • public thesis and recent activity
  • reasons the fund is or is not a fit
  • any obvious red flags or mismatches

Competitive Analysis

Collect:

  • product reality, not marketing copy
  • funding and investor history if public
  • traction metrics if public
  • distribution and pricing clues
  • strengths, weaknesses, and positioning gaps

Market Sizing

Use:

  • top-down estimates from reports or public datasets
  • bottom-up sanity checks from realistic customer acquisition assumptions
  • explicit assumptions for every leap in logic

Technology / Vendor Research

Collect:

  • how it works
  • trade-offs and adoption signals
  • integration complexity
  • lock-in, security, compliance, and operational risk

Output Format

Default structure:

  • executive summary
  • key findings
  • implications
  • risks and caveats
  • recommendation
  • sources

Quality Gate

Before delivering:

  • all numbers are sourced or labeled as estimates
  • old data is flagged
  • the recommendation follows from the evidence
  • risks and counterarguments are included
  • the output makes a decision easier

원문

  • 영문 원문

탐색

  • 한국어 문서 안내
  • 기여 가이드

Other skills for the same job

different authors, same section of the catalogue
Lead Research Assistant
by frostant
×8

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

2k tokens
Competitive Intelligence
by anthropics
vendor ×1

Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".

3k tokens
Amazon Product Research
by nexscope-ai
×1

Comprehensive product research and opportunity analysis for Amazon sellers. Analyzes demand, competition, profit potential, market entry barriers, and validates product ideas. Covers product sourcing, pricing strategy, and go-to-market planning. Use when the user asks about researching a product to sell, validating product ideas, product opportunity analysis, market research for Amazon, competition analysis, profit potential, should I sell this product, product viability, or any general product research questions.

3k tokens
Spin Selling
by guia-matthieu
×1

Master the consultative sales methodology trusted by enterprise sales teams worldwide. Use Neil Rackham's research-backed question sequence to uncover needs and close complex deals. Use when: **Complex B2B sales** with long sales cycles; **High-value deals** requiring multiple stakeholders; **Solution selling** where discovery is critical; **Enterprise sales** with sophisticated buyers; **Consultative positioning** to differentiate from competitors

5k tokens
Sop Product Launch
by ComeOnOliver
×1

Complete product launch workflow coordinating 15+ specialist agents across research, development, marketing, sales, and operations. Uses sequential and parallel orchestration for 10-week launch timeline.

7k tokens
Content Research Writer
by google
vendor

Content research and SEO writing methodology. Guides the agent through topic research, keyword identification, competitive analysis, and writing SEO-optimized content that ranks well and provides genuine value to readers.

838 tokens
Generate Sandbox Policy
by NVIDIA
vendor

Generate sandbox security policies from plain-language requirements and optional REST API documentation. Produces L4 or fine-grained L7 network policies and ordered network middleware configuration. Use for API access rules, middleware host selection, failure behavior, or built-in and operator-run middleware attachment. Trigger keywords - generate policy, create policy, update policy, change policy, sandbox policy, network policy, API policy, security policy, allow API, restrict API, network middleware, supervisor middleware.

13k tokens
Company Intel
by deanpeters

Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.

11k tokens

How to use it

Copy the folder

Take loulanyue/awesome-claude-notes-ko-kr-market-research from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.