Agent skill

Market Entry

by cbrock84 in cbrock84/headcount

Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry…

MITAuto-check passedProduct & Project Management

Install Market Entry

skills CLI
$ npx skills add cbrock84/headcount --skill market-entry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount market-entry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/corporate-strategy/skills/market-entry .claude/skills/market-entry && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
market-entry
GitHub stars
2k
Token cost
~1.2k tokens
SKILL.md length
698 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry…

  • Tasks that involve Go-to-market strategy
  • SKILL.md covers Size from the bottom up, then…, Test whether the advantage…, Choose the entry mode against… and Scope the operating cost…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Market sizing

What it does

Market Entry is an agent skill from cbrock84/headcount. Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry, partnership and acquisition, sequencing the operational and regulatory work that entry actually requires, and setting the criteria that would tell you to stop. Use this to evaluate a new geography, segment or vertical, pressure-test an entry plan, or work out why a launched market never reached scale.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Product & Project Management, covering Go-to-market strategy and Market sizing. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Go-to-market strategy
  • Tasks that involve Market sizing

Example prompts

  • “Use the market-entry skill to decide whether and how to enter a new market — sizing demand from the bottom up rather than from a market report…”
  • “/market-entry”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Market Entry loads about 1.2k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 126 tokens; SKILL.md has 698 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~126
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 698 words, ~1,231 tokens.

Download SKILL.mdSave it as .claude/skills/market-entry/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
market-entry
description
Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry, partnership and acquisition, sequencing the operational and regulatory work that entry actually requires, and setting the criteria that would tell you to stop. Use this to evaluate a new geography, segment or vertical, pressure-test an entry plan, or work out why a launched market never reached scale.

Market entry

Entry decisions are usually made on the size of the opportunity and lost on the cost of serving it. The market was real; what was underestimated was everything required to operate there.

Size from the bottom up, then check it against the top down

A market report gives you a number that includes companies who will never buy from you. Build the estimate from countable things: how many organizations fit your profile, how many have the problem acutely, what they spend on it today, what share you could plausibly hold in a defined period.

Use a top-down figure only as a sanity check. If bottom-up and top-down differ by an order of magnitude, one of them contains an assumption nobody has stated, and finding it is the most valuable hour in the analysis.

Test whether the advantage actually transfers

The question is not whether the market is attractive — attractive markets are attractive to everyone, including incumbents already there. The question is what you have that wins.

Advantages transfer unevenly. Product capability usually transfers. Brand rarely does across geographies. Distribution and relationships almost never do. Cost structure may invert entirely. An entry justified by "we are strong in the adjacent market" needs to name the specific thing that carries over, and it is usually less than assumed.

Ask why the incumbent has not already done what you plan to do. Either they cannot, which is your advantage, or they have found it does not work, which is your warning.

Choose the entry mode against speed, control and reversibility

  • Organic — full control, slowest, and every local capability has to be built. Right when the advantage is the product and the market is reachable with your existing motion.
  • Partnership or distribution — fast and cheap, and you learn less. Right when local relationships are the barrier and you can accept less control of the customer relationship.
  • Acquisition — buys presence and capability immediately, at the highest price and with the integration risk. Right when time matters more than money and the target has something you cannot build quickly.

Ask what each mode costs to unwind. Organic entry can be stopped. A distribution agreement with a long term and exclusivity cannot, and a bad partner can foreclose the market for years.

Show full SKILL.md (321 more words)Show less

Scope the operating cost honestly, including the parts that are not strategy

This is where entry plans are optimistic. Entity setup and tax registration, employment obligations, data residency and privacy regimes, sector licensing, payment methods and currency, local-language support hours, contract terms that differ from your standard, and localized documentation.

Each is individually manageable and collectively a program. Get someone who has actually operated in the market to review the list before committing, because the item you have not thought of is usually the expensive one.

Sequence for a real test, not for a full launch

Enter narrowly enough that failure is affordable and informative: one segment, one channel, a small number of reference customers. A full launch commits the spend before you know whether the thesis holds.

Define what you are trying to learn and what result would count as the thesis failing. Entry without a disconfirming condition becomes a market you stay in because you are already there.

Set the stopping criteria before you start

Write down what would have to be true by when, and what you will do if it is not. Markets rarely fail loudly; they underperform quietly while absorbing management attention that the core business was producing better returns on.

Review against the criteria on the date, not when someone finally raises it.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Size a market from a published figure without building it up from countable units.
  • Justify entry on an advantage nobody has named specifically.
  • Sign an exclusive distribution agreement before you understand the market.
  • Enter without a written condition that would tell you to stop.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/corporate-strategy/skills/market-entry of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Market Entry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Market Entry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Market Entry this skillcbrock84/headcount2k—~1.2kAutomated safety check: PassMIT
Management ConsultantDogInfantry/claude-skill-management-consultant-B1136—~14kAutomated safety check: PassCustom licence
Business Modelagentii-ai/agentii-investment-intelligence207—~2.8kAutomated safety check: PassApache-2.0
Product Market Researcherchendongqi/OPB-Skills126—~561Automated safety check: PassNone
Startup Designferdinandobons/startup-skill1.2k—~8.1kAutomated safety check: PassMIT
Product Strategistnicepkg/auto-company1951 repos~2.4kAutomated safety check: PassNone

Similar skills

  • Management Consultant

    DogInfantry/claude-skill-management-consultant-B1

    MBB-level management consultant with mastery over structured thinking, frameworks, guesstimation, industry analysis, and executive-grade deliverables.

    136 GitHub stars~14k tokensUpdated 19 days ago
    Product & Project ManagementAuto-check passed
  • Business Model

    agentii-ai/agentii-investment-intelligence

    Business model classification, business model analysis, structural analysis of how a company makes money, product offering decomposition, distribution channel analysis, customer segment analysis…

    207 GitHub stars~2.8k tokensUpdated 11 days ago
    Product & Project ManagementAuto-check passed
  • Product Market Researcher

    chendongqi/OPB-Skills

    市场调研助手 - 专业的市场洞察与机会分析专家。适用场景:(1) 目标用户画像构建与细分,(2) 用户需求调研与痛点挖掘,(3) 市场规模测算与增长预测(TAM/SAM/SOM),(4) 市场机会识别与蓝海分析,(5) 市场进入策略与GTM规划,(6) 行业趋势分析与预测,(7) 市场细分与定位策略,(8) 用户访谈问卷设计

    126 GitHub stars~561 tokensUpdated 8 mo ago
    Product & Project ManagementAuto-check passed
  • Startup Design

    ferdinandobons/startup-skill

    Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.

    1.2k GitHub stars~8.1k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed
  • Product Strategist

    nicepkg/auto-company

    Expert product strategy covering market analysis, competitive positioning, go-to-market planning, and product-led growth.

    195 GitHub starsUsed in 1 repo~2.4k tokens
    Marketing & SEOAuto-check passed
  • Organic Growth Path Advisor

    deanpeters/Product-Manager-Skills

    Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.

    7.2k GitHub starsUsed in 2 repos~5.2k tokens
    Product & Project ManagementAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo
  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 23 days ago
    Auto-check passed
  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed
  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 23 days ago
    Auto-check passed
  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 23 days ago
    Auto-check passed
  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 23 days ago
    Auto-check passed

Questions about Market Entry

What does Market Entry do?

Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry…. Market Entry is an agent skill from cbrock84/headcount. Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry, partnership and acquisition, sequencing the operational and regulatory work that entry actually requires, and setting the criteria that would tell you to stop.

When should I use Market Entry?

Market Entry fits situations like: tasks that involve Go-to-market strategy; tasks that involve Market sizing.

How do I install Market Entry in Claude Code?

Run `npx skills add cbrock84/headcount --skill market-entry -a claude-code`. Or copy the skill folder (plugins/corporate-strategy/skills/market-entry in cbrock84/headcount) into .claude/skills/market-entry in your project. Claude Code loads it when a task matches its description.

How do I install Market Entry in Codex?

Run `npx skills add cbrock84/headcount --skill market-entry -a codex`. Or copy the skill folder (plugins/corporate-strategy/skills/market-entry in cbrock84/headcount) into .agents/skills/market-entry in your project. Codex loads it when a task matches its description.

Can I use Market Entry in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill market-entry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/market-entry, .gemini/skills/market-entry, .github/skills/market-entry and .opencode/skills/market-entry in your project.

What does Market Entry need to run?

SKILL.md names no scripts, command-line tools or credentials: Market Entry is instructions for the agent only.

Does Market Entry access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Market Entry safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Market Entry use?

Market Entry is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Market Entry use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 236 tokens, read only when the agent opens those files.

What are the alternatives to Market Entry?

Skills that share tags, products or a category with Market Entry: Management Consultant (DogInfantry/claude-skill-management-consultant-B1, 136 stars), Business Model (agentii-ai/agentii-investment-intelligence, 207 stars), Product Market Researcher (chendongqi/OPB-Skills, 126 stars) and Startup Design (ferdinandobons/startup-skill, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Market Entry?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.