agentleFS
matteotittamatteotitta/genesys-skills/skills/positioning/SKILL.md

positioning

Skill53 starsChanged 5 days agoMITView on GitHub

Works out a B2B SaaS company's positioning: maps anchors and competitive alternatives, scores options, presents 2-3 positioning bets side by side, then locks the chosen one into a positioning statement. Use when asked for positioning, a positioning statement or how to stand out.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use level.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dachi-jp3Skill

    level

    表示レベル(auto / low / medium / high)を切り替える。

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT invoke when the user wants landing page copy, a full messaging library, competitor research only, or ICP research only.

    line 20
  2. Distinctive:

    If inputs missing: Ask for website URL. Identify founder type early (customer-focused / technology-focused / competition-focused) — drives …

    line 34
  3. Distinctive:

    Map strategic implications: Document what each decision implies for messaging direction, ICP sharpening, competitive counter-positions.

    line 45
  4. Very specific:

    Compose output: Use template at the premium reference (scenarios mode / --scenarios: use the premium reference).

    line 46
  5. Distinctive:

    Use Case: "We help [persona] [accomplish use case] without [key friction] — by [differentiated approach]."

    line 48
  6. Distinctive:

    Self-evaluation: Run completeness, evidence, guardrail checks.

    line 52
  7. Very specific:

    Suggest chain: If approved: "Want me to run product-messaging next?" Tight coupling.

    line 54
  8. Distinctive:

    All differentiators have guarantee test verdicts (Pass / Fail / Partial)

    line 66

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

B2B positioning strategy

Develop clear, defensible positioning for B2B SaaS products. Synthesizes ICP + competitor + brand context into a binary strategy choice (category vs problem), primary/secondary anchors, defensible differentiators, and a positioning statement that survives the 5-second clarity test.

When to run

Invoke when the user says:

  • "Help me position [product/company]" / "Positioning strategy for [company]"
  • "What category should we be in?" / "How do I differentiate from [competitor]?"
  • "Our homepage isn't converting" / "Our messaging is confusing"
  • "Should we niche down or go broad?" / "How do I explain what we do?"
  • "Multi-product positioning help"
  • "Give me positioning options / scenarios" / "What are the decisions to make on positioning?" → scenarios mode (N fully-worked bets + canvas + recommended pick)

Do NOT invoke when the user wants landing page copy, a full messaging library, competitor research only, or ICP research only.

Inputs

Required:

  • Company/product name and basic description
  • Website URL (accessible, fetchable)

Recommended (improve quality):

  • Buyer personas or ICP notes → sharpens persona + problem anchors
  • Competitor notes → enables competitive alternative mapping
  • Win/loss notes or call transcripts → real decision criteria, objections
  • Sales feedback → what's working in conversations

If inputs missing: Ask for website URL. Identify founder type early (customer-focused / technology-focused / competition-focused) — drives the approach sequence.

Steps

Mode: Phase 3 presents the top-N anchor combinations as positioning options + a comparison canvas (the scenarios / decisions-to-make step), then collapses to the option the client picks and runs the validation steps on it. --scenarios[=N] emits just the options + canvas standalone (a good closer for a competitor deck); default N=3. The single-committed-position outcome and the downstream contract are unchanged once a pick is made. → see the premium reference

  1. Phase 1 — Discovery & current state. Fetch website (homepage, pricing, about, product). Apply 5-second clarity test on H1+H2. Identify founder type. Extract current category / differentiation / ICP / problem claimed. → see the premium reference
  2. Phase 2 — Anchor & alternative mapping. Map 6 anchor types (Activity, Product Category, Use Case, Problem, Persona, Competitive Alternative). Map 5 alternative types (Manual/DIY, Legacy incumbent, Direct competitor, Adjacent tool, Status quo). Run Esner Decision Tree (Framework 13) to get a starting hypothesis. Score top combinations on Clarity / Differentiation / Relevance. Classify market maturity (emerging vs mature). → see the premium reference
  3. Phase 3 — Present scenarios, decide, commit. Take the top-N scored anchor combinations from Step 2.4 (default 3) and expand each into a fully-worked positioning option: concrete hero H1/H2, primary + secondary anchors with type labels, value triad (category / problem / differentiation), secondary angle archetype (Framework 14: Niche / Low-Cost / Premium / Unique Attribute / Lite — max 2), thesis, and risks. Each option must shift its primary anchor or binary strategy — no two options that are the same bet reworded. Assemble the comparison canvas (one column per option; confidence dot per cell mapped to VERIFIED/INFERRED/ESTIMATED/UNAVAILABLE). Mark a recommended pick and name the trade-off each option forces. Present as decisions to make → client picks one. Then collapse to the chosen option: lock its binary strategy (category vs problem), anchors, and 2-3 defensible differentiators (delivery / guarantee / focus / proprietary); determine market focus with TAM math; pick the primary competitive alternative. → see the premium reference + the premium reference
  4. Run clarity ladder. (On the committed option once a scenario is picked.) Compress positioning to 1 word, 1 phrase, 1 sentence, 1 paragraph. If any level fails, revisit anchor or differentiator selection.
  5. Run guarantee test. For each differentiator: would you guarantee with money on the line? Verdict Pass / Fail / Partial. Cross-reference proof type per anchor (Framework 15: Activity → Before/After, Use Case → Workflow + Outcome, Category → Comparative, Competitive Alt → Switch/Upgrade).
  6. Map strategic implications. Document what each decision implies for messaging direction, ICP sharpening, competitive counter-positions. If competitor notes are available, include voice calibration. These implications guide the messaging, persona and tone-of-voice work that follows.
  7. Compose output. Use template at the premium reference (scenarios mode / --scenarios: use the premium reference). Anchor-specific positioning statement template:
    • Activity: "We help [persona] [do activity] — replacing [manual process] with [product mechanism]."
    • Use Case: "We help [persona] [accomplish use case] without [key friction] — by [differentiated approach]."
    • Product Category: "We are a [category] that [key differentiator] — unlike [competitive alternative] which [weakness]."
    • Competitive Alternative: "We're a [leader]-alternative that [key upgrade] — for [persona] who [unmet need]."
  8. Channel emphasis guidance. Same positioning, different facet leads per channel: homepage → primary anchor; thought leadership → Activity/Use Case; comparison pages → Competitive Alternative; sales discovery → Use Case/Activity; case studies → proof type matching primary anchor.
  9. Self-evaluation. Run completeness, evidence, guardrail checks. Surface improvements. → see the premium reference
  10. Review gate (Level 2). Present full strategy + decisions. Approve or iterate.
  11. Suggest chain. If approved: "Want me to run product-messaging next?" Tight coupling.

Frameworks reference (15 total): all detailed in the premium reference. Anti-patterns + gotchas: the premium reference. Changelog + MCP integration: the premium reference.

What good looks like

Evaluations

  • 5-second clarity test passes (H1+H2 answer "which tools" or "which tasks")
  • Decision tree hypothesis recorded AND validated against scoring matrix
  • Secondary angle archetype selected from Framework 14 (max 2)
  • Clarity ladder passes at all 4 levels (word / phrase / sentence / paragraph)
  • All differentiators have guarantee test verdicts (Pass / Fail / Partial)
  • Proof types align to primary anchor per Framework 15
  • No "platform for X" alone, no invented categories, no "AI-powered" as primary differentiator
  • ≤3 differentiators (focus discipline)
  • Activity anchor used only when no software category exists
  • TAM math is realistic (ACV × customers needed) — not hopeful thinking
  • Strategic implications mapped for messaging, ICP, competitive (and voice if competitor data available)
  • Scenarios mode: exactly N options (default 3, range 2-4), each with a distinct primary anchor or binary strategy (no bet reworded)
  • Scenarios mode: every option has a concrete hero H1+H2 (not a placeholder), a thesis, and a risks list
  • Scenarios mode: canvas present, one column per option, a confidence dot on every cell mapped to VERIFIED/INFERRED/ESTIMATED/UNAVAILABLE (no all-green canvas)
  • Scenarios mode: recommendation framed as decisions to make with the trade-off per option named — not a forced single answer

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.