product-positioning
Skill3 starsChanged 8 months agoMITView on GitHub
定位產品/功能的市場位置和溝通策略。輸入產品描述/目標用戶/競品,輸出 positioning statement + one-liner + elevator pitch + landing page 骨架。當用戶要介紹產品、寫 README、準備 pitch 時使用。
5 other projects use a version of this.
Adopted by
Most recently taken up by
- brainbytes-dev/everything-claude-marketingtheir own version, first seen Nov 1, 2026
- realjaymes/marketingagentskillstheir own version, first seen Oct 21, 2026
- Akshit1018/product-positioning-skilltheir own version, first seen Oct 9, 2026
- chuhaiqu/skillstheir own version, first seen Aug 10, 2026
- DojoGenesis/openclaw-plugintheir own version, first seen Feb 13, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- realjaymes/marketingagentskills★ 68same name
- chuhaiqu/skills★ 22same name
- brainbytes-dev/everything-claude-marketing★ 9same name
- Akshit1018/product-positioning-skill★ 1same name
- DojoGenesis/openclaw-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- architecture-diagramSkill
- case-studySkill
- csv-to-chartSkill
- cv-optimizeSkill
- db-edaSkill
- demo-storytellingSkill
- disk-cleanupSkill
- drawioSkill
- generate-imageSkill
- gh-issue-to-specSkill
- json-validateSkill
- log-triageSkill
- markdown-link-checkSkill
- pdf-to-summarySkill
- postmortemSkill
- proposal-reviewSkill
- roundtableSkill
- vendor-evalSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 221
Use the actual current year.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
產品定位器
目標
定義一個產品/功能/side project 的市場定位,產出可直接使用的溝通素材。從模糊的「我做了一個東西」變成清晰的「這是什麼、給誰用、為什麼比現有方案好」。
不適用場景
- 產品還在發想階段(連 prototype 都沒有)→ 先去做
- 已經有明確定位,只需要文案 → 直接寫,不用跑定位流程
- 大型企業級產品定位(需要市場調研團隊)→ 這個 Skill 適合個人/小團隊
輸入
從 $ARGUMENTS 或對話中取得:
| 欄位 | 必填 | 說明 |
| 產品/功能 | 是 | 名稱 + 一句話描述 |
| 目標用戶 | 否 | 預設:由分析決定 |
| 替代方案 | 否 | 競品、現有做法、人工方式 |
| 已有素材 | 否 | 現有 README、介紹文、landing page URL |
若缺必填欄位,直接問用戶。
Decision Model
Step 1: 理解產品本質
回答以下 5 個核心問題(用戶回答不出來的,Skill 幫想 + 標記待驗證):
| # | 問題 | 目的 |
| 1 | 這東西做什麼?(動詞開頭) | 功能核心 |
| 2 | 誰最需要這個? | 目標用戶 |
| 3 | 他們現在怎麼做? | 替代方案 |
| 4 | 用了這個之後有什麼不同? | 價值主張 |
| 5 | 為什麼是你來做? | 可信度 / 護城河 |
Step 2: 競品 / 替代方案掃描
搜尋關鍵字:
{產品類別} tools {current_year}— 看市場上有什麼{產品類別} alternatives— 找替代方案{產品名} vs— 看有沒有人比較過
整理出 2x2 定位圖的兩個軸(例:簡單↔複雜、免費↔付費、通用↔專用)。
預設軸選擇(資料不足時):
- X 軸:簡單↔複雜
- Y 軸:通用↔專用(side project 常用)或 免費↔付費(商業產品常用)
- 標記為「待驗證」,等用戶確認
Step 3: 選定品類和差異化
品類選擇(你的產品「是什麼」):
- 選擇用戶已經理解的品類(降低認知成本)
- 如果是全新品類,用「像 X 但 Y」的公式
差異化類型(從以下選最強的 1-2 個):
| 類型 | 說明 | 適合 |
| 速度 | 比現有方案快 N 倍 | 有明確數字時 |
| 簡單 | 比現有方案簡單 | 競品太複雜時 |
| 專注 | 只做一件事但做到最好 | 競品太通用時 |
| 整合 | 串接了別人沒串的東西 | 你的獨特 workflow |
| 觀點 | 用不同方式解決同個問題 | 有獨特技術選擇時 |
| 價格 | 免費 / 更便宜 | side project 常用 |
Step 4: 產出 Positioning Statement
使用標準格式:
For [目標客群]
who [有什麼問題/需求]
[產品名] is a [品類]
that [核心價值/做什麼]
Unlike [主要替代方案]
[產品名] [關鍵差異化]驗證標準:
- 每一行都能通過「真的嗎?」測試
- 差異化不是「更好」而是「不同」
- 目標客群夠具體(不是「所有人」)
Step 5: 產出訊息層級
三層訊息,適應不同注意力長度:
| 層級 | 長度 | 用途 | 風格 |
| L1 | 一句話(<15 字) | bio / tagline / 名片 | 動詞開頭、無技術名詞 |
| L2 | 三句話(<50 字) | README 開頭 / 電梯內 | 痛點 + 方案 + 結果 |
| L3 | 一段話(<150 字) | About page / 自我介紹 | 加入故事和背景 |
Step 6: 產出 Landing Page 骨架
1. Hero:L1 標語 + L2 副標題 + CTA
2. Problem:3 個痛點(用情境不用功能)
3. Solution:產品截圖/GIF + 3 個核心功能
4. How it works:3 步驟流程
5. Social proof:(如果有的話)
6. CTA:重複 Hero 的 CTA輸出格式
## 產品定位:{產品名}
### Positioning Statement
For {目標客群}
who {問題/需求}
{產品名} is a {品類}
that {核心價值}
Unlike {替代方案}
{產品名} {差異化}
### One-liner(L1)
{一句話,可直接貼 bio / README 第一行}
### Elevator Pitch(L2)
{三句話,可直接念}
### About(L3)
{一段話,可貼 About page}
### 競品定位圖
軸:{X 軸} × {Y 軸}
| 產品 | {X 軸} | {Y 軸} | 備註 |
|------|--------|--------|------|
| {你的產品} | {位置} | {位置} | ← 你在這 |
| {競品 A} | {位置} | {位置} | |
| {競品 B} | {位置} | {位置} | |
### Landing Page 骨架
**Hero**
- 標語:{L1}
- 副標題:{L2}
- CTA:{按鈕文字}
**Problem**
1. {痛點情境 1}
2. {痛點情境 2}
3. {痛點情境 3}
**Solution**
1. {核心功能 1}:{一句話說明}
2. {核心功能 2}:{一句話說明}
3. {核心功能 3}:{一句話說明}
**How it works**
1. {步驟 1}
2. {步驟 2}
3. {步驟 3}
**CTA**
{重複 Hero CTA}
### 下一步建議
- [ ] {建議動作 1}
- [ ] {建議動作 2}
- [ ] {建議動作 3}Quality Gates
- Positioning Statement 每行通過「真的嗎?」測試
- 目標客群夠具體(不是「所有開發者」或「所有人」)
- 差異化是「不同」而非「更好」
- One-liner 在 15 字以內
- Elevator pitch 口語化,可以直接念出來
- Landing page 骨架的 Problem 用情境而非功能描述
- 沒有使用「革命性」「顛覆」「最好的」等空泛形容詞
- 所有素材風格一致
- 品類選擇是用戶已理解的概念
Heuristics
成功案例模式
- 「像 Notion 但只做 X」→ 借用已知品類 + 專注差異化,認知成本最低
- 「Y 問題的解法通常要 A+B+C,這個一鍵搞定」→ 簡單差異化,demo 效果好
- 「專門給 Z 族群的 X」→ 垂直市場定位,小眾但精準
失敗案例模式
- 「AI-powered everything platform」→ 什麼都做 = 什麼都不是
- 「比 X 更好」→ 沒有差異化,只有主觀判斷
- 「給所有人用」→ 等於給沒有人用
判斷捷徑
- Side project → 優先用「專注」差異化(你不可能跟大公司比功能量)
- PoC → 優先用「速度」或「整合」差異化(展示你能快速串接)
- 有明確數字 → 放進 one-liner(「30 秒完成原本 2 小時的工作」)
- 不確定品類 → 用「像 X 但 Y」公式,最容易讓人理解
Evidence boundaries
Use the actual current year. Cite dated primary sources for competitors, pricing and market claims. If browsing is unavailable, label the comparison unverified and use only supplied facts. Product ideas without a prototype may still be positioned as hypotheses; do not represent them as validated capabilities.
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
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.

