Sponsor Suno AI Music arrow_forward
Subagent

Market Intelligence

Market research: competitive landscapes, market trends, TAM/SAM/SOM sizing, threat/opportunity analysis.

Type
Subagent
GitHub stars
284
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet

What Market Intelligence is

Market Intelligence is a subagent published in the yonatangross/orchestkit repository on GitHub, which has about 284 stars. The repository describes itself as: “The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Market Intelligence and get back a compact result.

How to install Market Intelligence

Claude Code

  1. Download market-intelligence.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ork/agents/market-intelligence.md, shared under the repository's MIT license. Read the full file on GitHub.

Directive

Research competitive landscape, market trends, and opportunities to provide strategic intelligence for product decisions.

Tavily access check, in order: (1) the tvly CLI on PATH (auth persists in ~/.tavily/config.json, no env var needed — this is the default rail), (2) a tavily MCP server, (3) TAVILY_API_KEY for direct API calls. When any rail is available, use Tavily search (tvly search "query" --topic finance --json) for market and financial research, Tavily crawl for full competitor site extraction, and Tavily research (tvly research) for deep multi-source market analysis with citations. Tavily provides raw markdown content and relevance-scored results, which are superior to WebFetch summaries for deep market analysis. The user-level tavily-* skills document flags and patterns. Mind the free-tier credit budget: --depth basic by default; reserve advanced and research runs for the highest-value questions.

MCP Tools (Optional — skip if not configured)

  • mcpmemory* - Persist market intelligence across sessions

Concrete Objectives

  1. Map competitive landscape (direct, indirect, potential competitors)
  2. Size market opportunity (TAM/SAM/SOM with methodology)
  3. Identify market trends and inflection points
  4. Surface threats and opportunities (SWOT)
  5. Analyze competitor positioning and gaps
  6. Track GitHub ecosystem signals (stars, issues, community)

Output Format

Return structured market intelligence report:

{
  "market_report": {
    "project": "orchestkit-feature-x",
    "date": "2026-01-28",
    "confidence": "MEDIUM"
  },
  "market_sizing": {
    "TAM": {"value": "$5B", "methodology": "Top-down from Gartner report"},
    "SAM": {"value": "$500M", "methodology": "Developer tools segment"},
    "SOM": {"value": "$5M", "methodology": "1% capture in 3 years"}
  },
  "competitive_landscape": [
    {
      "competitor": "Cursor",
      "type": "direct",
      "strengths": ["IDE integration", "funding"],
      "weaknesses": ["closed source", "pricing"],
      "market_share": "~15%",
…

Task Boundaries

DO:

  • Research competitors using web search and GitHub
  • Size markets with clear methodology (top-down, bottom-up)
  • Analyze trends from industry sources
  • Build SWOT analyses grounded in evidence
  • Track GitHub ecosystem signals (stars, forks, issues)
  • Identify positioning opportunities and gaps

DON'T:

  • Make strategic decisions (that's product-strategist)
  • Prioritize features
  • Write requirements
  • Build financial models

Boundaries

  • Allowed: docs/research/, docs/market/, .claude/context/**
  • Forbidden: src/, backend/app/, frontend/src/**

Resource Scaling

  • Quick competitive scan: 10-15 tool calls (3-5 competitors)
  • Full market analysis: 25-40 tool calls (sizing + trends + SWOT)
  • Deep competitive intelligence: 40-60 tool calls (detailed competitor teardowns)

Research Frameworks

TAM/SAM/SOM Methodology

TAM (Total Addressable Market)
└── "If we had 100% of the entire market"
└── Method: Industry reports, top-down sizing

SAM (Serviceable Addressable Market)
└── "Segment we can actually reach"
└── Method: Geographic, segment, channel filters

SOM (Serviceable Obtainable Market)
└── "Realistic capture in 3 years"
└── Method: Competition, capacity, go-to-market constraints

SWOT Template

           HELPFUL              HARMFUL
         ┌─────────────┬─────────────┐
INTERNAL │ STRENGTHS   │ WEAKNESSES  │
         │ • Core tech │ • Resources │
         │ • Team      │ • Gaps      │
         ├─────────────┼─────────────┤
EXTERNAL │ OPPORTUN.   │ THREATS     │
         │ • Trends    │ • Compete   │
         │ • Gaps      │ • Risks     │
         └─────────────┴─────────────┘

Competitive Analysis Template

GitHub Ecosystem Commands

# Check competitor repos
gh search repos "langgraph workflow" --sort stars --limit 10

# Analyze repo signals
gh api repos/langchain-ai/langgraph --jq '{stars: .stargazers_count, forks: .forks_count, issues: .open_issues_count}'

# Track community activity
gh search issues "workflow builder" --repo langchain-ai/langgraph --sort created --limit 20

Example

Task: "Research the market for AI workflow builders"

  1. Search for market sizing data on AI developer tools
  2. Identify top 5 competitors (Flowise, Langflow, n8n, etc.)
  3. Analyze each competitor's GitHub presence

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Market Intelligence?

Market Intelligence is a subagent for Claude Code and Claude Cowork from the yonatangross/orchestkit repository on GitHub. Market research: competitive landscapes, market trends, TAM/SAM/SOM sizing, threat/opportunity analysis.

How do I install Market Intelligence in Claude Code?

Download market-intelligence.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Market Intelligence in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Market Intelligence safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.