Skip to content
cccskills
FreePublished on GitHub

market-research

Run market research, competitive analysis, investor due diligence, and industry scans. Use when the user wants market sizing, competitor comparisons, fund research, or tech scans.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Market Research

Make research that helps decisions, not research for show.

When to Use

  • Researching a market, company, investor, or tech trend
  • Building TAM/SAM/SOM numbers
  • Comparing competitors
  • Checking investor fit before outreach
  • Testing a thesis before building

Process

1. Pick the Research Type

Figure out which kind of research the user needs:

  • Investor / Fund Check
  • Competitor Check
  • Market Size
  • Tech / Tool Research

2. Run Investor / Fund Check

Get:

  • Fund size, stage, check size
  • Portfolio companies that matter
  • Public thesis and recent deals
  • Why they fit or don't fit
  • Red flags

3. Run Competitor Check

Get:

  • What the product really does (not marketing fluff)
  • Funding and investors
  • Traction if public
  • How they get users and what they charge
  • Strengths, weaknesses, gaps

4. Run Market Size

Use:

  • Top-down from reports
  • Bottom-up from real customer numbers
  • Show your math. Every guess should be clear.

5. Run Tech / Tool Research

Get:

  • How it works
  • Trade-offs and who's using it
  • How hard to set up
  • Lock-in, security, and risk

6. Write It Up

Structure every deliverable as:

  1. Quick summary (2-3 sentences)
  2. Key findings
  3. What this means
  4. Risks and caveats
  5. What to do next
  6. Sources

Rules

  • Every big claim needs a source.
  • Use recent data. Flag old data.
  • Include the bad news too. Show risks.
  • End with a decision, not just a summary.
  • Keep facts, guesses, and suggestions separate.
  • All numbers have sources or are marked as guesses.
  • Old data is flagged.
  • The suggestion follows from the facts.
  • Someone can make a decision from this.

Gotchas

  • Top-down TAM is lazy and always wrong. "10% of the $X billion market" is not analysis. Bottom-up from real customer numbers or go home.
  • Analyst reports have built-in bias. Reports from vendors (like AWS sizing the cloud market) overstate their own segment. Use independent sources.
  • Revenue proxies are unreliable. SimilarWeb traffic estimates can be off by 5x. Combine multiple signals: hiring, social, Crunchbase, app store rankings.
  • Don't confuse market size with addressable market. The CRM market is $80B, but if you're building for freelancers, your market is a fraction of that.
  • Recency matters. A market growing 40% in 2024 might be flat in 2026. Always check the latest data points, not just the headline number.

Output

Save to the project's 02-research/ folder.

Format each deliverable with: quick summary, key findings, what this means, risks and caveats, next steps, and sources.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Creates RPC-style endpoint following layered architecture (Controller → Manager → Repository). Use when creating new API endpoints or CRUD operations.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Run a structured brainstorm session for startup ideas. Takes a theme or problem and generates ideas with quick gut-checks. Use when the user wants to explore a space or generate new ideas.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Run real browser QA with Playwright. Use when testing a frontend feature, verifying UI before PR, smoke testing after deploy, or investigating reported visual bugs.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

CI/CD pipeline patterns for GitHub Actions, PR automation, and deployment workflows. Use when setting up CI, fixing broken pipelines, automating PR checks, or configuring deployment.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

See all skills by c0x12c

Report a problem with this skill