Expert market research skill — from market sizing and competitive analysis through consumer research and professional consulting-grade reports with LaTeX formatting and visual generation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmarket-research-analysisExecute the skills CLI command in your project's root directory to begin installation:
Fetches market-research-analysis from manojbajaj95/claude-gtm-plugin and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate market-research-analysis. Access via /market-research-analysis in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
29
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
29
stars
Expert market research skill — from market sizing and competitive analysis through consumer research and professional consulting-grade reports with LaTeX formatting and visual generation.
Choose your workflow:
TAM = Total market demand at 100% market share
= (Total potential customer base) × (avg contract value)
Data sources: Gartner, Forrester, IBISWorld, government statistics, trade associations
SAM = Portion of TAM you can realistically serve
Apply filters: geographic constraints, product limitations, customer size constraints
Typically 5-20% of TAM
SOM = Realistic near-term market share (1-3 years)
Conservative benchmarks:
Year 1: 0.1-0.5% of SAM
Year 2: 0.5-2% of SAM
Year 3: 1-5% of SAM
Bottom-up = (realistic target customers) × (conversion rate) × (ACV)
If top-down SOM / bottom-up > 3x → revisit top-down assumptions
| Type | Definition | Example |
|---|---|---|
| Direct | Same product, same customer | Asana vs Monday.com |
| Indirect | Different product, same problem | Asana vs Excel |
| Substitute | Alternative way to address need | Asana vs consultants |
| Potential | Could enter market easily | Microsoft, Google |
Create a 2D matrix:
Plot all competitors. Look for gaps — unserved or underserved quadrants = market opportunity.
| Dimension | Key Questions |
|---|---|
| Political | Regulatory environment, trade policies |
| Economic | Growth rates, inflation, currency risks |
| Social | Demographics, consumer behavior shifts |
| Technological | Disruptive technologies, R&D activity |
| Legal | Compliance requirements, IP landscape |
| Environmental | Sustainability trends, regulations |
For competitive landscape: map competitors on BCG Matrix (market growth vs market share) to identify Stars, Cash Cows, Question Marks, Dogs.
Van Westendorp Pricing: Ask customers 4 questions to find optimal price point:
Plot cumulative % — OPP (Optimal Price Point) = intersection of "too expensive" and "too cheap."
Anti-pattern: Never use leading questions ("Don't you think our innovative product..."). Always include negative response options.
For qualitative research:
Generates consulting-grade reports (50+ pages) modeled on McKinsey, BCG, Gartner deliverables.
Front Matter (~5 pages): Cover page · Table of Contents · Executive Summary (investment thesis, key findings, top 5 recommendations)
Core Analysis (~35 pages):
| Chapter | Pages | Key Frameworks |
|---|---|---|
| Market Overview & Definition | 4-5 | Industry structure |
| Market Size & Growth | 6-8 | TAM/SAM/SOM, regional breakdown |
| Industry Drivers & Trends | 5-6 | PESTLE, driver impact matrix |
| Competitive Landscape | 6-8 | Porter's Five Forces, positioning matrix |
| Customer Analysis | 4-5 | Segmentation, customer journey |
| Technology & Innovation | 4-5 | Technology roadmap, adoption curve |
| Regulatory & Policy | 3-4 | Regulatory timeline |
| Risk Analysis | 3-4 | Risk heatmap, mitigation matrix |
Strategic Recommendations (~10 pages): Opportunity matrix · Implementation roadmap · Investment thesis
Back Matter (~5 pages): Methodology · Data tables · Company profiles · Bibliography
# Batch generate all core visuals
python scripts/generate_market_visuals.py \
--topic "[MARKET NAME]" --output-dir figures/
| Priority | Visual | Tool |
|---|---|---|
| 1 | Market growth trajectory | scientific-schematics |
| 2 | TAM/SAM/SOM concentric circles | scientific-schematics |
| 3 | Porter's Five Forces | scientific-schematics |
| 4 | Competitive positioning matrix (2×2) | scientific-schematics |
| 5 | Risk heatmap | scientific-schematics |
| 6 | Executive summary infographic | generate-image |
# Initialize project structure
writing_outputs/YYYYMMDD_HHMMSS_market_report_[topic]/
├── drafts/v1_market_report.tex ← use assets/market_report_template.tex as base
├── figures/
├── references/references.bib
└── final/
# Compile
cd drafts/
xelatex v1_market_report.tex && bibtex v1_market_report
xelatex v1_market_report.tex && xelatex v1_market_report.tex
Use \usepackage{market_research} (from assets/market_research.sty).
Colored box environments:
\begin{keyinsightbox}[Key Finding]...\end{keyinsightbox} % blue
\begin{marketdatabox}[Market Snapshot]...\end{marketdatabox} % green
\begin{riskbox}[Critical Risk]...\end{riskbox} % orange
\begin{recommendationbox}[Recommendation]...\end{recommendationbox} % purple
See assets/FORMATTING_GUIDE.md for complete LaTeX reference.
See assets/market_report_template.tex for the full report template.
scripts/generate_market_visuals.py — Batch visual generation for reportsassets/market_research.sty — LaTeX style packageassets/market_report_template.tex — Full report templateassets/FORMATTING_GUIDE.md — Complete LaTeX formatting referencereferences/report_structure_guide.md — Detailed chapter-by-chapter guidancereferences/data_analysis_patterns.md — Analysis patterns and common calculationsreferences/visual_generation_guide.md — Visual creation workflowsproduct-strategy-and-marketing — Market opportunity within product strategygo-to-market-strategy — Applying market research to launch planningpricing-strategy — Using market research for pricing decisionsMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend market-research-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
market-research-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
market-research-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in market-research-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
market-research-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend market-research-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
market-research-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend market-research-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in market-research-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: market-research-analysis is focused, and the summary matches what you get after install.
showing 1-10 of 52