Skip to content
Skills Library
Marketing & content · Writing

positioning

/positioning

Draft or revise the six-step positioning doc from company, competitor and persona facts. Use when positioning is missing, stale, or someone asks "how should we describe what we do.

Licence
MIT
Last repository change
01.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Draft or revise the six-step positioning doc from company, competitor and persona facts. Use when positioning is missing, stale, or someone asks "how should we describe what we do.

Original author description

Draft or revise the six-step positioning doc from company, competitor and persona facts. Use when positioning is missing, stale, or someone asks "how should we describe what we do.

How it works

  1. Inputs
  2. Steps
  3. Output
  4. Rules
Original SKILL.md headings · 36 lines, 326 words
SKILL.md preview
---
name: positioning
description: Draft or revise the six-step positioning doc from company, competitor and persona facts. Use when positioning is missing, stale, or someone asks "how should we describe what we do."
allowed-tools: Read Grep Glob Write
metadata:
  category: know-the-market
  external-copy: "false"
---

# Positioning

Build a positioning doc in six steps, starting from what buyers would do without you. The result replaces foundation/positioning.md only after a person approves it.

## Inputs

Load these before drafting:

- `foundation/company.md` for what the company sells and the facts it may state.
- `foundation/competitors.md` for the alternatives a buyer weighs.
- `foundation/personas.md` for who cares and what they want to hear.

The person asking may add new facts, such as a feature that shipped or a segment that's winning. Treat anything they add as a claim to confirm, not a fact.

## Steps

1. **Competitive alternatives.** List what a buyer does today without you, starting with the status quo. Pull from competitors.md.
2. **Unique attributes.** List what you have that the alternatives don't. Only attributes that company.md or the person asking supports.
3. **Value.** For each attribute, write what changes for the buyer. If an attribute has no value anyone would pay for, drop it.
4. **Who cares most.** Name the segment and persona where that value is sharpest. Point at icp.md and personas.md.
5. **Market category.** Name the category that makes the value obvious. Say what you're not, too.
6. **Relevant trends.** Add at most two trends that make the value more urgent. Each one needs a reason, not a statistic you can't source.
7. Write a one-sentence short version. It should hold up if a buyer reads only that.
8. Diff the draft against the current foundation/positioning.md and list what changed and why.

## Output

A markdown doc with the six numbered sections, the short version, and a "Changes from current" list. Tag each claim **[Fact]** when a foundation file supports it, **[Inference]** when it's your reasoning, or **[Unknown]** when nobody has confirmed it yet.

## Rules

- Don't overwrite foundation/positioning.md. Write the draft to `outputs/positioning-draft-<date>.md` and let a person replace the file.
- No numbers without a source in company.md or metrics.md.
- Compare against alternatives, not vendor flaws.

Versions

RepositoryScoreLicence
This page · rokoruwa/gtm-os-starter90MIT
octavehq/lfgtm100MIT
matteotitta/genesys-skills100MIT
tansuasici/claude-marketing-kit100MIT
matteotitta/genesys-skills100MIT
Sidsaladi9/persona-os100MIT
Infinite-Labs-AI/infinite-skills100MIT
gerstep/positioning-plugin100MIT
kaminoikari/product-playbook100MIT

Database snapshot: 13.11.2026 · package version 54071bef931b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100positioning-doc
    Write a product positioning document. Use when the user says "write a positioning doc", "positioning statement", "how should we position this product", "positioning for [product]", "we need to differentiate from competitors", "product positioning and messaging", "positioning…
  • 100product-positioning
    Creates complete positioning frameworks for products. Use when the user wants to 'position my product,' 'create positioning,' 'positioning framework,' 'competitive positioning,' 'how to differentiate,' or 'positioning statement.
  • 100positioning-framework
    Writes a positioning doc (target customer, alternatives, unique attributes, value, category, proof) from your materials, each choice justified. Use when "position our product", "positioning doc".
  • 100pm-positioning
    Create a Pragmatic Institute Positioning Document — describe a product by the market problems it solves (not features), for one persona in one segment. Use when the PM asks for positioning, messaging, "how do we describe/pitch this", an internal positioning doc, or a positioning…
  • 100messaging-positioning
    Builds positioning statements, value propositions, message houses, and persona-specific messaging. Use for positioning development or messaging refresh.
  • 90yao-positioning-skill
    Generate evidence-aware positioning reports for personal IPs, courses, products, services, brands, or companies by combining positioning theory, course-marketing analysis, user intent, competitor research, market demand, and verifiable advantages. Use when users ask for…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.