positioning-and-messaging skillA
positioning-and-messaging is agent-read markdown (skill) from cbrock84/headcount: Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits. Use this when messaging is inconsistent across channels, when prospects misunderstand what the product does, when entering a new segment, when competitors are being compared against you unfavorably, or before any campaign, launch, or site rewrite..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Positioning and messaging Positioning is upstream of everything. A campaign built on unsettled positioning optimizes the wrong sentence. ## The five decisions 1. **Competitive alternative** — what the buyer does today if you do not exist. Often a spreadsheet or an intern, not a competitor. 2. **Unique attributes** — what you have that the alternative does not. Features, factual. 3. **Value** — what those attributes let the customer do that they could not before. Not the feature; the consequence. 4. **Who cares most** — the segment for whom that value is urgent rather than pleasant. Narrower than comfortable. 5. **Market frame** — the category you ask to be judged in. This sets every expectation the buyer brings, including on price. Get these in order. Most positioning failures are step 5 done first: picking an exciting category and reverse-engineering the value. ## Messaging that inherits from it - **One-liner** — what it is, for whom, instead of what. No adjectives that a competitor could not also claim. - **Three pillars** — the value claims, each with proof attached. A claim with no evidence is a slogan. …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/positioning-and-messaging@git:20260916.e72e404mdr add cbrock84/headcount/positioning-and-messaging@sha256:1273f73a1bc312d0Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_szdrlrw5fgujtk7i)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 2,642 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 2,303 B | A | view |
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 (2642 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
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_szdrlrw5fgujtk7i GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/positioning-and-messaging GET https://markdownregistry.com/api/v1/blob/1273f73a1bc312d03c4c0e78521256f2768e29a3f9e64084bd5fa82657a12cd5
Your agent 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.