agentleFS
sametcelikbicaksametcelikbicak/opencode-team/skills/team-market-research/SKILL.md

team-market-research

Skill69 starsChanged 19 days agoMITView on GitHub

Market, competitor and user research methodology. Source verification, competitor table, niche analysis and risk assessment. The playbook of the analyst role.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Verify competitor names and prices with websearch: Do not write made-up competitor names, made-up prices or made-up market sizes.

    line 23
  2. Distinctive:

    Write the source next to every claim.

    line 33
  3. Distinctive:

    Do not compare prices only.

    line 37
  4. Distinctive:

    Leave unclear answers as "unclear".

    line 86

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Market and User Research

1. Frame the problem

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

QuestionAnswer
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:

DimensionQuestion
PriceWho it is for, which tier, what is included
Target segmentWho they target, who they do not
Main flowWhat the user does in the first 5 minutes
GapWhat they do not do (a missing feature = an opportunity)
Bad experienceWhere users struggle (the most valuable column)
Trust signalsSOC2, 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

RiskHow it is detectedEarly test
No problem (artificial demand)Nobody is paying money / wasting time right nowPayment intent test (pre-order form, "would you pay for this?")
Wrong segmentYou 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 pressureThe competitor already has this featureLook at the competitor's changelog, read their 12-month roadmap
No distribution channelNo access to the channel or it is too expensiveTest reaching 100 target users
RegulatoryGDPR/data tax/payment regulationSector scan

6. Decision table

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

QuestionAnswerEvidenceConfidence
Is the problem real?yes/no/unclearsourcehigh/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).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.