Skip to main content
skill CX Codex

team-market-research — Claude Code skill: what it does, how to install

team-market-research is a Claude Code skill that structures market, competitor, and user research. Guides niche validation, source hierarchy checks, and product risk evaluations.

MIT ★ 71 updated 2026-11-13

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sametcelikbicak/opencode-team --skill team-market-research -a claude-code
Open on GitHub

What team-market-research does

The skill enforces an analyst methodology to evaluate business ideas before development begins. It starts by framing the pain point through four specific questions: target role, observed friction, current workarounds, and the timing rationale. If the timing cannot be justified, the skill documents it as an explicit risk.

Information gathering relies on a strict source ladder. Internal metrics and competitor documentation rank at the top, followed by user reviews from platforms like G2 or Reddit and search trends. Competitor names and pricing must be verified with websearch; unverifiable entries are discarded or marked accordingly. Competitor matrices track missing features and user pain points rather than pricing alone, capping comparison at six alternatives.

Output comes as a structured Markdown document under three pages. The workflow concludes with a decision table assigning confidence levels to each finding, keeping uncertain points explicitly labeled as unclear.

What it helps with

  • verify competitor pricing and features using web search
  • map customer pain points and existing alternatives
  • audit product niche viability across reach and demand metrics
  • structure competitor tables focused on user friction and missing gaps

Example prompts for the agent

  • Run market research for our invoicing tool using team-market-research
  • Analyze the competitive landscape and identify gaps in rival workflows
  • Evaluate our target niche and draft the final decision table

How to install team-market-research

1Skills CLI (Vercel)

npx skills add sametcelikbicak/opencode-team --skill team-market-research -a claude-code

2Manually: put the files in place

~/.claude/skills/team-market-research/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/team-market-research/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about team-market-research

How to install team-market-research in Claude Code?

Run npx skills add sametcelikbicak/opencode-team --skill team-market-research -a claude-code. The skill file will be placed at ~/.claude/skills/team-market-research/SKILL.md.

What does team-market-research do?

It directs the agent through an analyst playbook: framing problems, gathering verified data, evaluating competitors, and outputting a structured research report.

What is required for team-market-research to work?

The agent must have access to websearch to verify competitor claims, pricing tiers, and primary source materials.

Source text

SKILL.md · MIT
---
name: team-market-research
description: Market, competitor and user research methodology. Source verification, competitor table, niche analysis and risk assessment. The playbook of the analyst role.
---

# Market and User Research

## 1. Frame the problem

Answer these four questions; if you cannot answer them, the research has not started yet:

| Question | Answer |
|---|---|
| Who is in pain? | A concrete role ("a freelance graphic designer issuing 5-10 invoices a month") |
| What is the pain? | An observable behavior ("waiting weeks for payment, sending 3 reminders") |
| How do they solve it today? | The existing alternative (spreadsheet + email + WhatsApp) |
| Why now? | A timing rationale (a regulation change, a cost drop, a channel maturing) |

The "why now" answer is the hardest one. If it cannot be answered, write it up as a risk.

## 2. Source hierarchy

**Verify competitor names and prices with `websearch`.** Do not write made-up competitor names, made-up prices or made-up market sizes. Mark a competitor you could not verify as "unverifiable", or do not write it at all.

From strongest to weakest:

1. **Primary data**: your own sales/measurement data, support records, user interview notes, survey responses.
2. **The competitor's own material**: the competitor's pricing page, documentation, changelog, status page, support forum.
3. **Competitor user reviews**: G2/Capterra/Product Hunt/Reddit/HN — real expressions of pain live here.
4. **General search volume trend** (Google Trends) — the direction of demand.
5. **Secondary articles** — context only, never as the primary source.

Write the source next to every claim. A claim without a source is marked as an "estimate".

## 3. Competitor table

Do not compare prices only. The dimensions to compare:

| Dimension | Question |
|---|---|
| Price | Who it is for, which tier, what is included |
| Target segment | Who they target, who they do not |
| Main flow | What the user does in the first 5 minutes |
| Gap | What they **do not do** (a missing feature = an opportunity) |
| Bad experience | Where users struggle (the most valuable column) |
| Trust signals | SOC2, GDPR, data location, pricing model |

**The most valuable column is "bad experience".** Go where the competitor is in pain and be better there.

At most 6 competitors. More than that is noise.

## 4. Niche analysis

Think in combinations, not in a single dimension:

`[small segment] × [widespread problem] × [specific solution]`

Is the niche good? Apply this test:

- **Is it wide enough?** Are there 1000+ potential users?
- **Is it narrow enough?** Can you say something specific to them?
- **Is it reachable?** Which channel are they on, and what does it cost?
- **Is there a network effect** (user → user)? If so, growth happens on its own.

## 5. Risks

| Risk | How it is detected | Early test |
|---|---|---|
| No problem (artificial demand) | Nobody is paying money / wasting time right now | Payment intent test (pre-order form, "would you pay for this?") |
| Wrong segment | You are talking in general terms and nobody says "this is not for me" | Talk to 5 users, ask "how would this solve your problem?" |
| Competitive pressure | The competitor already has this feature | Look at the competitor's changelog, read their 12-month roadmap |
| No distribution channel | No access to the channel or it is too expensive | Test reaching 100 target users |
| Regulatory | GDPR/data tax/payment regulation | Sector scan |

## 6. Decision table

Research is not a document, it produces a **decision**. End with this table:

| Question | Answer | Evidence | Confidence |
|---|---|---|---|
| Is the problem real? | yes/no/unclear | source | high/medium/low |
| Is the segment right? | ... | ... | ... |
| Will the niche work? | ... | ... | ... |
| The biggest risk | ... | ... | ... |

Leave unclear answers as "unclear". Deciding nothing and then marking everything as "yes" is the most expensive mistake.

## Output format

Markdown. At most 3 pages. Sections: Problem and users / Market context / Competitor table / Opportunity and niche / Risks and open questions / Decision table.

In the user's language (Turkish or English).

© sametcelikbicak · MIT · sametcelikbicak/opencode-team

Similar skills

All skills for Marketing and content →

From the same set25

The whole set →
team-prd team-prd is a Claude Code skill that structures product requirements documents for version 1 releases. Defines scope boundaries and testable acceptance criteria. CX Codex +1 ★ 71repo stars team-qa team-qa is a Claude Code skill that turns acceptance criteria into tests and sets out a QA approach. It covers edge cases, key user journeys, and bug fixes. CX Codex +1 ★ 71repo stars team-ux team-ux is a Claude Code skill that writes structured UX design specifications covering user flows, screen states, component catalogs, accessibility rules, and mobile behavior. CX Codex +1 ★ 71repo stars team-marketing team-marketing is a Claude Code skill for planning product marketing and launches, from positioning to a publishing calendar. It guides requests for channel plans, launch copy, and measurable goals. CX Codex +1 ★ 71repo stars team-architecture team-architecture is a Claude Code skill for planning software architecture, from data models and API contracts to module boundaries and risks. It activates for architecture design requests. CX Codex +1 ★ 71repo stars team-security-review team-security-review is a Claude Code skill that enforces a strict security auditing playbook. It inspects authentication flows, access control, input handling, and secret leaks. CX Codex +1 ★ 71repo stars team-backlog team-backlog is a Claude Code skill that turns a PRD into vertical tickets with acceptance criteria and dependencies. It writes the approved plan to .team/03-backlog.md. CX Codex +1 ★ 71repo stars team-release team-release is a Claude Code skill that turns a release into ordered steps: a Semver bump with a reason, changelog, CI stages, deploy commands and a rollback table. It switches on when a project is ready to tag and ship. CX Codex +1 ★ 71repo stars

Project sponsors

Companies that keep this analytics open