本文へ移動
cccskills
無料GitHub で公開

positioning-and-messaging

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.6 KB
  • references/sources.md952 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.
  • Objection handling — the four things prospects actually push back on, answered plainly.
  • Words to avoid — including the category terms that would frame you wrongly.

Testing it

Read the one-liner to someone in the target segment and ask what they think it does and who it is for. If they answer with your category but the wrong use case, the frame is wrong. If they answer with a competitor's name, the differentiation is not landing.

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

  • Position against a competitor the buyer has not heard of.
  • Widen the segment because the narrow one feels small. Diffuse positioning converts nobody.
  • Change the one-liner per channel. Channels change format, not meaning.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0332026年9月18日 更新

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 inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0332026年9月18日 更新

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. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0332026年9月18日 更新

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 script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0332026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0332026年9月18日 更新

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. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0332026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する