researching-market

researching-market is a skill for Claude Code, Codex from qte77/claude-code-plugins. It costs 55 tokens per session (767 once invoked), scanned A, original, Apache-2.0.

A market-research workflow that combines a project's capabilities and competitor information to estimate market size, describe likely buyers, and identify signs of market opportunity. TAM, SAM, and SOM mean the total market, the part you can serve, and the part you could realistically win.

In plain words
What is it for?
Use it to size a market, create buyer personas, compare top-down and bottom-up estimates, and identify market-entry signals. It can also adapt the research depth and style to different planning approaches.
Why use it?
It brings technical and competitive research into one market view, while making assumptions and research sources explicit. This helps avoid unsupported market estimates and vague buyer descriptions.

Skill for Claude CodeCodex

Part of the market-research plugin — 8 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/qte77/claude-code-plugins/researching-market
Any agent
npx skills add qte77/claude-code-plugins --skill researching-market
Clone the repo
git clone --depth 1 https://github.com/qte77/claude-code-plugins

Made for: Claude Code, Codex.

Or install market-research, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for researching-market

README.md
[![agentmods](https://agentmods.dev/badge/skills/qte77/claude-code-plugins/researching-market.svg)](https://agentmods.dev/skills/qte77/claude-code-plugins/researching-market)
Your own site
<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/researching-market"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/researching-market.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 767 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00055 $0.00767
Opus 5 $0.00028 $0.00383
Sonnet 5 $0.00011 $0.00153
Haiku 4.5 $0.00006 $0.00077

Measured 4d ago against content hash 5fa0df510b5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

researching-market scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/market-research/skills/researching-market/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Researching Market (Phase 1B)

Target: $ARGUMENTS

Phase 1B of the GTM pipeline. Depends on Phase 0 and Phase 1A. Integrates technical capability and competitive intelligence into strategic market sizing and buyer analysis.

Mode Awareness

Read config/mode.md before starting:

  • concise — Top-down TAM estimate, one primary persona, bullet entry signals
  • detailed — Bottom-up + top-down sizing, 2-3 personas with full profiles, trend projections
  • conservative — Use published analyst figures, conservative growth rates
  • ambitious — Build bottom-up case for expansive TAM, highlight adjacencies

Inputs

  • results/phase-0/capability-profile.md — Source project capabilities
  • results/phase-1a/competitor-map.md — Competitive landscape
  • config/targets.md — Target market segments
  • config/comments_research.md — Research scope constraints
  • config/mode.md — Style and approach settings

Workflow

  1. Read Phase 0 and Phase 1A outputs — Synthesize capability and competitive signals
  2. Define addressable market — Scope TAM, SAM, SOM with methodology
  3. Size the market — Use cited sources; state assumptions explicitly
  4. Build buyer personas — Role, pain points, budget authority, buying triggers
  5. Assess entry signals — What evidence suggests this is the right moment to enter?
  6. Identify risks — Market timing, regulatory, adoption barriers
  7. Validate against criteria — Check config/validation_criteria.md Phase 1B gates

Output

Write to results/phase-1b/:

market-analysis.md

# Market Analysis

## Market Sizing

### TAM (Total Addressable Market)
- Estimate: $[X]B
- Methodology: [top-down / bottom-up]
- Source: [URL, year]

### SAM (Serviceable Addressable Market)
- Estimate: $[X]B
- Scope: [geography, segment, use case]

### SOM (Serviceable Obtainable Market — Year 1-3)
- Estimate: $[X]M
- Assumptions: [list]

## Growth Rate
- [X]% CAGR through [year] — Source: [URL]

## Buyer Personas

### Persona: [Name/Role]
- Title: [job title]
- Pain: [primary pain point]
- Budget authority: [Yes/No/Influence]
- Buying trigger: [what prompts purchase decision]

## Market Entry Signals
- [Signal] — Strength: [High/Medium/Low]

## Risks
- [Risk] — Likelihood: [H/M/L] — Mitigation: [approach]

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 93 lines · 55 tokens per session scan A 5fa0df510b5f

Subscribe to this mod's changes

researching-market is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 55 tokens to every session and 767 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

orchestrator

FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.

aleksandr-chaika/flutter-clean-arch-skills · 72 tokens

flutter-guide

Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.

aleksandr-chaika/flutter-clean-arch-skills · 39 tokens

maestro-flutter

Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.

aleksandr-chaika/flutter-clean-arch-skills · 41 tokens

android-kotlin-compose

Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…

and3r817/dot-claude-plugins · 84 tokens

android-kotlin-coroutines

Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…

and3r817/dot-claude-plugins · 87 tokens

codex-advisor

Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…

and3r817/dot-claude-plugins · 85 tokens