market-entry-brief SKILL.md skillA
market-entry-brief from mia-ppp/pmm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mia-ppp/pmm-skills/market-entry-brief@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mia-ppp/pmm-skills
- Path
skills/market-entry-brief/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Oct 16, 2026
- First version recorded
- Sep 29, 2026
- Size
- 15,338 bytes
- Repository stars
- 54
- License
- MIT
When the user wants to evaluate candidate entry or size and score a new market before positioning work. Use when the user asks 'should we enter [market],' or mentions 'market entry,' 'new market,' 'expand into,' 'TAM for,' 'is [segment/region] worth it,' or 'market sizing.' Produces a go, explore, or pass recommendation with labeled TAM, SAM, and SOM, the buyer delta, constraints, and ranked entry risks. It is Rung 1 of the launch chain. For external market/category/opportunity research, see…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Market Entry Brief You decide whether a company should enter a new market, before anyone writes positioning. A market is a segment, a region, or both. Your output is a one-line recommendation, then the brief that earns it. In a broad expansion, this skill selects or sequences the candidate market segment. It does not silently choose the customer use case or a new product; those must be carried through the shared opportunity-discovery trace and handed to `go-to-market-strategy` for a commercial beachhead proposal. ## Modes **Exploratory entry evaluation:** for a PMC handoff on a candidate market, return source-linked findings on company-specific entry fit, feasibility and constraints relevant to the assigned question. Consume market-intelligence for external structure/category conditions/opportunity research and competitor-profiling for competitive landscapes/facts/changes. Reuse their findings without repeating their methods. Route buyer collection to customer-research and internal product truth to its human owner. Do not require sizing, a full scorecard, a Go/Explore/Pass call or approved candidate personas for this mode. Return the shared research …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_cfr55xq5nd25i4xk/a70ed7bcc85f57058cee4c7b2398bbe1f666431fe9be7d8ac51fd73ca3327886.json
Then /plugin install market-entry-brief@markdownregistry-cfr55xq5nd25i4xk in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mia-ppp/pmm-skills/market-entry-brief@sha256:a70ed7bcc85f5705The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cfr55xq5nd25i4xk)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mia-ppp/pmm-skills/market-entry-brief since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of market-entry-brief from somewhere else? Ask it: where did my market-entry-brief come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Sep 29, 2026 and Oct 16, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-16 | 8babe52 | 15,338 B | A | view · diff |
| v1.0.0 | 2026-10-03 | 1c35b81 | 14,767 B | A | view · diff |
| v1.0.0 | 2026-09-30 | f96aeae | 12,021 B | A | view · diff |
| v1.0.0 | 2026-09-30 | 2f6abba | 12,005 B | A | view · diff |
| v1.0.0 | 2026-09-29 | f70816e | 8,210 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/market-entry-brief/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15338 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mia-ppp/pmm-skills · 54 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cfr55xq5nd25i4xk GET https://markdownregistry.com/api/v1/resolve?ref=mia-ppp/pmm-skills/market-entry-brief GET https://markdownregistry.com/api/v1/blob/a70ed7bcc85f57058cee4c7b2398bbe1f666431fe9be7d8ac51fd73ca3327886
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.