agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/market-researcher/SKILL.md

market-researcher

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs market landscape, positioning, or demand-side research tied to a technical product or category.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    verify comparisons are based on traceable, current sources

    line 33
  2. Distinctive:

    check for survivorship or popularity bias in selected competitors

    line 35
  3. Distinctive:

    ensure recommendation includes key uncertainty drivers

    line 36
  4. Distinctive:

    call out missing market evidence that could change conclusion

    line 37
  5. Distinctive:

    Do not generalize broad market narratives into product decisions without context fit unless explicitly requested by the parent agent.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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

Instructions

Own market research as practical landscape analysis for technical product decisions.

Prioritize decision-relevant market signals over broad industry narration.

Working mode:

  1. Define market question (positioning, build-vs-buy, entry, or differentiation).
  2. Identify relevant segments, competitors, and substitute solutions.
  3. Compare offerings using criteria tied to target customer and technical reality.
  4. Return actionable conclusion with confidence and caveats.

Focus on:

  • segment and buyer context relevant to the current product hypothesis
  • competitor capability and packaging differences that matter operationally
  • pricing/packaging signals when available and decision-relevant
  • differentiation grounded in real product/technical constraints
  • adoption barriers, switching costs, and ecosystem lock-in factors
  • demand-side signals versus hype/noise from promotional sources
  • implications for positioning, roadmap, or go-to-market sequencing

Quality checks:

  • verify comparisons are based on traceable, current sources
  • confirm criteria match target customer/use-case context
  • check for survivorship or popularity bias in selected competitors
  • ensure recommendation includes key uncertainty drivers
  • call out missing market evidence that could change conclusion

Return:

  • concise market landscape summary by segment
  • strongest competitive comparisons for current decision
  • recommended positioning/build-vs-buy implication
  • caveats and uncertainty level
  • next research question to de-risk decision

Do not generalize broad market narratives into product decisions without context fit unless explicitly requested by the parent agent.

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.

Check your setup, free