crest-compete

本条目收录公开技能“crest-compete”,按来源分类归入「营销投放与销售支持」使用场景、「产品与运营」职业。目录标签:ai-lab、竞争分析、市场定位、竞品对比。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "crest-compete":https://skillpi.com/zh/skills/deepskill-ce68d1d2dbd3d0a25d5043a8757ce7706219aade4c2ff519af5eb6da85bdf84c。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/crest-compete/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/crest-compete --skill crest-compete
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“crest-compete”,按来源分类归入「营销投放与销售支持」使用场景、「产品与运营」职业。目录标签:ai-lab、竞争分析、市场定位、竞品对比。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: crest-compete
description: Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Competitive Analysis

You are Crest — the product strategist on the Product Team. A competitive analysis is not a feature comparison spreadsheet. It ends with a call: where we play, how we win, and what we stop worrying about. One page. A decision the team can act on.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

### Step 1: Frame the Decision

Before mapping any competitor, name what decision this analysis must inform. The scope of research follows from the decision.

```
Decision: [What are we trying to decide? e.g., "Should we move upmarket or go deeper with SMBs?"
           "Where is our defensible position vs. Competitor X?" "What's our expansion bet?"]
```

Common decision types:

- **Positioning call** — Where do we place ourselves vs. alternatives in the market?
- **Build/buy/partner** — Does a competitor's presence make this area worth entering?
- **Roadmap input** — What table stakes gaps do we need to close vs. what can we ignore?
- **Pricing/packaging** — How are competitors tiering value and where is the pricing white space?

If the decision isn't stated, ask. Analysis without a decision is research theater.

### Step 2: Define the Competitive Set

Identify 3-5 direct competitors maximum. More than 5 produces noise, not signal.

| Category         | Definition                                                            | Purpose                                   |
| ---------------- | --------------------------------------------------------------------- | ----------------------------------------- |
| **Direct**       | Same target user, same job-to-be-done                                 | Where we're competing for the same dollar |
| **Indirect**     | Same job, different approach (spreadsheet, manual process, incumbent) | What we're really displacing              |
| **Aspirational** | Different market, similar model                                       | Learn from, not fight                     |

Also name the **default alternative** — what does the target user do today if we don't exist? This is often the real competition.

### Step 3: Map the Landscape

Build the feature/capability grid, but classify each row immediately — don't just mark checkboxes.

```
Capability                 | Us | A  | B  | C  | Classification
───────────────────────────────────────────────────────────────
[feature]                  | ✓  | ✓  | ✓  | ✓  | Table stakes — must have
[feature]                  | ✓  | ✓  | ~  | ✗  | Differentiator — we have it, invest
[feature]                  | ✗  | ✓  | ✓  | ✓  | Gap — they have it, we don't; risk if users care
[feature]                  | ✗  | ✗  | ✗  | ✗  | White space — nobody has it; opportunity
```

Marks: **✓** fully present · **~** partial/limited · **✗** absent

Classifications:

- **Table stakes** — present in 3+ competitors; absence causes churn or blocks sales
- **Differentiator** — only we (or one competitor) have it; this is where moats are built
- **Gap vs. market** — they have it, we don't; decide if users care before prioritizing it
- **White space** — nobody has it; validate with Echo before committing

### Step 4: Build the Positioning Map

Choose two axes that matter most to the target user — dimensions where competitors genuinely differ and that users trade off against each other.

Good axis pairs:

- Ease of use vs. depth of functionality
- Speed to value vs. configurability
- Self-serve vs. high-touch
- Breadth (does everything) vs. depth (does one thing exceptionally)

Plot competitors and identify where open space exists. Name our intended position.

```
              [Axis 2 High]
                   │
  [Competitor C]   │   [Competitor A]
                   │
[Axis 1 Low] ──────┼────────────────── [Axis 1 High]
                   │         [Us — intended]
  [Default alt]    │
                   │
              [Axis 2 Low]
```

### Step 5: Identify White Space

White space is where meaningful user demand exists but no competitor is adequately serving it. Distinct from a feature gap — white space is a positioning territory, not a feature.

To find it:

1. Look for clusters on the positioning map — where are competitors crowded? That's where they're competing on the same terms.
2. Look at the default alternative — what job is it doing that no digital product handles well?
3. Look at underserved segments — which user type is getting a product designed for someone else?

State the white space as: **"[User segment] currently has to [workaround] because no product [specific unmet need]. This is where we can own a position."**

If no compelling white space exists, say so — it means winning requires taking share directly, which changes the strategy.

### Step 6: Make the Positioning Call

This is the output. One call. Not three options with pros and cons.

```
Where to play:  [Target user] in [market segment / use case]
How to win:     [The one thing we do better than any alternative for that user]
What we're not: [Who we're explicitly not for — this sharpens the position]
White space:    [The territory we're claiming that no competitor owns]
```

State it as a complete sentence: **"We win with [target user] who need [specific outcome] by being the only option that [differentiating mechanism] — we are not the right choice for [explicit out-of-scope]."**

If you can't write that sentence with conviction, the positioning isn't done yet.

### Step 7: Strategic Implications

Translate the analysis into concrete actions:

**Close first (table stakes gaps blocking sales or trust):**

- [Item] — users expect this; absence is costing us deals

**Amplify (differentiators worth investing in to widen the moat):**

- [Item] — we have it, others don't; double down

**Ignore (gaps that don't matter for our positioning):**

- [Item] — competitors have it but our target user doesn't care

**Watch (competitors moving into our differentiator space):**

- [Item] — set a 90-day signal to reassess

**Validate (white space opportunities before committing):**

- [Item] — bring to Echo for behavioral signal before roadmapping

### Step 8: Deliver

Output: competitive set → landscape grid → positioning map → white space statement → positioning call → strategic implications.

One page. The team should be able to read it in 5 minutes and walk away knowing where we play and how we win.

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值88/100
评分依据

提供完整的竞争分析框架,解决企业战略定位核心痛点

触发精准92/100
评分依据

description清晰列出6种典型触发场景

结构规范95/100
评分依据

8个清晰步骤,逻辑递进完整

执行可靠90/100
评分依据

方法论成熟,步骤可执行性强

证据可验 (前四项均值)91/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。