AGENTSOURCE

Field Manual / A Claude Code Skill for Positioning: The One That Argues Back

A Claude Code Skill for Positioning: The One That Argues Back

Field manual · last reviewed 2026-08-19

A positioning skill for Claude Code is a SKILL.md workflow that makes the agent interrogate you instead of agreeing with you, which is the failure mode of asking a model about positioning in a bare chat. AgentSource's Positioning Market Map is that skill: eight phases run one question at a time, producing exactly one file, docs/positioning.md, and no code. It opens with a hard gate — it refuses to position a product whose demand is unproven unless you explicitly override — on the logic that sharp positioning on an unwanted product is just a well-worded way to describe something nobody asked for. It requires a four-column competitor matrix (status quo, direct, adjacent, outsider), where the status-quo column is the one usually skipped and usually decisive, since most products lose to nothing changes rather than to a rival; every entry needs a name, one-liner, pricing anchor, what they get right, what they get wrong and where they are vulnerable, plus one sentence naming the vacuum all four leave open. It grades the niche as vertical x use case x stage, rejecting Marketing teams and B2B SaaS marketing teams as too broad while accepting Series-B B2B SaaS marketing teams running outbound on Apollo with under 5 SDRs. The UVP comes out in Geoff Moore form under three enforced rules: AI-powered is rejected as a mechanism, the unlike must be an entry that actually exists in the matrix rather than an invented strawman, and the agent must state whether the result is sharp or fuzzy and why — the phrase nice positioning is banned output. That anti-sycophancy clause is what a bare prompt structurally cannot provide. Its captured field report is the skill's own working material unpacked — the niche drill and the deliverable skeleton — rather than an invented sample company. One-time $9, or $29 in the Founder Kit alongside demand validation, Reddit growth, X growth, a product SEO site builder and an AI-visibility audit. Compatible with Claude Code, claude.ai & Codex.

Ask any capable model to help with your positioning and it will help. That is the problem. You describe the product, it tells you the idea is strong, and twenty minutes later you are holding a sentence like "for busy professionals who want to save time." Nothing in that sentence is false. Nothing in it is usable either — you cannot write an ad from it, you cannot pick a subreddit from it, and no stranger reading it can tell whether they are the customer.

The failure is not that the model is weak at positioning. It is that positioning is an interrogation, and a bare chat prompt has no reason to interrogate you. It has every reason to agree with you.

A positioning skill for Claude Code is a fixed process the agent follows instead of improvising a friendly one. This page is about the one AgentSource ships for that job — the Positioning Market Map, $9 — and, as with every skill on the shelf, its captured field report is readable before you pay.

What the skill actually changes

It is a plain-markdown SKILL.md workflow. It writes no code and scaffolds nothing. It produces exactly one file, docs/positioning.md, and it gets there through eight phases the agent runs one question at a time.

The one-question-at-a-time rule sounds like a small stylistic choice. It is the load-bearing one. A model asked six positioning questions at once will answer all six itself, plausibly, and hand you a finished document you never actually thought about.

The gate that runs before anything else

The skill refuses to position a product whose demand is unproven, unless you explicitly override it.

This is worth dwelling on, because it is the opposite of what a sales-minded tool would do. Sharp positioning on an unwanted product does not produce a business; it produces a very well-worded way to describe something nobody asked for. The skill wants evidence first — customer quotes, reviews, revenue, validation notes — and says so before it will start. If you have not done that work yet, the honest sequence is demand first, positioning second.

Four competitor columns, and the one everyone omits

Most competitor analysis is a list of rival tools. The skill requires four columns:

Column What it captures
Status quo The workaround in use today — a spreadsheet and email, a manual process, an agency
Direct Tools solving the same problem the same way
Adjacent Neighbouring tools that could expand into yours
Outsider Another industry's solution, an open-source project, a services player

The first column is the one that gets skipped and the one that usually wins. Most products do not lose to a rival; they lose to nothing changes. A matrix that omits the status quo will tell you that you are cheaper and faster than three competitors while the actual buyer keeps using their spreadsheet.

Each entry has to carry a name, a one-liner, a pricing anchor, what they get right, what they get wrong, and where they are vulnerable — and then one sentence naming the vacuum all four columns leave open. "What they get right" is a required field on purpose; a matrix where every competitor is bad is a matrix nobody researched.

The niche drill, graded

The skill defines a niche as the intersection of vertical × use case × stage, and grades answers against that. Its own examples, verbatim:

  • ❌ "Marketing teams" — not a niche
  • ❌ "B2B SaaS marketing teams" — still too broad
  • ✅ "Series-B B2B SaaS marketing teams running outbound on Apollo with <5 SDRs" — a niche

If your answer looks like the first two, the agent keeps asking. Most people stop at the second one and believe they have narrowed, because it is visibly narrower than the first.

A UVP it will not let you fudge

The final statement comes out in Geoff Moore's form, with six slots to fill:

For [the named ICP], who [pain, from evidence], we are [category], that [unique mechanism], unlike [an entry from the matrix], we [the wedge — falsifiable and measurable].

Three rules are enforced around it, and each closes a specific escape hatch:

  • "AI-powered" is rejected as a mechanism. It describes your stack, not what the product does differently.
  • The "unlike" must be an entry that exists in your matrix. No invented strawman competitor who is conveniently worse than you.
  • The agent must say whether the result is sharp or fuzzy, and why. The phrase "nice positioning" is banned output.

That last rule is the anti-sycophancy clause, and it is the part a bare prompt structurally cannot give you. A model that is free to praise your UVP will praise it.

What you actually get out

One draft-stamped file: the upstream read, an ICP one-pager written as a named human with a day shape and a buying committee rather than a category, the four-column matrix with the vacuum named, the business model with a pricing anchor and the path to dollar #1, the niche sentence with a defensibility note, the UVP, and the open questions it could not close. Then a revise loop.

The open-questions section matters more than it looks. A positioning doc with no open questions is usually a doc that guessed.

Where this sits against the alternatives, honestly

  • A free prompt or a directory download. Genuinely fine for a first pass, and free. What you tend not to get is the enforcement — the gates, the rejected answers, the banned phrases. Free skill files are also unverified by default, which is why the sensible habit is to read a skill's instructions before you install it, whoever it came from.
  • A positioning consultant. Better than any skill if you can afford one, because a good consultant brings judgement about your specific market. Different price bracket entirely.
  • A positioning book. Obviously Awesome and Crossing the Chasm are where this thinking comes from, and the skill is downstream of them rather than a replacement. A book cannot ask you a follow-up question when you answer "SMB owners."

The honest summary: this is the interrogation, encoded, run the same way every time. It is worth $9 if the thing you keep failing at is being specific under your own questioning — which is most people, because self-interrogation is the hardest kind.

Compatibility and install

It is plain markdown, so it runs anywhere a skill file runs. Claude Code picks it up from ~/.claude/skills/; on claude.ai you upload it to a Project; for Codex you reference it from AGENTS.md or a skills directory. Full steps ship in the QUICKSTART.

One-time $9, or $29 inside the Founder Kit alongside five other skills — demand validation, Reddit growth, X growth, a product SEO site builder, and an AI-visibility audit. No subscription; updates to the skill are included.

The field report on the product page is the skill's own working material unpacked — the niche drill and the deliverable skeleton — so you can read the exact process before deciding whether it is worth nine dollars.

QUESTIONS

Why not just ask Claude or ChatGPT about my positioning directly?

You can, and for a first pass it is fine. The structural problem is that a bare prompt has no reason to interrogate you and every reason to agree with you, so you tend to get agreeable mush — the 'for busy professionals who want to save time' class of answer. The skill's value is enforcement rather than knowledge: it asks one question at a time so the model cannot answer six questions on your behalf, it rejects category answers like 'SMB owners', it requires the 'unlike' in your UVP to come from your actual competitor matrix, and it forbids the agent from calling a fuzzy result nice. The underlying frameworks are public; the discipline is the product.

Does it write code or build anything?

No. By design it produces exactly one markdown file, docs/positioning.md, and scaffolds nothing. It is the thinking step before you build, so it deliberately has no overlap with a code-generation skill. The output is draft-stamped and set up for a revise loop rather than presented as final.

What do I need before I can run it?

Some demand evidence — customer quotes, reviews, revenue, or validation notes. The skill has a hard gate and refuses to position a product whose demand is unproven unless you explicitly override it. If you have not got that evidence yet, the honest order of operations is to validate demand first and position second, because sharp positioning on a product nobody wants does not fix the wanting problem.

What is the status-quo column and why does the skill insist on it?

It is the workaround your buyer uses today — a spreadsheet and email, a manual process, an agency, or simply nothing. It is the column most competitor analyses omit because it is not a company you can look up, and it is usually the real competitor: most products lose to 'nothing changes' rather than to a rival tool. A matrix without it can tell you that you beat three named competitors on price and speed while the actual buyer quietly keeps using their spreadsheet. The skill requires all four columns — status quo, direct, adjacent, outsider — and then one sentence naming the vacuum they collectively leave open.

What does the field report show, given the skill has no sample company?

It shows the gear itself rather than a worked example on an invented startup. The captured report unpacks the skill's own working material: the niche drill with its graded pass and fail answers, the full four-column competitor matrix with the six fields each entry must carry, the six-slot UVP form with the three rules enforced around it, and the deliverable skeleton of docs/positioning.md. That is a deliberate choice — a positioning example on a made-up company would tell you how well the writer invented a company, not what the skill makes your agent do on yours.

Does it work in claude.ai and Codex, or only Claude Code?

All three, because it is plain markdown with no runtime dependencies. Claude Code picks it up from ~/.claude/skills/, on claude.ai you upload it to a Project, and for Codex you reference it from AGENTS.md or a skills directory. Install steps ship in the QUICKSTART. There is no CLI installer for it — the install is a copy into a folder, which is worth knowing before you buy.

Is a $9 skill worth it when free positioning prompts exist?

Only if the thing you keep failing at is being specific under your own questioning. Free prompts and directory downloads cover the same frameworks and cost nothing, and a good consultant will beat any skill file because they bring judgement about your specific market — at a very different price. What the paid skill adds is the enforcement layer: gates, rejected answers, banned phrases, and a maintained file you get updates to. It is also worth reading any skill's instructions before installing it, free or paid, which is why the full field report is published before checkout.