본문으로 건너뛰기
cccskills
무료GitHub에 공개

positioning

Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Positioning

Decide what you are, who it's for, what they'd use instead, and why you're the better choice, in words a buyer understands in five seconds. The method follows the public April Dunford school: start from the competitive alternatives buyers actually consider, and build out from there.

When to use it

  • The homepage doesn't explain what you do, or demos start with "so what is it exactly?".
  • You're choosing between going broad and niching down.
  • A new product, a new segment, or a competitor that moved.

Don't use it for taglines, value props or a full messaging library (/messaging, which runs after this), or for research you haven't done yet.

Inputs

Required: company name, a short description and the website URL.

Recommended: context/icp/, context/competitors/, context/win-loss/ and context/expert-pov/. Positioning without ICP and competitor evidence is opinion. If those are missing, say so, run what you can, and offer /icp-research and /competitor-research first.

Paths. Write to context/positioning/MMYY-positioning.md. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.

Steps

  1. Read the current state. Fetch the homepage, pricing and about pages. Run the five-second test: do the headline and sub-headline say what it is and who it's for? Note the category, differentiation and ICP the site claims today.

  2. Map the alternatives. What would a buyer do if you didn't exist?

    • do it manually
    • keep a legacy tool
    • buy a direct competitor
    • stretch an adjacent tool
    • do nothing
    • build it with a general AI assistant

    Rank them by how often they show up in deals.

  3. Map the anchors. What could the positioning hang on?

    • an activity
    • a product category
    • a use case
    • a problem
    • a persona
    • a competitive alternative ("the X alternative for Y")

    Score the promising combinations on clarity, differentiation and relevance to the ICP.

  4. Make the binary choice. Category-led (buyers already know the category and you win inside it) or problem-led (the category is new, crowded or wrong, so you lead with the pain). Use an activity anchor only when no software category fits.

  5. Lay out the options. Take the top 2 to 4 combinations (3 by default) and work each one up:

    • primary and secondary anchor
    • a hero headline and sub-headline
    • the value in three parts: category, problem, differentiation
    • who it's for
    • the bet it makes
    • the risks

    Each option must change the anchor or the binary choice. No rewording of the same bet.

  6. Build the comparison canvas. One column per option, rows for clarity, differentiation, ICP relevance, proof available, competitive exposure and risk. Mark each cell's confidence: verified, inferred, estimated or unknown. Recommend one and name the trade-off each option forces. The user decides.

  7. Lock the chosen option. Up to three differentiators, each one a thing you'd guarantee with money on the line (pass, partial or fail). Name the primary competitive alternative and the market focus, with simple TAM maths (average deal size × customers needed).

  8. Run the clarity ladder. Compress the position to one word, one phrase, one sentence and one paragraph. If a level fails, go back to the anchors.

  9. Write the positioning statement in the form that fits the anchor:

    • Use case: "We help [persona] [do the job] without [friction], by [approach]."
    • Category: "We are a [category] that [differentiator], unlike [alternative] which [weakness]."
    • Alternative: "We're the [leader] alternative that [upgrade], for [persona] who [unmet need]."
    • Activity: "We help [persona] [do activity], replacing [manual process] with [mechanism]."
  10. Map the implications. What changes for messaging, for the ICP, and which channel leads with which facet (homepage: primary anchor; comparison pages: the alternative; case studies: proof that matches the anchor).

  11. Hand off to /messaging.

Output shape

Open with a TLDR (the one-sentence position) and one block of open decisions. Then: current state, alternatives, the options with the canvas, the committed position (anchors, differentiators with guarantee verdicts, statement, clarity ladder), implications, and sources. Each caveat is stated once.

What good looks like

  • A stranger reads the hero and knows what it is and who it's for in five seconds.
  • No more than three differentiators, each one provable.
  • The comparison set matches the buyer. Compare to other vendors only when buyers already use the category.
  • The options are real choices, not three phrasings of one idea.
  • The TAM maths is realistic, not hopeful.

Mistakes to avoid

  • "The platform for X" with nothing else.
  • "AI-powered" as the main differentiator.
  • Inventing a category nobody searches for.
  • Choosing the position before mapping the alternatives.
  • Differentiators you couldn't prove to a sceptical buyer.

Chain

Part of the free five-skill chain: /icp-research → /competitor-research → /tov-guidelines → positioning → /messaging. The other six context skills (company context, win-loss, founder POV, brand kit, funnel and goals) are in the paid context plugin ($19.99, link in the README).

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Researches one B2B SaaS competitor across 13 dimensions (company, product, ICP, pricing, reviews, content, launches, search and AI visibility, tech stack, hiring, go-to-market, social, paid ads) and writes a sourced dossier with an executive summary, a threat level, strengths and weaknesses, and a data gaps section. Run it once per competitor, then compare. Triggers: "competitor analysis", "competitor research on", "what is [competitor] doing", "compare us to", "competitive landscape", "battlecard prep". Run after /company-context and /icp-research. Not for researching your own company (use /company-context).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

matteotitta/repo-structure-in-house672026년 10월 21일 업데이트

Builds an ideal customer profile from evidence: case studies, testimonials, customer logos, solutions pages, reviews and any sales notes you have. Produces market sizing layers, firmographic segments, a champion and an economic buyer persona, a negative ICP, intent signals, customer proof points and a voice-of-customer section in the buyers' own words, every claim sourced. Triggers: "ICP research", "ideal customer profile", "who are our customers", "customer segments", "buyer personas", "who should we target". Run after /company-context. Not for competitor analysis (use /competitor-research) or call transcript patterns (use /win-loss).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

matteotitta/repo-structure-in-house672026년 10월 21일 업데이트

level

무료

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

matteotitta/repo-structure-in-house672026년 10월 21일 업데이트

messaging

무료

Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

matteotitta/repo-structure-in-house672026년 10월 21일 업데이트

Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

matteotitta/repo-structure-in-house672026년 10월 21일 업데이트

matteotitta의 스킬 모두 보기

이 스킬의 문제 신고